Live · refreshing every 30s

All systems normal.

Voice, messaging, AI, dashboard and APIs are operating within SLA across every region.

API requests / sec
12,847+2.1%
Avg API latency
84 ms−3 ms
Call setup success
99.98%30d
Services

90-day uptime · per component

Outbound calls
99.99%
Inbound calls
99.97%
Call recordings
100.00%
Media streams (WebSocket)
99.96%
Regions · 14 of 14 healthy

Every edge, in real time

us-east-1
US East
18ms p50
Load62%
us-west-2
US West
22ms p50
Load48%
ca-central-1
Canada
24ms p50
Load31%
sa-east-1
Brazil
41ms p50
Load27%
eu-west-2
UK
12ms p50
Load71%
eu-west-1
Ireland
14ms p50
Load55%
eu-central-1
Germany
16ms p50
Load49%
eu-west-3
France
17ms p50
Load38%
me-central-1
UAE
32ms p50
Load22%
ap-south-1
India
28ms p50
Load58%
ap-southeast-1
Singapore
19ms p50
Load64%
ap-northeast-1
Tokyo
21ms p50
Load44%
ap-southeast-2
Sydney
26ms p50
Load33%
af-south-1
South Africa
38ms p50
Load19%
Performance · last 24h

Live performance metrics

API latency · p50
−3 ms
84 ms
−24hnow
API latency · p99
+9 ms
412 ms
−24hnow
Call answer rate
+0.2%
98.7%
−24hnow
SMS delivery · global
stable
99.4%
−24hnow
Webhook delivery · first try
+0.04%
99.91%
−24hnow
Agent first-token latency
−11 ms
182 ms
−24hnow
Incidents · last 90 days

Past incidents

  1. ResolvedElevated webhook delivery latency in eu-west-1
    42 min
    Affected:Webhookseu-west-1
    1. Resolved

      All webhook queues drained. Median delivery is back to 320ms. No data loss; affected events were retried.

    2. Identified

      Tracked to a misbehaving downstream egress node. Rolling restart in progress.

    3. Investigating

      Customers in EU regions seeing elevated webhook delivery times. APIs are unaffected.

  2. MaintenanceScheduled SBC firmware update · ap-southeast-1
    20 min · no impact
    Affected:Voiceap-southeast-1
    1. Completed

      Firmware roll-out complete. No customer impact observed; the upgrade was hitless.

    2. Maintenance start

      Beginning the scheduled SBC firmware update. Calls failover transparently across the cluster.

  3. ResolvedSMS deliverability degraded · US T-Mobile
    1h 14m
    Affected:Messaging · SMSCarrier: T-Mobile
    1. Resolved

      Carrier confirmed remediation. Queued messages delivered within 8 minutes after recovery.

    2. Identified

      Upstream issue confirmed by T-Mobile. We are queueing and retrying affected messages with backoff.

Subscribe

Know before your customers do.

Pick the components you care about and the channels you check — we'll do the routing. Average notification latency under 8s from incident open.

Unsubscribe anytime. We never share your details.

Email

Per-component updates straight to your inbox.

SMS

Sev-1 only. Always-on, even outside hours.

Webhook

Push to your incident pipeline / Slack / PagerDuty.

RSS / Atom

Plain feeds. Self-host away.