Twilio Outage History
Daily provider-status observations and published incident history for Twilio.
Twilio has an active component incident; no global outage is indicated. Verified . Official provider source.
Looking for an update now? Check the current status, or follow Twilio for future changes.
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with issues |
|---|---|---|---|
| September 2026 | 0% | 30 | 30 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Incident History
Voice Call Failures and Post Dial Delay from Twilio Phone Numbers to DigiMobil Spain
View incident details and source
Started:
SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in United States
View incident details and source
Started:
SMS Delivery Delays and Failures from Twilio to DigiMobil (Movistar) Spain
View incident details and source
Started:
SMS Delivery Delays from Twilio to Algar Telecom Brazil
View incident details and source
Started:
Gateway API (Lookup API) Failure Increase and High Latency on Verizon in United States
View incident details and source
Started:
SMS Delivery Delays from Twilio to Kolbi Costa Rica
View incident details and source
Started:
SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in Colombia
View incident details and source
Started:
SMS Delivery Delays from a Subset of Twilio Phone Numbers to Tigo Guatemala
View incident details and source
Started:
SMS Delivery Delays and Failures from Twilio to Wind Tre Italy
View incident details and source
Started:
SMS Delivery Failures from a Subset of Twilio Short Codes to Multiple Networks in Chile
View incident details and source
Started:
Legacy Incident Archive
793 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.