Twilio Outage History

The Twilio outage began around Nov 12, 2025 9:27 PM UTC with increased errors on Twilio Messaging APIs, followed by widespread SMS and MMS delivery delays across multiple carrier networks. Over the next several days, the incident persisted with ongoing reports of messages failing or arriving late across regions including North America, Europe, APAC, and Africa. The disruption lasted for multiple days and continued to be monitored through Nov 16, 2025 7:37 AM UTC as engineers and carrier partners worked to restore normal service.

Twilio's status page showed a sequence of updates from Investigation to Maintenance on various carrier pathways and messaging components (SMS, MMS, and REST API). Updates described ongoing investigation, carrier maintenance events, and progress toward recovery as the company coordinated with partners to resolve the issue and restore messaging throughput. The event coincided with a noticeable uptick in user-reported delivery problems and API errors, reflecting a broad impact on Twilio customers relying on messaging APIs and carrier routes.

Twilio experienced a broad, multi-day disruption affecting messaging and voice services globally as carrier maintenance activities took place. SMS and MMS deliveries were delayed or failed across many networks in North America, Europe, APAC, Latin America, and Africa, and some calls experienced failures or degraded quality. The incident began around Oct 23, 2025 2:02 AM UTC with United States MMS Carrier Partner maintenance and persisted through Oct 28, 2025 2:47 PM UTC as additional carrier networks and Twilio components underwent ongoing maintenance.

Twilio issued numerous status updates detailing investigations, monitoring steps, and maintenance across dozens of carrier networks and Twilio services, including SMS, MMS, Voice, various Sender IDs and identity/auth components, and developer tools. Notable examples included outages or delays to outbound calls in Hungary and Colombia, delivery delays to multiple networks across Africa, Europe, and the Americas, and intermittent issues with delivery receipts and identity lookups. The updates show a broad, regional footprint and ongoing recovery efforts.

Impact and reach were global, with user reports indicating degraded messaging performance rather than a complete service outage. The incident demonstrates how coordinated carrier-maintenance events can ripple across messaging and voice services, requiring continuous updates as networks recover. The latest update indicates ongoing monitoring as of Oct 28, 2025 2:47 PM UTC.

Twilio experienced a large-scale disruption beginning at Oct 21, 2025 4:02 AM UTC with United States SMS and MMS Carrier Maintenance for Verizon. Over the following ~44 hours, the issue broadened to numerous carrier networks and regions, producing SMS delivery delays, intermittent message failures, and some voice delivery issues in locations such as Hungary, Israel, and across Europe, Latin America, the Middle East & Africa, and APAC.

Twilio experienced widespread service disruptions across multiple product lines due to an AWS US-1 region incident. Customers reported SMS delivery delays and failures, degraded voice performance, and intermittent API responsiveness across various Twilio services, including Programmable Messaging, Programmable Voice, Flex, Studio, and Serverless. The outage began on Oct 20, 2025 8:12 AM UTC and persisted as AWS worked to remediate the incident, with impact felt across Twilio's messaging and communications platforms.

The Twilio incident began at Oct 17, 2025 10:47 AM UTC with delays in SMPP API MO traffic, followed by AccSec US Verizon API errors and SMS delivery delays to the Orange network in Spain. This degraded messaging affected three components: PROGRAMMABLE MESSAGING / SMPP, ACCOUNT SECURITY / Lookup, and CARRIER NETWORK / SMS in Europe, with messages experiencing delays and intermittent failures. The degraded period lasted about 3 hours and 15 minutes and the issues were regional rather than a full service outage. The status page tracked the progression through ongoing investigation and recovery updates.

Twilio experienced SMS delivery delays to Altan Redes in Mexico, affecting outbound messages routed through the Carrier Network / SMS Long Code, North America. Users sending messages to Altan Redes may have observed slower delivery during the incident.

The incident began at Oct 17, 2025 8:07 AM UTC and was resolved by Oct 17, 2025 8:27 AM UTC, lasting about 20 minutes. The carrier partner was engaged to resolve the issue, and Twilio posted two status updates during the incident, describing the delay and the eventual resolution. The impact was regional to Mexico.

The Twilio carrier network outage disrupted SMS, MMS, and Voice services. Users could experience message delivery delays and outbound call failures across regions as carrier partners and ZIPWHIP Messaging were affected. The incident began on Oct 15, 2025 1:42 PM UTC with an initial investigation into Identity Match API errors and related carrier issues, and escalated over the following hours as more components entered degraded or maintenance states.

Over the next 40 hours, Twilio issued multiple status updates and coordinated with partners across more than 10 carrier network components including SMS Long Code, SMS Short Code, Toll-Free, MMS, and ZIPWHIP Messaging in North America, as well as regional carrier networks in Europe, APAC, and Latin America. Recovery began as components moved back to up or monitoring, and the incident was resolved by Oct 17, 2025 6:02 AM UTC. The outage lasted approximately 40 hours and 20 minutes.

Twilio experienced widespread SMS delivery delays across multiple carrier networks, impacting texts on routes including Altan Redes in Mexico, Vodafone and EE in the United Kingdom, Shelcomm in the United States, Tele2 in APAC, and Safaricom in Ethiopia.

The incident began at Oct 14, 2025 8:17 PM UTC and lasted through Oct 15, 2025 12:27 PM UTC, roughly 16 hours. The Twilio status page posted 23 updates during the incident, noting ongoing maintenance with carrier partners and continuous monitoring as engineers worked to restore delivery.

As recovery progressed, several networks began returning to normal while others remained under monitoring or maintenance. The updates reflect a coordinated effort across many carrier networks to restore SMS delivery.

Twilio reported delays in receiving SMS delivery reports for messages sent to Italy, reducing visibility into delivery status for affected messages. The issue impacted the CARRIER NETWORK / SMS, Europe component. The incident began at Oct 14, 2025 1:17 PM UTC when the status page moved to a warning and was resolved by Oct 14, 2025 4:07 PM UTC after the final update, lasting approximately 2 hours and 50 minutes. The provider published two status updates during the incident describing the issue and its resolution.

Twilio conducted a coordinated carrier maintenance window across United States and Latin American networks, impacting SMS and MMS delivery. The maintenance began at Oct 14, 2025 3:02 AM UTC with United States MMS Carrier Maintenance for AT&T and continued through the day with Verizon, T-Mobile, and Mexico-based AT&T maintenance windows. Over the incident, nine official status updates were issued, and multiple carrier networks across North America and Latin America listed maintenance on components including SMS Short Code, SMS Long Code, MMS Short Code, MMS Long Code, Toll-Free, and ZIPWHIP MESSAGING. By Oct 14, 2025 12:02 PM UTC, many components had returned to service as maintenance progressed, though some remained in progress during the window.

Impact focused on SMS and MMS routing across regional networks. Users in affected regions may have experienced temporary delays or interruptions in sending or receiving messages during the maintenance window. The incident was communication-driven maintenance rather than an unplanned outage, with the carrier teams coordinating restoration as maintenance tasks completed.