- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Stytch. 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-01-28 20:23 UTC and 2026-01-28 20:23 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.
Updates from Stytch 1
- resolved
Type: Incident Duration: 4 hours and 51 minutes Jan 28, 20:55:00 GMT+0 - Resolved - This incident has been resolved. Jan 28, 20:23:00 GMT+0 - Identified - Event log streaming and internal logging in the Dashboard were interrupted for approximately 32 minutes. A fix was deployed, and the issue has 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-0c64efe545
Is Stytch still down?
No, this incident was resolved 2026-01-28 20:23 UTC. For Stytch's live state, see https://down.guide/stytch.
How long did it last?
0m, from 2026-01-28 20:23 UTC to 2026-01-28 20:23 UTC, by the times Stytch posted.
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.