• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more

Network status

All systems operational

Updated 22 November 2026, 12:29 UTC. Refreshes every minute. Times on this page are UTC.

Uptime since launch
99.886%
lowest component
API latency, 24 h
125 ms
p50, p95 315 ms
Delivery rate, 7 days
98.5%
delivered of sent, all routes
Webhook latency
1.1 s
p95, event to first attempt

Components

  • Operational
  • Degraded
  • Outage
  • Maintenance
  • Before launch
  • APISend, status, rates and balance endpoints
    Operational
    90 days ago99.913% uptime since launchToday
  • Web panelCampaign composer, reports and account
    Operational
    90 days ago100.000% uptime since launchToday
  • WebhooksDelivery events pushed to your endpoints
    Operational
    90 days ago99.910% uptime since launchToday
  • Crypto depositsAddress generation and crediting
    Operational
    90 days ago100.000% uptime since launchToday
  • Routes: North AmericaUnited States, Canada and the Caribbean
    Operational
    90 days ago100.000% uptime since launchToday
  • Routes: EuropeEU, UK, Nordics, Balkans, Turkey
    Operational
    90 days ago99.918% uptime since launchToday
  • Routes: Latin AmericaBrazil, Mexico, Andes, Southern Cone
    Operational
    90 days ago99.886% uptime since launchToday
  • Routes: Middle East & AfricaGulf, Levant, North, West and East Africa
    Operational
    90 days ago99.985% uptime since launchToday
  • Routes: Asia-PacificSouth Asia, South-East Asia, East Asia, Oceania
    Operational
    90 days ago100.000% uptime since launchToday

Scheduled maintenance

Next window: Wednesday 9 December 2026, 02:00 to 02:40 UTC.

planned

Scheduled maintenance: database failover drill

MNT-202612API, Web panel40 min

Planned failover of the primary database to its replica. The API and panel stay available; requests may see up to a few seconds of added latency during the switch. Message routing, webhooks and deposits are not affected.

HistoryPast incidents

Since launch, every incident, every update.

Each entry keeps the full timeline as it was posted. Durations are from first report to resolution. Maintenance windows are listed with the incidents.

November 20263 entries

  • 19 NovdegradedDegraded delivery to one operator in Europe2 h 28 min

    INC-21373CRoutes: Europe01:28 to 03:56 UTC

    1. 01:28Investigating

      We are seeing a lower delivery rate than usual to one operator in Europe. Other operators in the region are unaffected.

    2. 02:20Identified

      The route to this operator is filtering a share of traffic. We are swapping it for an alternative route.

    3. 03:22Monitoring

      Traffic to the affected operator is now on the alternative route and delivery rates have recovered. We are monitoring.

    4. 03:56Resolved

      Delivery rates to the operator have been normal for the past hour. Incident resolved.

  • 11 NovmaintenanceScheduled maintenance: database failover drill40 min

    MNT-202611API, Web panel02:00 to 02:40 UTC

    Planned failover of the primary database to its replica. The API and panel stay available; requests may see up to a few seconds of added latency during the switch. Message routing, webhooks and deposits are not affected.

    Completed as planned. No customer impact was recorded.

  • 1 NovdegradedDelayed webhook deliveries2 h 43 min

    INC-1E1E3AWebhooks13:04 to 15:47 UTC

    1. 13:04Investigating

      Webhook events are being delivered with a delay. No events are lost; they are queued and will be delivered in order.

    2. 14:02Identified

      The webhook dispatcher is working through a backlog caused by a slow downstream endpoint saturating a worker pool. Isolation per endpoint has been enforced.

    3. 15:13Monitoring

      The backlog is clearing and delivery delay is back under one minute for most endpoints.

    4. 15:47Resolved

      All queued events have been delivered. Incident resolved.

October 20263 entries

  • 22 OctdegradedIntermittent 429 responses below the documented rate limit2 h 37 min

    INC-F3F5E3API12:40 to 15:17 UTC

    1. 12:40Investigating

      Some keys are receiving 429 responses below their limit. Retrying after the Retry-After header succeeds.

    2. 13:28Identified

      A rate-limiter node had a stale configuration. It has been reloaded.

    3. 14:41Monitoring

      No incorrect 429 responses observed since the reload. We are monitoring.

    4. 15:17Resolved

      Incident resolved.

  • 14 OctmaintenanceScheduled maintenance: database failover drill40 min

    MNT-202610API, Web panel02:00 to 02:40 UTC

    Planned failover of the primary database to its replica. The API and panel stay available; requests may see up to a few seconds of added latency during the switch. Message routing, webhooks and deposits are not affected.

    Completed as planned. No customer impact was recorded.

  • 9 OctoutageDelivery failures on Latin America routes1 h 43 min

    INC-87F37FRoutes: Latin America06:22 to 08:05 UTC

    1. 06:22Investigating

      Messages to several operators in Latin America are failing with carrier error codes. Sending is paused on the affected route while we investigate.

    2. 06:46Identified

      The upstream carrier confirmed an outage on its signalling link. Traffic is being moved to the backup route for the affected operators.

    3. 07:43Monitoring

      Traffic is flowing on the backup route. Queued messages are being released in order; delivery receipts may arrive with a delay.

    4. 08:05Resolved

      The primary route has been restored and verified. All queued messages were delivered or reported as failed with their carrier code. No message was billed twice.

September 20261 entry

  • 21 SepdegradedDegraded delivery to one operator in Middle East and Africa27 min

    INC-0C018DRoutes: Middle East & Africa13:46 to 14:13 UTC

    1. 13:46Investigating

      We are seeing a lower delivery rate than usual to one operator in Middle East and Africa. Other operators in the region are unaffected.

    2. 13:52Identified

      The route to this operator is filtering a share of traffic. We are swapping it for an alternative route.

    3. 14:07Monitoring

      Traffic to the affected operator is now on the alternative route and delivery rates have recovered. We are monitoring.

    4. 14:13Resolved

      Delivery rates to the operator have been normal for the past hour. Incident resolved.

History starts 21 September 2026, when this page went live. Degraded performance counts half in uptime; outages count in full.