Contact webhook events are delayed in delivery
We have resolved the underlying issue and service has been resumed.
The latest update from Resend.
State
Resolved
Started
75 d ago
2026-08-18 19:53 UTC
Lasted
14 h 9 min
until 2026-08-19 10:01 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
1 h 19 min 9%
Identified
1 h 21 min 10%
Monitoring
11 h 29 min 81%
Updates
Times in UTCAs posted by Resend
We have resolved the underlying issue and service has been resumed.
We have processed more than 66% of the backlog at this point. Within the next hour, the backlog will be fully processed, and this incident will be marked as resolved.
We are still monitoring the progress on processing the backlog. The impact has been reduced from a peak 3-hour delay in delivering a contact webhook to 2h 20 min. The delay is being reduced further as we process the backlog. Within 2-3 hours, the backlog will be completely processed.
A fix has been deployed to the underlying infrastructure and we can now confirm we're processing the backlog with the correct volume. Delayed webhooks are now being delivered. We will post another update in 30 minutes to share more about the progress on processing the backlog.
We have identified the issue and are working on mitigating its effects. The volume of contact webhooks processed over time was affected by an infrastructure change, and now we have an increasing backlog of contact webhooks to process. The team is working on increasing the speed of processing the backlog. No contact webhooks were lost.
We are currently investigating increased latency in contact webhook delivery. We have noticed a delay of approximately 50 minutes in sending webhooks related to contact events. The team is investigating and mitigating this processing delay issue. Contact management via dashbaord and its API are not affected.
Resend in the last 90 days
Full historyIncidents in 90 days
18
Days with an incident
21
Median duration
39 min
This incident
22× the median
Other Resend incidents
All incidentsResend·Delayed email status updates
Email status updates are processing normally again. All delayed updates have been delivered, and no data was lost.
Resend·Intermittent latency spikes on our emails API
We have resolved the underlying issue and service has been resumed.
Resend·Delayed new team provisioning and contact webhook delivery
We have resolved the underlying issue and service has been resumed.
Resend·Delayed new team provisioning and contact webhook delivery
We have resolved the underlying issue and service has been resumed.
Resend·Resend API with elevated error rate
We have resolved the underlying issue and service has been resumed
Follow Resend
Your coding agent knows when Resend is down, and tells you when a failure is theirs, not yours. You can also get Resend incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "resend" and tell me if Resend has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=resend/feed subscribe https://outages.cc/feed.xml?providers=resendFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane