Provider
TwilioIncident detail
503 Errors When Calling Comms-API
Resolved incidentMinor1 affected service
Timeline window
to
Get alerted the next time Twilio breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
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.
Keep exploring
More from Twilio
Neighboring incidents on Twilio's timeline and the rest of their record on OutageDeck.
← Older incident
MMS Delivery Failures from a Subset of Twilio Short Codes to Multiple Networks in United States
Newer incident →
SMS Delivery Failures from a Subset of Twilio Long Codes to Orange and Tigo Democratic Republic of the Congo
- A2P 10DLC Campaign Statuses Remaining 'In Review'Minor
- SMS Delivery Delays and Failures From a Subset of Twilio Phone Numbers to Orange Democratic Republic of the CongoMinor
- Delays with Phone Number Registration to A2P 10DLCMinor
- SMS Delivery Delays and Failures From a Subset of Twilio Alphanumeric Sender IDs and Long Codes to Tigo Democratic Republic of the CongoMinor · Active