Stytch: Gmail incident - delayed emails

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-01-24 13:02 UTC and 2026-01-24 13:02 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.

resolvedJan 24, 2026, 1:02 PM UTC
Type: Incident Duration: 14 hours and 29 minutes Affected Components: Message deliverability Jan 25, 03:30:57 GMT+0 - Resolved - This incident has been resolved. Jan 24, 21:12:10 GMT+0 - Monitoring - Reports of delivery issues has dropped but is still not back to normal. We're continuing to monitor. Jan 24, 17:22:06 GMT+0 - Monitoring - Continuing to monitor. Jan 24, 13:02:00 GMT+0 - Investigating - Gmail is currently experiencing an incident that is causing delayed emails for end users. You can follow along with their incident here: We'll be monitoring and will resolve this incident when we've confirmed delivery returns to normal for Gmail users.
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-01-24 13:02 UTC. For Stytch's live state, see https://down.guide/stytch.

How long did it last?

0m, from 2026-01-24 13:02 UTC to 2026-01-24 13:02 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.