Uptime — last 90 days

100.00%
Last 24 hours
100.00%
Last 7 days
99.998%
Last 30 days
99.991%
Last 90 days

Regions

NOAM Operational
North America · IAD / SJC / DFW
30-day uptime100.00%
LATAM Operational
Latin America · GRU / MEX / SCL
30-day uptime100.00%
EURO Operational
Europe · LHR / FRA / AMS
30-day uptime99.998%
MENA Operational
Middle East & N. Africa · DXB / RUH / CAI
30-day uptime100.00%
AFRICA Operational
Sub-Saharan Africa · JNB / LOS
30-day uptime99.99%
INDIA Operational
Indian Subcontinent · BOM / DEL / HYD
30-day uptime100.00%
APAC Operational
Asia-Pacific · SIN / HKG / NRT
30-day uptime100.00%
ANZAC Operational
AU/NZ · SYD / AKL
30-day uptime99.99%
Global Edge Operational
Anycast · 200+ POPs worldwide
30-day uptime100.00%

Components

Inbound voice (SIP termination)
Operational
Outbound voice (2-way termination)
Operational
SMS & MMS — inbound & outbound
Operational
Call recording
Operational
Number provisioning
Operational
Port-in processing
Operational
REST API
Operational
Customer dashboard
Operational
Webhooks
Operational
Billing & payments
Operational

Recent incidents (last 30 days)

No incidents reported in the last 30 days.

Incident history

Scheduled maintenance — APAC SIP gateway upgrade
Mar 14, 2026 · 02:00–02:45 UTC
Maintenance APAC Completed

Rolling upgrade of SIP gateways in our SIN POP. Calls were automatically routed via HKG and NRT during the window — no customer impact observed.

Brief upstream carrier degradation — UK inbound
Feb 27, 2026 · 14:22–14:38 UTC
Investigating → Identified → Resolved EURO Resolved

One of our UK upstream carriers experienced a 16-minute degradation affecting roughly 4% of UK inbound calls. Traffic was failed over to alternate carriers; full service restored at 14:38 UTC. No data loss; affected calls received treatment per failover policy.

Dashboard slowness — login latency
Jan 18, 2026 · 09:10–09:35 UTC
Resolved Dashboard

Authentication service experienced elevated latency (login took 5–15s instead of usual sub-second). Voice and SMS/MMS traffic were unaffected. Resolved by failing over auth to a secondary database replica.

Stay informed

Subscribe to incident notifications by email at [email protected], or follow @didhubstatus for real-time updates. For incident-history JSON or RSS, see the API documentation.