outages.live
Live

Resend

Resend is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

18

Days with an incident

21

Median duration

39 min

Longest incident

2 days

Components

12
Single Email Operational
90 days agoNo incidentsToday
Batch Emails Operational
90 days agoNo incidentsToday
Broadcast Emails Operational
90 days agoNo incidentsToday
Scheduled Emails Operational
90 days agoNo incidentsToday
SMTP Operational
90 days agoNo incidentsToday
General API Operational
90 days agoNo incidentsToday
Email Events Operational
90 days agoNo incidentsToday
Automations Operational
90 days agoNo incidentsToday
Webhooks Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Website Operational
90 days agoNo incidentsToday
MCP Server Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 26, 2026

Duration23 min14:34 to 14:57Delayed email status updatesDegraded

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

Oct 23, 2026

Duration49 min15:57 to 16:47Intermittent latency spikes on our emails APIDegraded

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

Oct 10, 2026

Duration34 min14:35 to 15:09Delayed new team provisioning and contact webhook deliveryDegraded

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

Oct 9, 2026

Duration23 min21:47 to 22:10Delayed new team provisioning and contact webhook deliveryDegraded

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

Oct 1, 2026

Duration52 min12:28 to 13:20Resend API with elevated error rateDegraded

We have resolved the underlying issue and service has been resumed

Sep 26, 2026

Duration2 h 46 min06:29 to 09:15Delayed function processingDegraded

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

Sep 24, 2026

Duration51 min14:31 to 15:22Intermittent errors on some dashboard and API requestsDegraded

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

Sep 22, 2026

Duration19 min22:31 to 22:50Failing to verify new domainsDegraded

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

Sep 18, 2026

Duration2 days18:26 to 18:26Degraded performanceDegraded

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

Sep 16, 2026

Duration5 min15:58 to 16:03Increased latency in WebHooksDegraded

Service has been resumed.

Sep 15, 2026

Duration1 h 20 min15:49 to 17:09Delayed email sendingPartial outage

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.

Sep 4, 2026

Duration32 min19:02 to 19:34Delays in background processes are affecting webhooks, domain verifications, and other important featuresDegraded

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.

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

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane