Twilio incident: Elevated Rate of Http 503s When Sending Messages Using the Programmable Messaging Api

1. resolvedAug 17, 2026, 22:07 UTC

   Between 13:25 PST and 13:27 PST, customers may have received an elevated rate of HTTP 503s when sending messages via the Programmable Messaging API. The issue has been resolved.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• SendGrid: SMS Delivery Failures from Twilio to Telemat Cel BrazilMinor · Aug 15, 2026, 12:55 UTC
• HashiCorp Vault: Delayed HCP Terraform RunsMinor · Aug 15, 2026, 17:08 UTC
• SendGrid: Service Disruption: Inbound Voice Calls to France Numbers and Frankfurt InterconnectMinor · Aug 16, 2026, 20:28 UTC
• SendGrid: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to IraqMinor · Aug 16, 2026, 23:36 UTC
• SendGrid: User Authentication Identity SNA Failure Increase for AT&T in United StatesMinor · Aug 17, 2026, 18:54 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Tailscale: Coordination service performance issuesMinor · Aug 17, 2026, 20:27 UTC

How often does Twilio have incidents?

Twilio reported 501 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 49m. See Twilio's uptime and incident history