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
SMS Delivery Delays from Twilio to Ooredoo Kuwait
View incident details and source
Started:
Increased Latency In Console
View incident details and source
Started:
SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender IDs and Long Codes to LIME Cayman Islands
View incident details and source
Started:
SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Tigo Colombia
View incident details and source
Started:
SMS Delivery Failures from Twilio to Datora Brazil
View incident details and source
Started:
Intermittent Failures to Update Call Recordings
View incident details and source
Started:
SMS Delivery Delays and Failures from a Subset of Twilio Short Codes and Toll-Free Numbers to Altice (CSC Wireless) United States
View incident details and source
Started:
SMS Delivery Receipt Delays from Twilio to Globe Telecom Philippines
View incident details and source
Started:
Voice Call Failures and Audio Quality Degradation between a Subset of Twilio Phone Numbers and Multiple Networks in Hong Kong
View incident details and source
Started:
SMS Delivery Delays and Failures from Twilio to Megafon Tajikistan
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.