- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 100
What to do
Check whether your product depends on Resend. 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 43m it lasted.
Anything that failed between 2026-08-08 21:46 UTC and 2026-08-08 22:29 UTC may need a replay.Subscribe to Resend's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=resend works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Resend 2
- identified
Our team has identified an issue causing intermittent error rates across our APIs and SMTP services. The impact is currently affecting email sending requests, which may result in intermittent 500 errors for some customers. We are actively working on mitigation and will provide further updates as we make progress.
provider
- resolved
Our team has mitigated the issue and this incident is fully resolved. All services are operational.
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-dfc97720a8
Is Resend still down?
No, this incident was resolved 2026-08-08 22:29 UTC. For Resend's live state, see https://down.guide/resend.
How long did it last?
43m, from 2026-08-08 21:46 UTC to 2026-08-08 22:29 UTC, by the times Resend posted.
What caused it?
Resend hasn't published a root cause. If it does, it shows here.
Where does this come from?
Resend's official status page, https://resend-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.