Twilio Outage History

Twilio experienced a phone number porting issue affecting both their console and API for 2.4 hours. The incident prevented users from successfully porting phone numbers through either interface. Engineers resolved the issue and confirmed full recovery of the phone number porting service.

Twilio experienced SMS delivery delays to Digitel network subscribers in Venezuela for 10.9 hours. The issue affected SMS services in the Latin America region, causing delayed message delivery for customers sending to this specific carrier network. Service recovery was observed and monitored before full resolution was confirmed, with SMS delivery returning to normal operations.

Twilio experienced SMS delivery failures from a subset of short codes to Verizon network subscribers in the United States, affecting the SMS Short Code service in North America. The incident lasted 8 minutes and was classified as minor. The team actively investigated the issue during the outage period.

Twilio experienced a latency issue with Intelligent Alerts that caused customers to receive notifications with approximately 1-hour delays. The incident affected the Messaging Insights component and lasted 4.1 hours. The issue was resolved after the team identified and fixed the underlying problem causing the notification delays.

Twilio experienced network degradation between regions that impacted voice calls, video sessions, and webhooks for 8.4 hours. The incident affected multiple components including Group Rooms, PSTN, SIP Interface, Client Web, Client Mobile, and Conference services, causing call quality issues and dropped webhooks for traffic traversing between regions. The cross-region connectivity issues were resolved and services returned to normal operation.

Twilio experienced increased failures in User Authentication Identity Silent Network Auth (SNA) specifically for T-Mobile users in the United States, affecting the Verify Silent Network Auth and Lookup SIM Swap services. The incident lasted 6 hours, during which customers likely encountered authentication failures when attempting to verify T-Mobile phone numbers. Twilio identified the root cause and restored normal service operations after monitoring the recovery.

Twilio experienced SMS delivery delays to Orange network subscribers in Cameroon, affecting customers sending messages to that specific carrier and region. The incident lasted 5.6 hours, during which SMS messages were delayed rather than completely blocked. The issue was identified, monitored during recovery, and ultimately resolved with normal SMS delivery restored.

Twilio experienced SMS delivery failures to Digicel network subscribers in the Cayman Islands for 6.6 hours. The issue affected Twilio customers attempting to send SMS messages to recipients on the Digicel network in that region. The team identified the root cause and implemented a fix, with service recovery observed before full resolution was confirmed.

Twilio experienced a 4-hour service interruption affecting Messaging Logs, which caused delays in new message logs appearing and made them unavailable for querying, while some Message Logs API queries returned HTTP 5xx errors. The incident impacted MMS, SMS, and Messaging Insights components, though message sending functionality remained fully operational throughout the outage. The engineering team deployed a fix and restored normal operations to all affected services.

Twilio experienced an 8.9-hour service degradation that affected multiple products including SMS, Voice, Flex, Sync, and other core services, initially triggered by errors in the Sync service and causing intermittent 5xx API errors and higher than normal latency. The incident impacted a wide range of Twilio's platform including messaging, voice, billing, console access, and customer support tools. All services began recovering and were fully restored to normal operation.