Skip to main content
Twilio

Notify SMS Requests Failed With 500s Errors if the Request Landed on OTK Pods

Degraded Lasted 0m · started · Twilio's page

Level
confirmed
Worst impact
Degraded
Components
Notify
Down Index
8of 100

What to do

  • Check whether you use Twilio Notify. 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-05-12 13:41 UTC and 2026-05-12 13:41 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

    Notify SMS was degraded between 05/06/2026, 23:00 and 05/11/2026, 7:00 Pacific Time. During this period of time customers may have experienced Notify: SMS requests not getting delivered to users. The issue has now been 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-4e9ca14e18

Is Twilio still down?

No, this incident was resolved 2026-05-12 13:41 UTC. For Twilio's live state, see https://down.guide/twilio.

How long did it last?

0m, from 2026-05-12 13:41 UTC to 2026-05-12 13:41 UTC, by the times Twilio posted.

What was affected?

Twilio named Notify.

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.