Twilio Outage History

Twilio experienced a major disruption beginning on Jan 9, 2026 3:22 AM UTC, with widespread delays and delivery failures across SMS, MMS, and voice services. The impact affected multiple carrier networks and regions, disrupting message delivery and voice calls for many customers. Initial updates cited MMS delivery delays to a subset of Twilio numbers in Australia caused by an ongoing undersea cable fault, with the issue later expanding to additional SMS/MMS routes and carriers around the world. The incident lasted for several days and affected a broad set of Twilio components across carrier networks and Twilio Platform services.

Over the next several days, Twilio issued numerous status updates as engineers worked with carrier partners to restore service. The disruption impacted a wide range of components including SMS, MMS, Voice, and related verification and developer tools. The incident persisted for roughly eight days, from Jan 9, 2026 3:22 AM UTC to Jan 17, 2026 1:22 AM UTC, with gradual recovery and ongoing monitoring noted in updates.

Twilio reported an outage affecting SMS delivery and RCS messaging in the United States and Canada. The issue began with delays to the AT&T network in the US via a subset of short codes and expanded to include delays and occasional failures for messages sent to and from Twilio numbers in the US and Canada via short and long codes. Users could experience slower delivery or non-delivery of SMS and RCS messages during the incident, with a regional pattern centered in North America. The outage lasted from Jan 8, 2026 8:07 AM UTC to Jan 8, 2026 3:27 PM UTC, roughly 7 hours and 20 minutes, and the provider issued a total of 7 status updates throughout the incident.

From Jan 7, 2026 1:32 PM UTC to Jan 8, 2026 8:02 AM UTC, Twilio experienced widespread SMS delivery delays and call failures across a broad set of carrier networks, affecting North America, Europe, APAC, and Africa. The incident included delays to SMS messages to and from numbers such as Google Voice in the United States, inbound and outbound call issues in several regions, and various carrier-specific degradation across SMS, MMS, and voice services. The outage lasted roughly 18 hours and 30 minutes as recovery progressed.

Twilio experienced widespread issues affecting SMS, MMS, and voice services across multiple carrier networks, resulting in delivery delays, failed verifications, and degraded call quality for users. The incident began on 8:37 AM UTC with call quality issues involving Twilio numbers in Taiwan and expanded to additional regions and services over the following days. While some users reported severe SMS delays (including 2FA codes), the disruption persisted for several days as carrier partners investigated and implemented mitigations. The incident appears to have had a broad, multi-service impact, rather than a single-point outage.

Twilio issued numerous official updates on the status page, detailing investigations into Taiwan call quality, multiple carrier maintenance events, and ongoing efforts to resolve SMS delivery delays and inbound call failures across Voice, SMS, MMS, and related networks. The updates show the incident evolving over time with components moving between up, warn, and maintenance as recovery progressed. By Jan 7, 2026 12:02 PM UTC many networks had returned to normal operation, though some monitoring and maintenance activities continued during the recovery phase. A sample user in Atlanta described extreme SMS delays affecting two-factor verifications, illustrating the real-world impact of the disruption.

The Twilio Programmable Messaging system experienced an outage affecting RCS messaging and the carrier network. RCS messages failed to reach end users due to TTL expiration, resulting in undelivered delivery status reports. Simultaneously, SMS delivery delays were observed for Roshan/TDCA Network in Afghanistan, impacting message delivery timelines for users in that region. The incident affected two components: PROGRAMMABLE MESSAGING / RCS Messaging and CARRIER NETWORK / SMS in the Middle East & Africa. The outage began on Dec 29, 2025 1:52 AM UTC and was resolved by Dec 29, 2025 4:27 AM UTC, lasting approximately 2 hours and 35 minutes. There were four official status updates during the incident, with updates moving from investigation to monitoring and recovery.

Twilio experienced SMS delivery delays and failures affecting Movicel customers in Angola. The issue was isolated to the Carrier Network / SMS component for the Middle East & Africa region. The outage began on 7:32 AM UTC and was resolved by 12:57 AM UTC, lasting approximately 17 hours and 25 minutes. Twilio engineers were working with the Movicel carrier to restore normal service.

Twilio posted two status updates during the incident, starting with an investigation and a follow-up note confirming continued work with the carrier, before the service was restored. The impact was regional, centered on Angola via Movicel.

Twilio experienced SMS delivery delays when sending messages to Coop Network in Italy, causing slower delivery for affected recipients. The issue was isolated to the CARRIER NETWORK / SMS, Europe component and did not indicate a full outage. The incident began at 9:47 AM UTC and was resolved by 4:37 PM UTC, lasting approximately 6 hours and 50 minutes.

Twilio experienced SMS delivery delays affecting the United States for a subset of shortcodes and delays delivering messages to Claro in Colombia. The incident began at 5:02 PM UTC and was resolved by 9:57 PM UTC, lasting approximately 4 hours and 55 minutes. The disruption involved two carrier network components: CARRIER NETWORK / SMS Short Code, North America and CARRIER NETWORK / SMS, Latin America.

Twilio experienced widespread delays delivering SMS and MMS messages across multiple carrier networks worldwide. The incident began on Dec 25, 2025 3:42 PM UTC with MMS delivery delays to C Spire in the United States, and subsequently affected destinations including Movicel in Angola and GrameenPhone in Bangladesh, with issues observed across Europe, the United Kingdom, and Africa. Users reported messages arriving slowly or not at all, and there were intermittent call failures noted in related channels. The outage persisted for roughly 24 hours and was largely recovering by Dec 26, 2025 3:17 PM UTC as networks began to restore deliveries. The incident impacted multiple carrier networks and message types (MMS, SMS, Short Code, and Voice) across regions including North America, Europe, APAC, and Africa.

Twilio reported outages delivering SMS to multiple networks in Mexico via a subset of short codes, with investigations underway by Twilio and carrier partners. The issue began on Dec 22, 2025 3:07 PM UTC and affected messages reaching Mexican networks, likely causing failures or delays for some users. By Dec 22, 2025 6:32 PM UTC, Twilio indicated partial success for a subset of short codes and continued monitoring as the situation evolved. The incident impacted regional carrier networks across Latin America and extended to other regions, including North America, Europe, and the Middle East & Africa, involving both standard SMS paths and short-code routes.