Skip to content

Outage tracker

Resend: the full evidence record

The last 24 hours in detail, 46 days of measured availability, a 12-month summary, our own incident log, Resend's declared record, and how the two compare.

← Back to Resend's live status

We started measuring Resend on August 22, 2026, which is 46 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me the next time we see Resend go down

Measured by our own probes from ten regions, not Resend's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Resend's own status page declared. Below it, any public chatter we saw about Resend and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Resend's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Resend in the last 24 hours, which is not evidence that nothing is wrong.
Resend's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Resend's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Resend next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East99.97%6281
US-West100.00%6273
Europe99.95%6200
Asia-Pacific100.00%5955
US-Central100.00%2399
Canada100.00%2396
UK100.00%2396
Southeast Asia100.00%2365
Australia100.00%2360
South America100.00%2389

Monthly summary

Tracking Resend since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min
Oct 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Resend: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Resend's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Resend in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Resend's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Resend since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Resend's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Resend API with elevated error rateMinor incident
Oct 1, 2026, 12:28 PM UTC to Oct 1, 2026, 1:20 PM UTC (52 min)resolved
their latest update (Oct 1, 2026, 1:20 PM UTC): We have resolved the underlying issue and service has been resumed
Delayed function processing Minor incident
Sep 26, 2026, 6:29 AM UTC to Sep 26, 2026, 9:15 AM UTC (2h 46m)resolved
their latest update (Sep 26, 2026, 9:15 AM UTC): We have resolved the underlying issue and service has been resumed.
Intermittent errors on some dashboard and API requestsMinor incident
Sep 24, 2026, 2:31 PM UTC to Sep 24, 2026, 3:22 PM UTC (51 min)resolved
their latest update (Sep 24, 2026, 3:22 PM UTC): We have resolved the underlying issue and service has been resumed.
Failing to verify new domainsMinor incident
Sep 22, 2026, 10:31 PM UTC to Sep 22, 2026, 10:50 PM UTC (19 min)resolved
their latest update (Sep 22, 2026, 10:50 PM UTC): We have resolved the underlying issue and service has been resumed.
Degraded performanceMinor incident
Sep 18, 2026, 6:26 PM UTC to Sep 20, 2026, 6:26 PM UTC (2d 0h)resolved
their latest update (Sep 20, 2026, 6:27 PM UTC): We have resolved the underlying issue and service has been resumed.
Degraded performanceMinor incident
Sep 18, 2026, 4:48 PM UTC to Sep 18, 2026, 4:17 PM UTC (0 min)resolved
their latest update (Sep 18, 2026, 4:54 PM UTC): We have resolved the underlying issue and service has been resumed.
Increased latency in WebHooksMinor incident
Sep 16, 2026, 3:58 PM UTC to Sep 16, 2026, 4:03 PM UTC (5 min)resolved
their latest update (Sep 16, 2026, 4:03 PM UTC): Service has been resumed.
High latency on General-API All systems operational
Sep 16, 2026, 12:23 PM UTC to Sep 16, 2026, 12:06 PM UTC (0 min)resolved
their latest update (Sep 16, 2026, 12:06 PM UTC): We have resolved the underlying issue and service has been resumed.
Delayed email sendingPartial outage
Sep 15, 2026, 3:49 PM UTC to Sep 15, 2026, 5:09 PM UTC (1h 20m)resolved
their latest update (Sep 16, 2026, 3:04 PM UTC): 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 br…
Unresponsive remote MCP serverMajor outage
Sep 11, 2026, 7:27 PM UTC to Sep 11, 2026, 3:37 PM UTC (0 min)resolved
their latest update (Sep 11, 2026, 3:37 PM UTC): We have resolved the underlying issue and service has been resumed.

Showing the 10 most recent of 37 incidents Resend has declared in the history we hold.

These entries are Resend's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Resend's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Resend's own status page on August 22, 2026, 44 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Resend since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Resend decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Resend believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.