- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-08-04 18:45 UTC and 2026-08-01 00:00 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
- investigating
We are currently investigating increased latency in contact-related webhook deliveries. At this time, you may experience delays in receiving contact events on your webhook endpoints.
provider
- monitoring
We are still noticing increased latency in contact-related webhook deliveries. Events can be delayed by up to 8 hours before being delivered. We have identified the issue and implemented infrastructure changes to process the backlog faster.
provider
- resolved
The backlog is gone, and all delayed contact webhooks have been delivered. Delivery latency has now recovered. The new infrastructure configurations prevent this same issue from happening again.
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-23933407e3
Is Resend still down?
No, this incident was resolved 2026-08-01 00:00 UTC. For Resend's live state, see https://down.guide/resend.
How long did it last?
0m, from 2026-08-04 18:45 UTC to 2026-08-01 00:00 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.