outages.live
Live
ResendIncident · 2026-08-20 04:58 UTC

Increased latency across API endpoints

ResolvedOfficial update

We have resolved the underlying issue and service latency has been recovered.

The latest update from Resend.

State

Resolved

Started

73 d ago

2026-08-20 04:58 UTC

Lasted

24 min

until 2026-08-20 05:22 UTC

Worst impact

Degraded

Timeline

3 updates
04:5805:0405:1005:1605:22
DegradedUpdate postedTimes in UTC

Investigating

19 min 80%

Identified

5 min 20%

Updates

Times in UTC

As posted by Resend

Resolved2026-08-20 05:22 UTC

We have resolved the underlying issue and service latency has been recovered.

Identified2026-08-20 05:17 UTC

We have identified the issue and deployed a fix. API latency has recovered since then. Our team is still monitoring to ensure it remains stable over the next few minutes.

Investigating2026-08-20 04:58 UTC

We are currently investigating increased latency in non-email sending API endpoints. Our team is investigating it.

Resend in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

18

Days with an incident

21

Median duration

39 min

This incident

38% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 days
median 39 min
90 days agoToday

Other Resend incidents

All incidents

Resend·Delayed email status updates

Email status updates are processing normally again. All delayed updates have been delivered, and no data was lost.

Resolvedresolved 6 d ago

Resend·Intermittent latency spikes on our emails API

We have resolved the underlying issue and service has been resumed.

Resolvedresolved 9 d ago

Resend·Delayed new team provisioning and contact webhook delivery

We have resolved the underlying issue and service has been resumed.

Resolvedresolved 22 d ago

Resend·Delayed new team provisioning and contact webhook delivery

We have resolved the underlying issue and service has been resumed.

Resolvedresolved 23 d ago

Resend·Resend API with elevated error rate

We have resolved the underlying issue and service has been resumed

Resolvedresolved 31 d ago

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=resend
Slack
/feed subscribe https://outages.cc/feed.xml?providers=resend

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane