Twilio is a critical cloud communications platform that powers messaging, voice, video, and authentication features in thousands of applications and services.

Like any cloud service, Twilio isn’t immune to downtime. From degraded SMS delivery to widespread API disruptions, a single Twilio outage can cascade into failed user verifications, broken customer notifications, and app failures.

That’s why it’s vital to stay ahead of outages and issues with tools that go beyond Twilio’s official status page. StatusGator enables teams to monitor Twilio’s current status, receive real-time outage alerts, and access the complete Twilio outage history dating back several years.

We will review a few notable Twilio incidents over the years. Let’s dive in.

April 30, 2025 – Console Errors and Widespread SMS Delivery Delays

On April 30, 2025, Twilio experienced a series of simultaneous service issues that impacted both its platform and global messaging infrastructure.

Twilio Console Navigation Errors

Beginning around 09:22 UTC, users encountered elevated 5XX errors affecting navigation within the Twilio Console. The disruption degraded the experience for developers attempting to access critical tools and features. Twilio engineers quickly began investigating and observed signs of recovery by 09:57 UTC, transitioning the issue to monitoring status.

SMS Delivery Delays Across Multiple Regions

Throughout the day, Twilio reported SMS delivery delays across a wide range of global networks, including:

• France (Bouygues Telecom)
  
• Paraguay (Personal Network)
  
• United Kingdom (H3G Network via subset of numbers)
  
• Philippines (Smart)
  
• Chile (Telefonica via long codes)
  
• China (China Unicom)

Each incident was attributed to delivery delays, with Twilio teams working in collaboration with carrier partners to resolve the issues. Some regions, like Chile and Paraguay, experienced extended delays requiring multiple updates throughout the day.

Customer Support Center and Zendesk Issues

Additionally, a separate issue emerged involving duplicate support tickets being generated in Zendesk, Twilio’s support platform. Customers were advised not to submit multiple tickets while engineering teams implemented a fix.

Carrier Maintenance

In the midst of these issues, Twilio also conducted scheduled carrier maintenance affecting SMS delivery to multiple destinations in the Middle East and Africa, adding complexity to ongoing investigations and resolutions.

This multi-region, multi-service day of incidents highlights the interconnected nature of Twilio’s communications platform and the challenges of maintaining real-time services across global carrier networks.

October 7, 2024 – Twilio Console Access Issue for Sender ID Registration

On October 7, 2024, Twilio experienced a disruption affecting its Alphanumeric Sender ID registration page within the Twilio Console. 

Starting at approximately 05:17 UTC, users were unable to access the registration interface, preventing them from managing or submitting Sender ID requests.

Twilio acknowledged the issue and began investigating around 22:15 PDT on October 6. Although the incident primarily impacted user access within the Console, it was marked as a platform-level disruption.

The issue was resolved by 10:07 UTC, coinciding with a planned Mexico SMS carrier maintenance event (AT&T). While the two events occurred around the same time, Twilio categorized the maintenance separately and did not indicate a direct connection between the access issue and the carrier work.

This outage underscores the potential operational impact of even partial Console disruptions on businesses managing sender compliance and messaging delivery.

July 17, 2024 – Twilio Help Center Outage

On July 17, 2024, Twilio experienced a significant outage affecting its Customer Support Center, rendering the Twilio Help Center inaccessible to all users.

The incident began at 15:47 UTC, when the service status changed from up to down. During this time, customers were unable to access the Help Center or open new support tickets.

Twilio acknowledged the issue and stated that their engineering team was actively investigating. Approximately 10 minutes later, at 15:57 UTC, the status shifted from down to warn, indicating partial recovery and ongoing monitoring.

Full service restoration was confirmed at 16:57 UTC, when the status returned to up.

This disruption coincided with a scheduled maintenance event involving a U.S. carrier partner (AT&T) related to Twilio’s Account Security services. While no direct link was confirmed, the overlap raised concerns about potential dependencies or side effects from the maintenance activity.

Additionally, on the same day, Twilio reported SMS delivery delays to the Zain Network in Jordan, further highlighting multiple simultaneous issues affecting the platform.

February 21–22, 2024 – Twilio Outage During Maintenance

On February 21, 2024, beginning around 7:01 PM PST, Twilio initiated scheduled maintenance across various SMS services. This included SMS in Latin America, North America (Short Code and Long Code), and the Middle East & Africa, particularly focused on partnerships with AT&T and Movistar. While these events were initially routine, issues escalated over the following hours.

By 10:43 PM PST, delivery delays were reported to the Movistar network in Peru, prompting a service status shift from maintenance to warn for Latin America SMS. Twilio engineers began investigating in collaboration with the affected carrier.

At around 10:26 PM PST, Twilio’s Flex Application Platform and TaskRouter services experienced service interruptions tied to a “Low create meeting 2xx” issue in Flex Orchestrator, triggering warnings across the Flex platform.

Throughout February 22, Twilio also experienced SMS delivery degradation to the Telenor network in Pakistan and intermittent service failures to EE UK for Account Security-related transactions. These issues were actively investigated and monitored, with some gradually returning to operational status.

By early morning on February 22, additional delivery delays surfaced in the United States. They affected SMS, MMS, and Verify API traffic to AT&T’s network.

These disruptions impacted a broad range of messaging types, namely Short Code, Long Code, Toll-Free, and Account Security. These services were marked by ongoing warnings across North America. Engineers worked with AT&T to identify and resolve the underlying causes.

To compound the impact, Twilio’s Super SIM service (Internet of Things) also reported potential issues late in the incident window, marking an expansive impact across multiple Twilio service areas.

Impacted services

• SMS delivery delays across Latin America, Pakistan, and the United States
  
• Flex Application Platform disruptions
  
• Account Security API failures for EE UK and AT&T USA
  
• Warnings and degradations affecting multiple carrier routes and regions
  
• Incident duration spanned over 24 hours, with overlapping events under active investigation through February 22.

Twilio’s engineering teams provided frequent updates and continued monitoring to ensure full recovery across affected services.

July 19, 2023 – WhatsApp Disruption Impacts Twilio Messaging Services

On July 19, 2023, Twilio experienced a significant outage affecting Programmable Messaging services, primarily due to a disruption with WhatsApp.

The issue began at 21:07 UTC, causing Twilio’s WhatsApp-related requests to fail and resulting in a down status for its Messaging Services.

Impacted services

• Programmable Messaging: Messaging Services, particularly those leveraging WhatsApp, experienced complete outages and delivery failures.
  
• Flex: The Flex Teams View entered a degraded (warn) state, potentially impacting agent visibility and status accuracy.
  
• Internet of Things (IoT): Super SIM functionality also showed warning-level issues during the incident.

Twilio’s engineering team actively collaborated with WhatsApp’s support to diagnose and mitigate the issue.

Updates were posted regularly, emphasizing that while the majority of messaging traffic had stabilized, a subset of users continued to experience delivery delays during the recovery window.

The full recovery confirmed for Messaging Services on July 20 at 01:37 UTC. Twilio noted that WhatsApp was operating normally again and that they would continue to monitor for stability.

March 28, 2022 – Major Twilio API Outage Disrupts SMS, Voice, Video, and Serverless Services

On March 28, 2022, Twilio suffered a major multi-product outage that affected nearly every critical service in its ecosystem.

Beginning at 13:32 UTC, Twilio’s status dashboard began reporting warn states for a few services, and by 15:37 UTC, many services had gone fully down.

Impacted services

The outage disrupted a wide range of Twilio offerings across key product areas:

• Carrier Network: SMS delivery delays and failures were reported in Yemen (Sabafon) and Bangladesh (Banglalink), as well as short code disruptions in North America and parts of APAC.
  
• Programmable Messaging: SMS, MMS, Notify, and Conversations were affected, leading to delivery delays and failures across multiple regions.
  
• Voice Services: SIP Interface, PSTN, Client Mobile/Web, and Conference features experienced degraded performance or downtime.
  
• Serverless Products: Key services like Studio, Functions, TwiML Bins, Sync, and Assets were unreachable or unstable.
  
• Programmable Video: Issues were reported with Group Rooms, Peer-to-Peer Rooms, Go Rooms, and video recordings.
  
• Flex: Twilio Flex’s Teams View reported false availability statuses, showing offline agents as available.
  
• Account Security: The Verify product was also affected, potentially impacting two-factor authentication flows and identity checks.

Twilio initially posted isolated issue reports about SMS delivery failures to the Sabafon network in Yemen and Banglalink in Bangladesh early on March 28 (PDT).

However, by 08:36 PDT (15:36 UTC), Twilio confirmed that the root cause was a broader issue in Twilio REST API infrastructure, which affected many downstream services.

The company noted that webhook requests were failing, impacting both programmable messaging workflows and serverless functions.

Twilio’s engineering team moved quickly to mitigate the issue, and by 16:47 UTC, most services had returned to operational status. Full recovery was confirmed by 17:12 UTC.

February 23–24, 2021 – Widespread SMS, Voice, and Console Issues Across Twilio Services

Between February 23 and 24, 2021, Twilio experienced a series of significant service disruptions. They impacted SMS delivery, voice services, IoT connectivity, and core platform functionality.

These incidents highlight the interconnected nature of Twilio’s infrastructure and how multiple components can be affected simultaneously.

SMS and Carrier Network Instabilities

The day began with carrier network issues affecting SMS delivery notifications, status callbacks, and short code messaging in North America. 

At 1:02 AM UTC, both SMS delivery reporting and inbound short code messaging went into a warn state as on-call engineers began investigating the issue.

The instability fluctuated throughout the early morning hours with further degradation reported at 1:38 AM UTC, including inbound SMS delays and delivery report issues.

By early morning, regional voice issues surfaced, with inbound call failures reported on a subset of Twilio phone numbers in Mexico. All while Programmable Wireless SIMs in Spain and Italy faced 4G/LTE connectivity issues.

Major API Outage Across Flex, Chat, and Sync

Around 6:32 PM UTC, Twilio experienced a widespread cloud API failure. Sync, Flex, Programmable Chat, and Conversations simultaneously went down due to client timeout errors. These services remained inaccessible for nearly two hours before being restored by 8:17 PM UTC.

Console Access and International SMS Disruptions

At 9:42 PM UTC, Twilio reported a warn status for its Console. The customers were unable to log in due to authentication errors. Simultaneously, Twilio’s SMS services in Europe, the Middle East, and Africa experienced cascading issues, including:

• Delivery failures to Nigerian MTN Network
  
• MMS delays in the US
  
• Duplicate SMS and delayed delivery to UK numbers
  
• SMS delays to Ethiopia’s ETH-MTN network

These issues were resolved gradually through February 24, with final updates posted in the early afternoon UTC.

June 24, 2020 – IBM Watson Add-on Downtime Affects Twilio Voice Transcriptions

On June 24, 2020, Twilio experienced a disruption in its Programmable Voice product. Specifically, Recording Transcriptions relying on the IBM Watson Speech-to-Text status was affected. 

The Twilio status changed from up to down at 7:32 AM UTC, indicating a complete outage of transcription services relying on the Watson integration.

The issue persisted throughout the day and was later downgraded to a warn state by 5:02 PM UTC, reflecting ongoing instability.

In parallel, the Twilio Flex Application Platform status showed a temporary degradation (warn), though it was fully restored to operational by 8:57 PM UTC.

This event highlights how external service dependencies can directly affect Twilio’s service reliability. Monitoring Twilio’s official status page alone may not provide sufficient insight. With StatusGator, users receive real-time alerts and historical visibility into third-party service disruptions that impact platforms like Twilio.

Conclusion

These extended historical incidents illustrate why it’s essential to monitor Twilio status and other cloud services with tools that go beyond the official Twilio status page.

While Twilio published timely status updates, teams relying solely on its official status page may have missed the early indicators or struggled to keep up with rapidly changing service conditions.

With StatusGator, you can proactively track the current status of Twilio, access years of Twilio outage history, and receive unified alerts across all your third-party services, helping your team stay ahead of issues and minimize downtime impact.

As a status page aggregator, StatusGator monitors the Twilio status page along with nearly 6,000 other official status pages from top SaaS providers.

Users gain access to early warning signals, historical service status data, and instant notifications — all in one centralized dashboard. Whether you’re an engineer, DevOps pro, or IT admin, monitoring Twilio with StatusGator means fewer surprises and faster incident response.

Ready to reduce downtime impact? Start monitoring the Twilio official status page and your other dependencies with StatusGator — for free.