Skip to main content
Twilio

Retroactive Incident: Verify Settings in Twilio Console Degraded

Degraded Lasted 0m · started · Twilio's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on Twilio. 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 0m it lasted.

    Anything that failed between 2026-08-04 18:15 UTC and 2026-08-04 18:15 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 1

  1. resolved

    On Jul 28th, from 02:03:40 UTC to 02:13:30 UTC, Verify settings in the Twilio Console were degraded. Actions related with template management, webhooks management, geopermissions and fraud guard configuration were unavailable in the US1 region. This incident is now resolved.

    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-887dfb76ee

Is Twilio still down?

No, this incident was resolved 2026-08-04 18:15 UTC. For Twilio's live state, see https://down.guide/twilio.

How long did it last?

0m, from 2026-08-04 18:15 UTC to 2026-08-04 18:15 UTC, by the times Twilio posted.

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.