Delayed email sending
Follow-up: the impact was wider than we reported at the time. Between 16:41 and 17:05 UTC, roughly 9,200 transactional emails were accepted by our API and then held before delivery, by up to 25 minutes. This came from a database issue caused by the action we took to clear the broadcast backlog. All of those emails were delivered and none were lost. Some customers also saw errors loading email details or lists during the same minutes.
The latest update from Resend.
State
Resolved
Started
47 d ago
2026-09-15 15:49 UTC
Lasted
1 h 20 min
until 2026-09-15 17:09 UTC
Worst impact
Partial outage
Timeline
4 updatesIdentified
33 min 42%
Monitoring
46 min 58%
Updates
Times in UTCAs posted by Resend
Follow-up: the impact was wider than we reported at the time. Between 16:41 and 17:05 UTC, roughly 9,200 transactional emails were accepted by our API and then held before delivery, by up to 25 minutes. This came from a database issue caused by the action we took to clear the broadcast backlog. All of those emails were delivered and none were lost. Some customers also saw errors loading email details or lists during the same minutes.
Broadcast sending is fully recovered and the backlog has cleared. All broadcasts delayed during this incident have been sent or are sending normally. No emails were lost and no action is required.
Broadcast sending has recovered and the queued backlog is draining. Broadcasts that were delayed are sending now. No emails were lost and no action is required: affected broadcasts continue automatically and do not need to be resent. We are monitoring until the backlog is fully clear.
We are investigating delays in broadcast sending. Broadcasts started after 15:05 UTC may stay in a queued state and make little or no progress. No emails have been lost. Affected broadcasts remain queued and will continue sending once the backlog clears. We have identified the cause and are working on a mitigation. Next update in 30 minutes.
Resend in the last 90 days
Full historyIncidents in 90 days
18
Days with an incident
21
Median duration
39 min
This incident
2.1× 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