Increased API and SMTP Error Rates
Our team has mitigated the issue and this incident is fully resolved. All services are operational.
The latest update from Resend.
State
Resolved
Started
85 d ago
2026-08-08 21:46 UTC
Lasted
43 min
until 2026-08-08 22:29 UTC
Worst impact
Partial outage
Timeline
2 updatesIdentified
43 min 100%
Updates
Times in UTCAs posted by Resend
Our team has mitigated the issue and this incident is fully resolved. All services are operational.
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.
Resend in the last 90 days
Full historyIncidents in 90 days
18
Days with an incident
21
Median duration
39 min
This incident
About 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