Twilio: Elevated HTTP 400 Errors for Programmable Messaging
Timeline of updates
- 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 (opens in new tab). The incident is now resolved.
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2021-12-10 23:07 UTC, resolved after 2.1 h, 1 update(s).
- Title
- Elevated HTTP 400 Errors for Programmable Messaging
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/b03p42zr7460
Twilio profileRecent Twilio incidentsAll outages on December 10, 2021Twilio in December 2021MarkdownJSON