Incident History

We are no longer experiencing SMS delivery delays and failures from Twilio to Vietnamobile network subscribers in Vietnam. This incident has been resolved.

We are no longer experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to network subscribers on multiple networks in the United States. This incident has been resolved.

The incident has been resolved and SMS delivery from Twilio to Orange network subscribers in Cameroon is operating normally.

We are no longer experiencing SMS delivery delays from a subset of Twilio Short Codes to Algar network subscribers in Brazil. This incident has been resolved.

The issue preventing 'Auto Recharge Successful' emails from sending has been resolved and Auto Recharge emails are operating normally at this time.

Twilio Programmable Messaging API was partially degraded for 3 minutes between 04:52 and 04:54 Pacific Time on 03/27/2026. During this period of time customers may have experienced elevated latency in API response time. The issue has now been resolved.

We are no longer experiencing intermittent TCP connectivity issues affecting inbound and outbound SMPP connections within our IE1 region. This incident has been resolved and service is operating normally.

The incident has been resolved and SMS delivery from a subset of Twilio Short Codes to Liberty Mobile network subscribers in Puerto Rico is operating normally.

The issue affecting voice calls from network subscribers to Twilio Spain Phone Numbers has been resolved, and the service is functioning normally at this time.

Twilio Voice ConversationRelay was degraded for 1 day 18 hours and 54 minutes between 18:29 Pacific Time on 03/24/2026 and 13:23 Pacific Time on 03/26/2026. During this period, ConversationRelay sessions could intermittently fail to terminate when the WebSocket Application sent an end message while still streaming text-to-speech tokens. If all tokens completed before the end message, the session terminated normally. However, if the end message arrived mid-stream, the remaining tokens were discarded and the session entered a state where it could not complete. Affected calls remained silent until the caller hung up or a 60-second safety timeout fired. In both cases, the callback did not receive the end message's handoff data, preventing call transfers from completing. The issue has now been resolved.