Flex Orchestration Service Disruption

What to do

• Check whether you use Twilio Flex Programmable Voice. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 51m it lasted.

  Anything that failed between 2026-08-24 05:30 UTC and 2026-08-24 06:21 UTC may need a replay.

• Subscribe to Twilio's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Twilio 3

1. investigatingAug 24, 2026, 5:30 AM UTC

   We are currently investigating an issue causing elevated 5xx server errors within Flex Orchestration Services, which may result in intermittent errors or dropped voice calls for Flex users. Our engineering team is actively working to identify the root cause, and we will provide another update in 30 minutes or as soon as new information becomes available.

   provider

2. monitoringAug 24, 2026, 5:56 AM UTC

   5xx errors have subsided, and Flex Orchestration Services have returned to normal operation. Our engineering team is continuing to monitor system stability closely, and we will provide a final update in 30 minutes.

   provider

3. resolvedAug 24, 2026, 6:21 AM UTC

   Flex Orchestration Services have returned to normal operation, and 5xx errors affecting voice calls have fully subsided. Voice services are operating as expected, and this issue is now resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.