Twilio degradation — 2026-08-11
Partially Degraded Service It began at 2026-08-11 11:17 UTC and is still ongoing after 1h 3m. We recorded 25 failing checks during the window.
Check-by-check timeline
- 2026-08-11 11:17 UTCDegraded51ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:20 UTCDegraded146ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:21 UTCDegraded465ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:24 UTCDegraded124ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:27 UTCDegraded211ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:30 UTCDegraded169ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:33 UTCDegraded111ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:36 UTCDegraded233ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:39 UTCDegraded80ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:42 UTCDegraded197ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:45 UTCDegraded20ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:48 UTCDegraded217ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:51 UTCDegraded128ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:51 UTCDegraded118ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:51 UTCDegraded82ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:53 UTCDegraded42ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:54 UTCDegraded81ms · HTTP 200Partially Degraded Service
- 2026-08-11 11:57 UTCDegraded300ms · HTTP 200Partially Degraded Service
- 2026-08-11 12:00 UTCDegraded18ms · HTTP 200Partially Degraded Service
- 2026-08-11 12:03 UTCDegraded337ms · HTTP 200Partially Degraded Service
- 2026-08-11 12:06 UTCDegraded111ms · HTTP 200Partially Degraded Service
- 2026-08-11 12:09 UTCDegraded253ms · HTTP 200Partially Degraded Service
- 2026-08-11 12:12 UTCDegraded191ms · HTTP 200Partially Degraded Service
- 2026-08-11 12:15 UTCDegraded122ms · HTTP 200Partially Degraded Service
- 2026-08-11 12:18 UTCDegraded140ms · HTTP 200Partially Degraded Service
Current Twilio status and full outage history
How this is measured
Readings are taken every few minutes from outside Twilio's network, combining their published status feed with a timed request to the service itself.
An incident opens after two consecutive bad readings and closes after two consecutive good ones, so the recorded duration may be a few minutes wider than the true outage.
Twilio's official status page is the authority on causes and affected components.