Twilio Outage History

Twilio customers experienced issues retrieving Debug Events, affecting the Debugger & Alarms components for 1.3 hours. The service began recovering and was fully restored to normal operation.

Twilio experienced SMS delivery receipt delays from a subset of Long Codes to multiple small networks in the United States, though message delivery itself continued to succeed. The issue affected SMS Long Code services in North America for 4.9 hours. The service was restored after monitoring showed recovery of delivery receipts, and the incident was resolved.

Twilio's User Authentication Identity API experienced high latency specifically for Verizon customers in the United States, affecting Lookup SIM Swap and Legacy Identity MatchAndAttributes services. The incident lasted 6.9 hours, during which customers would have experienced slower response times when using authentication services for Verizon phone numbers. Twilio identified the root cause and resolved the latency issues after monitoring service recovery.

Twilio experienced SMS delivery delays to Liberty Mobile network subscribers in Puerto Rico for 4.4 hours. The issue affected Twilio's SMS service in the Latin America region, preventing timely message delivery to users on the Liberty Mobile network. Twilio engineers worked with their carrier partner to resolve the problem, and SMS delivery returned to normal operation.

Twilio experienced a retroactive issue affecting Marketo cloud sources on their production environment for 26 minutes. Engineers investigated the customer impact of this minor incident. The issue was resolved and moved to monitoring status.

Twilio customers experienced post dial delays when making voice calls from Twilio phone numbers to subscribers in the United States, affecting the Voice service in North America. The issue caused delays in call connection after dialing, impacting call quality and user experience. The problem was resolved after 3.4 hours of investigation and monitoring.

Twilio's User Authentication Identity API experienced errors in Indonesia, affecting the Verify Silent Network Auth component for 3.3 hours. Customers in Indonesia were unable to properly authenticate users through the API during this period. The service was restored to normal operation after the team identified and resolved the underlying issue.