Skip to content
Twilio · Apps and SaaSSep 17, 2026, 15:57 UTC

503 Errors When Calling Comms-API

InformationalNot disclosedUpdated 20h ago
Sep 17, 15:57 UTCSep 17, 15:57 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Twilio, 90 days
545 incidents
Affected
SMSPROGRAMMABLE MESSAGING - SMS
Status page

Final update

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.

Timeline

  1. Resolved · Sep 17, 15:57 UTC
    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.

More from Twilio

Full history

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.