503 Errors When Calling Comms-API
Sep 17, 15:57 UTCSep 17, 15:57 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Twilio, 90 days
554 incidents
Affected
SMSPROGRAMMABLE MESSAGING - SMS
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
- 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| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2503:49 UTC | SMS Delivery Delays from Twilio to Claro Brazil | minor | Ongoing |
| Sep 2502:24 UTC | SMS Delivery Delays from a Subset of Twilio Short Codes to Cellularone NE Arizona United States | minor | Ongoing |
| Sep 2420:40 UTC | Event Streams Service Disruption | minor | 5h 44m |
| Sep 2417:55 UTC | SMS Delivery Receipt Delays from a Subset of Twilio Alphanumeric Sender IDs to Ooredoo Algeria | minor | Ongoing |
| Sep 2417:19 UTC | Some Transfer Calls in Elastic SIP Trunking Failing With Error Code 32204 | minor | 43m |
| Sep 2416:22 UTC | Link Branding Creation Fails with HTTP 500 Internal Server Error (Auto SSL Enabled) | minor | 2h 4m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.