Twilio: 503 Errors When Calling Comms-API
Timeline of updates
- resolved
Starting on 2026-09-16 ~19:00 UTC customers were experiencing 503 errors while calling comms-api messages endpoints. 128 requests took 1 minute and eventually got failed by the timeout. After 19:30 there were no 503 errors observed anymore but the root cause of the issue is unclear.
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: none) posted by Twilio, started 2026-09-17 15:57 UTC, resolved after 0 min, 1 update(s).
- Title
- 503 Errors When Calling Comms-API
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/h99llnp6l6y4
Twilio profileRecent Twilio incidentsAll outages on September 17, 2026Twilio in September 2026MarkdownJSON