NoKYCPhone
Get a number

Service status

All systems operational

Every system has been running normally. Last checked 21 Sep 2026, 18:51 UTC.

Uptime, 30 days
99.993%
Uptime, 90 days
100%
Uptime, 12 months
99.990%
Serving since
Sep 2024

Systems

Every moving part, day by day.

One column per day over the last 90 days. Uptime counts the share of the day actually lost, so a slow hour is not a lost day.

  • Operational
  • Degraded
  • Partial outage
  • Major outage
  • Maintenance

Messaging

  • Inbound SMSOperational

    Verification codes and messages arriving on your lines.

    90 days ago100% uptimeToday

  • Outbound SMSOperational

    Messages you send from one of your lines.

    90 days ago99.985% uptimeToday

  • Voice & voicemailOperational

    Incoming calls, recording and transcription.

    90 days ago100% uptimeToday

Platform

  • Web panelOperational

    The browser app: inbox, numbers, balance, settings.

    90 days ago100% uptimeToday

  • Public APIOperational

    REST endpoints and webhook delivery.

    90 days ago100% uptimeToday

  • WebsiteOperational

    Public pages, country directory and checkout.

    90 days ago100% uptimeToday

Supply

  • Number provisioningOperational

    New numbers going live after payment.

    90 days ago100% uptimeToday

Payments

  • Crypto paymentsOperational

    Deposit addresses, confirmations and balance credits.

    90 days ago99.986% uptimeToday

Measured from our own probes in Frankfurt, Ashburn and Singapore, one check per minute per system, plus the delivery receipts our carriers return. Everything on this page is computed from that record — nothing is set by hand.

History

Every incident since day one.

Nothing is removed once it is posted. 58 incidents over 735 days of service, maintenance windows included below.

Degraded performance

Delayed inbound SMS on Dutch ranges

20 Jan 2026, 14:37 UTC lasted 1 h 43

  • Inbound SMS
  1. Resolved16:20

    Resolved. Everything has been running normally since; nothing is pending on your side.

  2. Monitoring15:51

    Queued messages are draining and delivery times are back under ten seconds.

  3. Identified15:05

    Confirmed: one upstream route was queuing messages instead of rejecting them. Traffic is moving to the backup route.

  4. Investigating14:37

    A delivery route used for these ranges is returning delays. We are failing traffic over to a second route.

Major outage

Messaging and voice unavailable

8 Jan 2026, 14:31 UTC lasted 33 min

  • Inbound SMS
  • Outbound SMS
  • Voice & voicemail
  1. Resolved15:04

    Resolved after 33 min. A full write-up went out to every account with an active line. Nothing is pending on your side.

  2. Monitoring14:54

    All ranges are on the backup carrier. Messages that arrived during the outage are being replayed into the inboxes they belong to.

  3. Identified14:40

    Identified: our main carrier lost a core route, which took down both messaging and voice. We are moving every range to the backup carrier.

  4. Investigating14:31

    Messaging and voice are down. We are investigating with our upstream carriers.

Under maintenance

Carrier migration on part of the European ranges

2 Jan 2026, 04:00 UTC lasted 1 h

  • Inbound SMS
  • Outbound SMS
  1. Completed05:00

    Completed on time, with no impact outside the window.

  2. Started04:00

    The maintenance window has started. Numbers keep receiving throughout.

Jump to a month

How to read this page

What the numbers mean.

Times are UTC

Every timestamp on this page is UTC, with no daylight saving. A day runs from 00:00 to 23:59 UTC, which is also how the 90-day bars are cut.

Uptime is weighted

A major outage costs the full minute, a partial outage half of it, degraded performance twelve percent. Ninety minutes of slow delivery is not the same as ninety minutes of nothing, and the number says so.

What an incident is

Anything a customer could notice: delayed codes, a failing route, a slow panel, a payment not crediting. Third-party outages that break delivery are posted here too, even when the fault is upstream.

Machine-readable

The same data is served as summary.json for dashboards and as an Atom feed for readers and chat bots. Both are public and need no key.

No e-mail alerts

We never ask for an address, so we cannot send one. Subscribe to the feed, poll the JSON, or point a webhook at it — that is the whole notification story, by design.

Maintenance

Planned work is announced here at least 72 hours ahead and runs between 02:00 and 05:00 UTC. Your numbers keep receiving throughout; orders placed during a window are queued, never lost.

Something broken that is not listed?

Open a ticket from the panel, or write to us — we post an incident here as soon as we can confirm it affects more than one account.

Report a problem API reference