Twilio Outage History

Twilio experienced SMS delivery delays when sending messages to the Turkcell carrier in Turkey, resulting in slower or queued SMS delivery for messages to Turkcell customers. This degraded the reliability of SMS for Turkish users and could affect time-sensitive communications such as one-time passwords and alerts. The issue impacted two Twilio components: Carrier Network / SMS and Programmable Messaging / SMS.

The outage began on Jul 6, 2025 5:57 AM UTC and was resolved by Jul 6, 2025 10:27 AM UTC, lasting approximately 4 hours and 30 minutes. The provider issued two official status updates during the incident, confirming investigation with the Turkcell carrier and later reporting resolution as the delivery problems were mitigated.

Twilio experienced an extended incident affecting SMS delivery and API services across multiple regions. Users attempting to send messages faced delivery delays to Claro in Brazil and observed degraded performance in several carrier networks, as well as API issues in the United Kingdom. The event began on 5:32 PM UTC and lasted for about 27 hours, with regionalized impact across Latin America, Europe, Africa, and APAC.

Twilio's status page posted multiple updates during the incident, including notices about SMS delays, API errors, and ongoing mitigations with carrier partners. Some components were moved to maintenance during the investigation, and by 8:22 PM UTC many services returned to normal as engineers continued to monitor for stability.

Twilio reported a brief maintenance window affecting SMS delivery to the Globe network in the Philippines. The issue caused temporary delays in message delivery and was resolved after about five minutes. The status page indicated ongoing recovery and two official updates were posted during the incident, noting that delivery would return to normal as monitoring continued. The incident began at Jul 4, 2025 10:07 AM UTC and was resolved by Jul 4, 2025 10:12 AM UTC.

The incident began at Jul 4, 2025 4:07 AM UTC with scheduled carrier maintenance in the United Arab Emirates by Etisalat, impacting the CARRIER NETWORK / SMS path in the Middle East & Africa. Users experienced outages or delays in SMS delivery while the maintenance was in progress.

By Jul 4, 2025 7:12 AM UTC the issue expanded to Globe Network in the Philippines (APAC), with engineers working with the carrier partner to resolve the delays. The provider issued updates as the situation progressed and the APAC path showed signs of recovery over the morning.

Recovery progressed and by Jul 4, 2025 10:02 AM UTC the routes had returned to normal for the affected regions. The incident lasted approximately 6 hours.

An outage affected Twilio's ability to deliver SMS and MMS to certain carrier networks, starting with the Libyan Al Madar network. Users in Libya experienced outbound message delivery issues as engineers investigated with carrier partners. The incident expanded into Europe, where carrier- and identity-match related maintenance (Germany and Vodafone in the UK) was conducted to restore services. The issue spanned multiple carrier-network components and regions, with updates indicating ongoing maintenance and mitigation actions until all components returned to normal.

The outage began on Jul 3, 2025 3:17 PM UTC and was resolved by Jul 4, 2025 3:02 AM UTC. Over the course of the incident, Twilio issued 6 official status updates. The affected components included 4 carrier-network areas across Africa/Middle East and Europe, with Libyan SMS delivery issues followed by European carrier-partner maintenance that eventually restored service.

An incident on July 3, 2025 affected Twilio's messaging and transcription services, impacting users in Italy. SMS delivery to the Wind Tre network experienced delays starting at 1:32 PM UTC, while an accompanying spike in received recordings caused increased latency in creating transcripts for Programmable Voice. These issues reduced messaging reliability and slowed transcription processing for a period of about 1 hour and 5 minutes. The regional impact was centered on Italy (Wind Tre) with broader European relevance given the carrier involved.

The provider communicated with four updates during the incident. By 2:27 PM UTC, SMS delivery delays were showing signs of recovery, and by 2:37 PM UTC both issues had largely resolved and affected components returned to normal operation.

Twilio faced a global service disruption beginning on Jun 27, 2025 6:14 PM UTC. The initial update cited WhatsApp pricing issues tied to an accidental Meta rollout, but the incident quickly expanded to broad SMS and voice problems across multiple carrier networks and regions. Users experienced SMS delivery delays and failures to various networks, HTTP 500 errors on Calls API endpoints, and delays in transcription for Autotranscribe.

Over the following days, Twilio issued numerous status updates across Programmable Messaging, Voice, Carrier Network, and other services. Communications described ongoing investigations, in progress maintenance, and gradual recovery as carrier partners and Twilio engineers worked to resolve issues that affected messaging (SMS, MMS), voice calls, and related API behavior across Europe, the Americas, APAC, and the Middle East and Africa.

As of Jul 3, 2025 6:47 AM UTC, Twilio continued to monitor and remediate, with several components returned to operational states and ongoing carrier work to complete the recovery. The incident was global in scope and persisted for multiple days, with updates signaling continued stabilization across messaging, voice, and developer tooling.

Twilio conducted scheduled maintenance on United States SMS and MMS carrier networks in North America. The maintenance window began at 3:02 AM UTC and concluded at 11:02 AM UTC, lasting roughly 8 hours. The work affected North American routes for SMS Short Code, MMS Short Code, SMS Long Code, and MMS Long Code numbers.

Twilio's status page tracked the event as a scheduled maintenance, with the window starting at 3:02 AM UTC and ending at 11:02 AM UTC. The status changed from up to maintenance and back to up, and the page noted the maintenance affected four North American carrier routes: CARRIER NETWORK / SMS Short Code, North America; CARRIER NETWORK / MMS Short Code, North America; CARRIER NETWORK / SMS Long Code, North America; CARRIER NETWORK / MMS Long Code, North America. The incident was managed with two official status updates on the Twilio status page.

Twilio experienced broad degradation of messaging and voice services, beginning on May 30, 2025 3:22 PM UTC with SMS delivery delays to Algar Telecom in Latin America. The issue then expanded to inbound call failures to the KPN network in the Netherlands and subsequently affected additional networks across Europe, APAC, the Americas, and beyond. Customers could have seen delayed or failed SMS messages, intermittent call quality problems, and general degraded performance across Twilio's messaging and voice pathways.

Twilio responded with a steady stream of status updates on their Status page, covering investigations, ongoing monitoring, and scheduled maintenance for Twilio Phone Numbers and related carrier networks. Updates were issued over several days, with the latest entries indicating that issues persisted across multiple regions and components (including CARRIER NETWORK / SMS, Voice, and PHONE NUMBERS) as of Jun 6, 2025 11:02 AM UTC. The incident spans roughly {{duration:2025-05-30T15:22:00Z}} to Jun 6, 2025 11:02 AM UTC (about 6 days and 20 hours).

Twilio experienced a multi-service disruption affecting voice calls in Korea and API latency during a prolonged maintenance window. Voice calls from Korea network subscribers to a subset of Twilio Korea toll-free numbers failed, and Lookup API V1 experienced increased latency. The incident also involved scheduled maintenance that impacted Twilio Hosted SMS and long-code registrations across North America. The outage lasted from May 30, 2025 1:37 AM UTC to May 30, 2025 11:02 AM UTC, with ongoing updates as engineers worked to restore affected components.