Twilio Outage History

Twilio experienced inbound call failures through the Telefonica carrier in Germany, affecting Voice services in Europe. The issue was detected by monitoring systems and investigated by engineers. The incident was resolved after 22 minutes.

Twilio's Knowledge API calls failed when accessed through the Python SDK and Package, affecting the REST API component for 1.4 hours. The issue prevented successful API calls to knowledge.twilio.com for Python SDK users. Twilio resolved the incident and released a minor version fix to restore full functionality.

Twilio experienced SMS delivery delays for messages sent from certain alphanumeric sender IDs to Orange network subscribers in Botswana, lasting approximately 3.9 hours. The issue affected Twilio's SMS service in the Middle East & Africa region, causing delayed message delivery to this specific carrier and geographic combination. The team identified the root cause and successfully resolved the incident, with SMS delivery returning to normal operations.

Twilio experienced SMS delivery delays and failures for messages sent from Twilio phone numbers to Telekom Srbija network subscribers in Serbia for 4.5 hours. The issue affected SMS services in the Europe region, preventing reliable message delivery to users on the Serbian carrier network. The incident was resolved after monitoring showed recovery in SMS delivery performance to the affected network.

Twilio's User Authentication Identity Gateway API experienced increased failures and high latency specifically for T-Mobile users in the United States, affecting the Lookup SIM Swap and Legacy Identity MatchAndAttributes components. The incident lasted 1.5 hours before service was restored to normal operation.

Twilio experienced increased API failures in their User Authentication Identity Gateway for the PacificEast region in the United States, affecting the Lookup Identity Match and Legacy Identity MatchAndAttributes components. The incident lasted 3.2 hours, during which customers experienced service disruptions with these authentication services. The team identified the root cause and successfully resolved the issue, restoring normal operations.

Twilio investigated reports of customers being unable to select addresses from a dropdown menu during phone number purchases in the Twilio Console. The issue affected the phone number purchasing process for approximately 1.4 hours. The incident was ultimately determined to be a false positive, with all services operating normally.

Twilio experienced a 2.8-hour incident where customers were not receiving RCS messages from iOS users in conversation threads older than a few minutes, with messages failing to arrive until an outbound message was sent first. The issue was identified as a third-party vendor problem affecting inbound RCS message delivery specifically for iOS devices. Engineers implemented a fix through the vendor and confirmed full service restoration after monitoring the recovery.

Twilio's monitoring systems detected a potential issue with their Flex service, prompting an immediate engineering investigation. The incident affected a small subset of customers who were individually contacted regarding the impact. The issue was fully resolved within 20 minutes with all systems returning to normal operation.

Twilio experienced intermittent call failures when attempting to connect voice calls to multiple networks in Spain, affecting their Voice service in the Europe region. The issue lasted 6 hours while engineers worked with carrier partners to resolve the connectivity problems. Service was restored to normal functionality after monitoring confirmed full recovery from the call failures.