Elevated HTTP 400 Errors for Programmable Messaging

Incident Report for Twilio

Resolved

Our investigation concludes that these elevated HTTP 400 errors were legitimate responses triggered by the traffic behavior of a small subset of customers. Programmable Messaging API has been operational since the resolution of the API incident: https://status.twilio.com/incidents/ztxfwntyhgqd. The incident is now resolved.

Posted Dec 10, 2021 - 17:16 PST

Monitoring

Between 12:35PM PT and 3:21PM PT, Twilio experienced elevated rate of HTTP 400 errors for Programmable Messaging. The root cause is still to be identified but the error rate has resumed back to normal level in the past 30 minutes. We will continue to investigate the root cause and monitor our traffic for the next 2 hours and provide an update as soon as more information becomes available.

Posted Dec 10, 2021 - 16:09 PST

Update

We are continuing to investigate the elevated HTTP 400 issue for Programmable Messaging. Customers may see a subset of API requests returning with HTTP 400 error. Please retry these requests as a workaround. We will provide another update within an hour or as soon as we have more information to share.

Posted Dec 10, 2021 - 15:24 PST

Investigating

Our monitoring system shows elevated HTTP 400 errors for Programmable Messaging, which is believed to be related to the API incident that was resolved earlier: https://status.twilio.com/incidents/ztxfwntyhgqd. Our engineering team is actively investigating and we will provide an update as soon as we have more information.

Posted Dec 10, 2021 - 15:07 PST

This incident affected: PROGRAMMABLE MESSAGING (SMS).