Twilio Outage History

Twilio experienced widespread delays delivering SMS across carrier networks worldwide, impacting messaging across Europe, Africa, APAC and the Americas. The issue began with delays to Lebara in France and expanded to a broad set of carriers, Long Code registrations, and related voice/video services in multiple regions. The incident affected numerous components, including CARRIER NETWORK / SMS across APAC, Europe, LATAM, and MEA, as well as Programmable Voice features like ConversationRelay and associated long-code registrations. The outage caused degraded SMS delivery performance for many users, with regional variations and ongoing maintenance windows during the event.

The Twilio Marketplace Add-Ons feature experienced a brief degradation lasting about 35 minutes. The issue centered on Marketplace add-ons not functioning as expected and affected the Programmable Voice / Recording component. Users attempting to access or use add-ons may have encountered failures or degraded behavior during the incident. The status page first indicated an investigation at May 28, 2025 11:27 AM UTC with an expectation of an update within about one hour, and the problem cleared later the same day as the component returned to normal at May 28, 2025 12:02 PM UTC after two official updates were issued.

Twilio experienced an extended disruption affecting SMS delivery and related services due to scheduled maintenance across multiple carrier networks. The incident began on May 27, 2025 2:07 PM UTC with carrier maintenance and progressed to include delays for messages sent to Claro Brazil, intermittent issues with the WhatsApp sign-up flow, and a temporarily inaccessible Twilio Blog page. The disruption impacted multiple components across regions including Voice, SMS, and various identity and onboarding services, with degraded performance spanning roughly 21 hours before restoration was reported. The incident was resolved by May 28, 2025 11:07 AM UTC as updates indicated broader recovery across affected parts.

Twilio experienced SMS delivery delays affecting messages sent to MTN Nigeria, with broader delays reported across multiple carrier networks in the United States and other regions. The incident began at 2:12 PM UTC and stretched across the evening and into the next day, with gradual recovery in several regions and ongoing monitoring through 7:12 AM UTC. Users likely observed longer delivery times for SMS and intermittent delivery issues during the peak of the incident. The disruption affected a wide set of carrier networks and messaging components, spanning Africa, Europe, and North America, as well as related Programmable Messaging and Conversations capabilities.

Twilio experienced widespread delays and partial outages affecting SMS delivery across a broad set of carrier networks worldwide beginning with a maintenance window on 8:02 PM UTC. Over the next day, users reported delays and occasional failures delivering SMS and MMS to networks including MTN in Guinea-Bissau, T-Mobile in the United States, KPN in the Netherlands, and Telenet in Belgium, among others. The incident involved multiple carrier networks and provisioning services, with Twilio engineers coordinating with partners to investigate and mitigate the impact. The status page shows a sequence of maintenance notices and investigation updates across SMS, Short Code, Long Code, and MMS components.

Updates through May 23–25 describe ongoing recovery efforts and continued degradation on several routes, with some paths returning to normal and others remaining unreliable. By 7:07 AM UTC the REST API related components had moved back to an up state, indicating partial service restoration, though carrier-level conditions were still variable. The incident reflects broad carrier-level disruption spanning APAC, Europe, the Americas, and Africa, and demonstrates how messaging delivery can be selectively degraded even as some services recover.

Twilio experienced a brief call failure impacting subscribers attempting to reach Denmark Twilio numbers in Europe. The issue affected the CARRIER NETWORK / Voice, Europe component and caused degraded calling functionality. The outage began at May 22, 2025 6:32 PM UTC and was resolved by May 22, 2025 7:37 PM UTC, lasting about 1 hour and 5 minutes. The provider issued 2 status updates during the incident, noting an investigation with the carrier partner and subsequent restoration of calling capability.

The outage affected SMS delivery, MMS, and voice across carrier networks and Twilio's messaging platforms. The incident began on May 5, 2025 12:22 AM UTC with Indonesia API errors and quickly expanded to include SMS delivery failures and carrier maintenance across regions worldwide. The issue persisted for more than six days and remained active through May 11, 2025 7:02 AM UTC with ongoing updates.

Twilio's status page documented a long sequence of updates, investigations, and maintenance across dozens of components, including CARRIER NETWORK / SMS, Voice, MMS, and related Twilio services. The updates describe problems such as SMS delivery delays and failures, call failures, and configuration challenges, with new maintenance windows and recoveries reported across North America, Europe, APAC, and other regions as engineers and carrier partners worked to restore services.

Impact was broad, with degraded messaging and calling experiences for customers relying on Twilio's SMS, MMS, and voice services. The incident involved multiple carrier partners and many Twilio components, and remained under active investigation and recovery in the latest updates, signaling a widespread disruption across global communications.

Twilio experienced a multi-region incident beginning May 3, 2025 12:52 PM UTC with elevated HTTP 500 errors for the Quota API that affected Flex Billing, impacting Flex customers. Shortly after, SMS delivery delays were reported to MegaFon in Russia and API errors affected the Verify service in Indonesia. A separate carrier-network maintenance event in the UK also impacted identity matching components. The issues affected multiple Twilio services, including the Flex Application Platform, REST API, Flex Billing, and carrier-network messaging and identity services, with delays and intermittent problems observed in Russia, Indonesia, and the UK.

Twilio published multiple status updates as the incident unfolded. By May 3, 2025 8:07 PM UTC, Flex Platform, REST API, and Flex Billing had begun to recover to normal operation. Indonesia Verify issues continued, and by May 4, 2025 2:47 AM UTC the related Legacy Identity Match and Lookup Identity Match components had progressed to up. The UK carrier maintenance continued alongside these recoveries, and final verification showed Verify returning to full operation by May 4, 2025 5:47 AM UTC. Overall, the incident involved eight official updates and affected several components across APAC and EMEA regions, signaling a broad impact across Twilio's platform.

Twilio faced two concurrent issues: SMS delivery delays to Telefonica's network in Chile via domestic long codes, and delays in voicemail transcription through VoiceBase. The SMS problem affected messaging in Latin America, with outbound SMS to Chile delayed while engineers worked with the carrier partner to resolve the issue. The voicemail transcription delays impacted transcription of voicemail messages in Programmable Voice. The SMS disruption began at May 2, 2025 8:57 PM UTC and was resolved by May 3, 2025 12:12 AM UTC; the transcription delays began at May 2, 2025 9:27 PM UTC and were resolved by May 2, 2025 10:37 PM UTC.

Twilio posted several status updates as the incident unfolded, noting the SMS delays first and later transcription delays, with a final update confirming recovery. The Latin America SMS route returned to normal by May 3, 2025 12:12 AM UTC and VoiceBase transcription services were restored by May 2, 2025 10:37 PM UTC.

Twilio experienced an SMS delivery outage affecting multiple US networks via a subset of long codes during scheduled carrier partner maintenance. Messages to US networks, including Verizon, were failing for a period as the maintenance proceeded. The incident began at May 2, 2025 8:02 AM UTC and was resolved by May 2, 2025 7:57 PM UTC.

The provider issued four official updates during the incident: the initial maintenance notice at May 2, 2025 8:02 AM UTC, followed by updates at May 2, 2025 10:27 AM UTC and May 2, 2025 12:02 PM UTC as issues persisted, and a final resolution at May 2, 2025 7:57 PM UTC. The affected components included ZIPWHIP MESSAGING / SMS Long Code, North America and CARRIER NETWORK / SMS Short Code, North America.