Twilio Outage History

Twilio experienced SMS delivery delays affecting messages to AT&T Mexico in Mexico and across multiple US networks using short codes. The issue began at Aug 15, 2025 11:07 PM UTC and prompted a series of updates as Twilio investigated and mitigated the issue. An associated Flex Insights historical reporting maintenance was also noted during the period. By Aug 16, 2025 2:47 PM UTC, the Latin America carrier network had recovered to normal, while other networks continued to recover. The incident spanned roughly 15 hours and 40 minutes and mainly resulted in delayed SMS delivery rather than a full outage.

From Aug 8, 2025 5:12 PM UTC Twilio began reporting degraded performance across multiple carrier networks and channels, including SMS delivery delays and delivery receipt delays to Viettel Burundi, and call failures affecting various numbers and regions. The impact spanned SMS, MMS, Voice, and programmable messaging, with users experiencing delays in sending messages, failed calls, and intermittent voice transcription issues. The Twilio status updates documented an ongoing investigation and monitoring across numerous components, with engineers working with carrier partners to restore service. The incident reflected a broad, multi-network disruption across multiple regions and services.

Twilio SMS delivery delays affected two regional carrier networks: Europe (Novatel Slovenia) and APAC (Telenor Pakistan). Messages to Slovenian Novatel via a subset of longcodes and alphanumeric numbers experienced delays, and some messages to Telenor Pakistan were delayed or failed. The incident began at 11:47 AM UTC and lasted until 3:02 PM UTC, spanning about 3 hours and 15 minutes. The affected components were CARRIER NETWORK / SMS, Europe and CARRIER NETWORK / SMS, APAC.

Twilio's engineering teams investigated and coordinated with carrier partners. Four official status updates were issued during the incident, including notes at 12:37 PM UTC and 2:22 PM UTC; the final update at 3:02 PM UTC indicated the regions had moved back to normal and service was restored. This incident demonstrates the dependence on carrier networks for international SMS traffic and shows how regional routes can be impacted for several hours even without a full outage.

The Twilio SMS path to the Telenor network in Pakistan experienced delays and some delivery failures, impacting outbound messages to Pakistani recipients. The issue affected the CARRIER NETWORK / SMS, APAC component and was localized to Pakistan. The outage began at Aug 8, 2025 8:57 AM UTC and was resolved by Aug 8, 2025 10:27 AM UTC, lasting about 1 hour and 30 minutes. The provider issued 2 status updates during the incident.

Twilio reported that engineers were investigating and working with the carrier partner to resolve the issue, and the service returned to normal after the carrier issue was addressed.

Twilio experienced a broad disruption affecting SMS delivery and some voice capabilities across multiple carrier networks. The incident began during a Japan Voice Carrier Partner maintenance window and escalated to widespread SMS delays to networks in the United States via a subset of shortcodes, with additional regional impact in Nigeria, Mexico, Israel, and the UAE. The disruption spanned APAC, North America, Latin America, and MEA, impacting messaging channels including SMS and related voice services. The outage lasted roughly 12 hours, from Aug 7, 2025 1:02 PM UTC to Aug 8, 2025 1:12 AM UTC.

Twilio experienced widespread SMS and MMS delivery delays across carrier networks globally. The incident began on 4:02 AM UTC with carrier maintenance affecting North America, and over the next days updates described ongoing SMS/MMS delivery delays and intermittent issues with various carriers (including AT&T Mexico, China Unicom, MTN Nigeria, MTN Ivory Coast, Vodafone UK, Verizon, and others). The disruptions affected SMS Long Code, Short Code, Toll-Free, and MMS paths, impacting messaging in North America, Latin America, Europe, APAC, and Africa. The outage lasted for about 2 days and 8 hours, ending around 12:02 PM UTC.

Twilio's status page posted numerous updates detailing maintenance events, investigations, and progress toward recovery. The incident involved multiple carrier networks and messaging components, with partial recoveries appearing over time as carriers completed work. By the end of the window, some regions and paths had recovered while others continued to experience delays.

Twilio experienced a series of carrier-related disruptions that affected voice and messaging services across multiple regions. Inbound call failures were observed on a subset of UK numbers, and there were delays in VoiceBase voicemail transcriptions and SMS delivery to Bouygues Telecom in France. Additional issues included inbound calls to Twilio Japan numbers and a broader set of carrier-path problems impacting several Twilio components across Europe, APAC, and North America. The incident began on Aug 3, 2025 11:47 AM UTC and involved ongoing updates and remediation activities as engineers worked with carrier partners to identify and resolve the root causes, continuing through 1:42 AM UTC when recovery progressed.

Twilio experienced scheduled carrier maintenance affecting the SMS network and identity routing services in the APAC region and the United Kingdom. The incident began at 8:02 PM UTC with maintenance on three components: CARRIER NETWORK / SMS, APAC; Lookup Identity Match; Legacy Identity MatchAndAttributes. A second maintenance window for the Vodafone UK carrier partner followed, with APAC SMS moving to up by 11:02 PM UTC and the remaining identity matching components restored later. All affected components were back to normal by 5:42 AM UTC, ending a roughly 9 hours and 40 minutes maintenance window. Over the course of the incident, the provider issued 3 status updates. The geographic impact centered on APAC regions and the United Kingdom.

Twilio reported SMS delivery delays to AmericaNet in Brazil and SMS delivery failures to LG U+ in South Korea, impacting users trying to send messages to those networks. The incident began at 12:12 AM UTC and persisted for several hours while engineers worked with carrier partners to resolve the issue. The disruption involved two carrier networks in Latin America and APAC and caused degraded message delivery during the event window.

Twilio's status page showed ongoing investigation and regular updates from the engineering team, with a focus on restoring service with the carrier partners. Recovery began for the APAC network around 8:37 AM UTC and full restoration across affected networks was in place by 8:57 AM UTC.

An issue with the AccSec US Verizon API caused errors in Twilio's Account Security / Lookup flow, potentially impacting account verification and related security checks. The incident began at Aug 1, 2025 6:37 PM UTC and led to a degraded operation status while Twilio's engineering team investigated, with an update expected in about an hour. The status page indicated monitoring detected the issue and that engineers were actively investigating.

The problem was resolved by Aug 1, 2025 11:07 PM UTC, at which point the Account Security / Lookup component returned to normal and the status page was updated to up. The incident involved a single component and lasted approximately 4 hours and 30 minutes, with two status updates issued during the course of the incident.