The Twilio Programmable Messaging API was partially degraded for 9 minutes on July 14th, 2026 between 05:58 PST and 06:07 PST. During this period of time, customers sending an outbound message may have received elevated volumes of 5xx's in API responses. This issue has now been resolved.
We have resolved an issue where updating an account name could cause the SSL certificate validation setting to be disabled, temporarily impacting secure connectivity for some accounts. Our systems are now functioning normally, and we are actively working to restore the original SSL configurations for all affected accounts.
We have fully investigated the issue when attempting to add newly purchased phone numbers to their SIP Trunks triggered by our automated alert, and it was determined that there is no noticeable customer impact. All systems are operational.
The issue with unexpected status updates causing message send failures has been resolved and Direct Send WhatsApp templates are operating normally at this time.
The incident has been resolved and SMS delivery from Twilio to Liberty Mobile network subscribers in Puerto Rico is operating normally.
The incident has been resolved and SMS delivery from Twilio to network subscribers in the United States is operating normally.
The incident has been resolved and SMS delivery from a subset of Twilio Alphanumeric Sender IDs and Long Codes to XL Axiatia network subscribers in Indonesia is operating normally.
The incident has been resolved and SMS delivery from a subset of Twilio Short Codes to network subscribers on affected networks in India is operating normally.
The incident has been resolved and SMS delivery from Twilio to MTN network subscribers in affected countries is operating normally.
The incident has been resolved and SMS and MMS delivery from Twilio to T-Mobile network subscribers in the United States are operating normally.