Incident History

The incident has been resolved and access to the Twilio Console from Singapore is operating normally.

We have fully investigated the API related issue triggered by our automated alert, and it was determined that there is no noticeable customer impact. All systems are operational.

The incident has been resolved and SMS delivery from a subset of Twilio Long Codes to AT&T network subscribers in the United States is operating normally.

The incident has been resolved and voice calls from a subset of Twilio Phone Numbers to Verizon network subscribers in the United States are operating normally.

Our engineers have investigated and resolved an issue with Messaging Services. From 10:28AM PDT on Tuesday, 7/21/26 to 6:00PM PDT on Friday, 9/4/26, customers may have experienced HTTP 400 responses with Twilio error code 21620 when sending messages through Messaging Services if the media URL parameter contained a comma. The issue has been resolved and all impacted services are operating normally.

The issue for Branded calling inside the Twilio Console has been resolved and it is operating normally at this time.

The incident has been resolved and SMS delivery from a subset of Twilio Long Codes to Claro network subscribers in Brazil is operating normally.

The incident has been resolved and SMS delivery from Twilio Short Codes to network subscribers on affected networks in the United States is operating normally.

The issue affecting the Voice 'Try It Out' feature in the New Twilio Console has been fully recovered. All services are operating normally. This incident is now resolved.

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