← Back to Twilio's check readings
We started checking Twilio on August 20, 2026, which is 65 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Twilio reports an incident on its status page, and again when it reports it resolved.
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Twilio's own status page declared. Below it, any public chatter we saw about Twilio and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Twilio's own status page declared. Three records side by side; none of them changes another.
- MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United States: minor incident, from before this window to now, still open per their page.
- MMS Delivery Failures From A Subset Of Network Subscribers In Australia To Twilio Australia Phone Numbers: minor incident, from before this window to now, still open per their page.
- Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) Failure Increase in Netherlands: minor incident, from before this window to 13:00 UTC.
- SMS Delivery Delays and Failures Between a Subset of Twilio Long Codes and Multiple Networks in Italy: minor incident, from before this window to now, still open per their page.
- SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile China: minor incident, from before this window to now, still open per their page.
- SMS Delivery Delays from a Subset of Twilio Short Codes to Cellularone NE Arizona United States: minor incident, from before this window to 11:00 UTC.
- SMS Delivery Delays from Twilio Short Codes to Multiple Networks in India: minor incident, from before this window to now, still open per their page.
- SMS Delivery Delays from Twilio to Orange France: minor incident, from before this window to 22:45 UTC.
- SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender Type to Jazz Pakistan: minor incident, from before this window to 22:45 UTC.
- SMS Delivery Failures from United Kingdom to a Subset of Twilio Long Codes: minor incident, from before this window to 19:15 UTC.
- Voice Call Failures and Post Dial Delay from a Subset of Twilio Mobile Numbers to Brazil: minor incident, from before this window to 04:45 UTC.
- Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to Israel: minor incident, from before this window to now, still open per their page.
- Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to Thailand: minor incident, from before this window to now, still open per their page.
- SMS Delivery Delays from Twilio to MTN Nigeria: minor incident, from 01:15 UTC to 06:30 UTC.
- RCS Inbound Events Delayed: minor incident, from 04:30 UTC to 05:30 UTC.
- SMS Delivery Delays and Failures from Twilio to Malitel Mali: minor incident, from 12:30 UTC to now, still open per their page.
- Hosted Number Verification Calls not Reaching Customers: minor incident, from 14:45 UTC to now, still open per their page.
- Intelligent Alerts Delivery Issues: minor incident, from 16:00 UTC to 16:30 UTC.
- Issue with 500 Errors on Porting Request Submissions: minor incident, from 17:00 UTC to 19:45 UTC.
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Twilio's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Twilio next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
- Confirmation probe17:30 UTC, Southeast Asia: a new incident on their status page prompted an extra probe. Result: Twilio answered normally.
- Confirmation probe17:30 UTC, US-Central: a new incident on their status page prompted an extra probe. Result: Twilio answered normally.
- Confirmation probe17:29 UTC, US-West: a new incident on their status page prompted an extra probe. Result: Twilio answered normally.
- Confirmation probe17:29 UTC, Canada: a new incident on their status page prompted an extra probe. Result: Twilio answered normally.
- Confirmation probe17:29 UTC, US-East: a new incident on their status page prompted an extra probe. Result: Twilio answered normally.
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
| Region | Checks passing | Probes recorded |
|---|---|---|
| US-East | 99.97% | 9124 |
| US-West | 100.00% | 9118 |
| Europe | 99.99% | 9049 |
| Asia-Pacific | 100.00% | 8802 |
| US-Central | 100.00% | 3708 |
| Canada | 99.97% | 3712 |
| UK | 100.00% | 3707 |
| Southeast Asia | 100.00% | 3676 |
| Australia | 99.86% | 3672 |
| South America | 99.70% | 3690 |
Their declared record
Twilio's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Showing the 10 most recent of 434 incidents Twilio has declared in the history we hold.
These entries are Twilio's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Twilio's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.