- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 34m it lasted.
Anything that failed between 2026-10-10 14:35 UTC and 2026-10-10 15:09 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 3
- identified
We've identified an issue on our infrastructure affecting new team provisioning and contact webhook delivery. Email sending and receiving is not affected. • Newly created teams may take longer to have their account resources fully setup. • Some webhooks related to contact activity are being delivered with a delay. Our team is working on fixing this issue.
provider
- monitoring
A fix is in place and we are monitoring to ensure the issue has been fixed.
provider
- resolved
We have resolved the underlying issue and service has been resumed.
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-a31d1fd7bc
Is Resend still down?
No, this incident was resolved 2026-10-10 15:09 UTC. For Resend's live state, see https://down.guide/resend.
How long did it last?
34m, from 2026-10-10 14:35 UTC to 2026-10-10 15:09 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.