Stytch: Small percentage of SMS requests resulting in 500 errors

What to do

Check whether you use Stytch Message deliverability. 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-09-01 16:30 UTC and 2026-09-01 16:30 UTC may need a replay.
Subscribe to Stytch's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=stytch works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedSep 1, 2026, 4:30 PM UTC
Type: Incident Duration: 57 minutes Affected Components: Message deliverability Sep 1, 17:27:00 GMT+0 - Resolved - This issue has been resolved. Sep 1, 16:30:00 GMT+0 - Investigating - A small percentage of SMS requests are currently resulting in 500 / internal\_server\_errors due to an upstream messaging issue.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Stytch still down?

No, this incident was resolved 2026-09-01 16:30 UTC. For Stytch's live state, see https://down.guide/stytch.

How long did it last?

0m, from 2026-09-01 16:30 UTC to 2026-09-01 16:30 UTC, by the times Stytch posted.

What was affected?

Stytch named Message deliverability.

What caused it?

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

Where does this come from?

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