Skip to main content
Twilio

Studio Timeout Functionalities Are Degraded Potentially Causing Stuck Executions

Degraded Lasted 1h 33m · started · Twilio's page

Level
confirmed
Worst impact
Degraded
Components
Studio
Down Index
18of 100

What to do

  • Check whether you use Twilio Studio. 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 1h 33m it lasted.

    Anything that failed between 2026-07-29 20:55 UTC and 2026-07-29 22:28 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. investigating

    Our monitoring systems have detected a potential issue with Studio Timers failing to schedule causing workflow failure. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

    provider

  2. investigating

    We are investigating a small number of Send & Wait for Reply widgets in studio are failing to take the no reply transition, also a small number of add Twiml redirect widgets in studio are failing to take the timeout transition.. We expect to provide another update in 1 hour or as soon as more information becomes available

    provider

  3. resolved

    The issu about Studio Timers failing to schedule causing workflow failure has been resolved and it is operating normally at this time.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-f7992b9e49

Is Twilio still down?

No, this incident was resolved 2026-07-29 22:28 UTC. For Twilio's live state, see https://down.guide/twilio.

How long did it last?

1h 33m, from 2026-07-29 20:55 UTC to 2026-07-29 22:28 UTC, by the times Twilio posted.

What was affected?

Twilio named Studio.

What caused it?

Twilio hasn't published a root cause. If it does, it shows here.

Where does this come from?

Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.