API logs are delayed
API request logs had increased latency in Resend and could appear up to 15 minutes late. Resend reported that the issue is resolved and lasted about 62 minutes.
State
Resolved
Started
Lasted
1 h 2 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
56 min 90%
Monitoring
6 min 10%
Updates
Times in UTCAs posted by Resend
This issue is now resolved.
A fix is in place and the delay to persist API request logs is reducing. We are monitoring to ensure this issue is resolved.
We are currently investigating increased latency in persisting API request logs. They can appear up to 15 minutes late. No data has been lost, and all API endpoints are responding normally.
Resend in the last 90 days
Full historyIncidents in 90 days
15
Days with an incident
18
Median duration
49 min
This incident
1.3× the median
Other Resend incidents
All incidentsResend·Microsoft 365 Incident
Email delivery to Microsoft-hosted inboxes was degraded. Resend reported that Microsoft 365 was not accepting mail normally. Resend retried affected emails automatically. The incident is resolved and lasted about 24 hours.
Resend·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.
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.live/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.live/feed.xml?providers=resend/feed subscribe https://outages.live/feed.xml?providers=resendFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane