Live status & reliability report

Resend status, outages & reliability

#10 of 11 transactional email APIsOperational

Resend is an email sending API for developers, based in San Francisco.

Data updated Nov 1, 2026 · score recalculated

Over the last 90 days Resend had 99.39% effective uptime across 23 status page incidents (4 partial or major outages), resolving them in 3h 39m on average.

60.5/100Reliability scoreVisit Resend ↗

Is Resend down right now?

No, Resend is up and running.

  • Resend's status page reports all systems operational. Checked .
  • All 3 Resend pages we check are responding. Checked .

Official Resend status page ↗

Uptime (90d)99.39%12h 59m weighted downtime
Incidents (90d)234.3 per 30 days
Major / partial outages4
Avg time to resolve3h 39m
Outages we detected0by our independent probes

90-day uptime

Aug 4, 2026 – Aug 6, 2026: no incidentsAug 7, 2026: 99.74% uptime, 1 incident (Degraded performance)Aug 8, 2026: 94.47% uptime, 1 incident (Partial outage)Aug 9, 2026 – Aug 12, 2026: no incidentsAug 13, 2026: 99.54% uptime, 1 incident (Partial outage)Aug 14, 2026 – Aug 15, 2026: no incidentsAug 16, 2026: 100% uptime, 1 incident (Degraded performance)Aug 17, 2026: no incidentsAug 18, 2026: 97.42% uptime, 1 incident (Degraded performance)Aug 19, 2026: 93.73% uptime, 1 incident (Degraded performance)Aug 20, 2026: 99.75% uptime, 1 incident (Degraded performance)Aug 21, 2026 – Sep 2, 2026: no incidentsSep 3, 2026: 99.59% uptime, 1 incident (Degraded performance)Sep 4, 2026: 99.66% uptime, 1 incident (Degraded performance)Sep 5, 2026 – Sep 10, 2026: no incidentsSep 11, 2026: 99.93% uptime, 1 incident (Major outage)Sep 12, 2026 – Sep 14, 2026: no incidentsSep 15, 2026: 97.23% uptime, 1 incident (Partial outage)Sep 16, 2026: 99.94% uptime, 2 incidents (Degraded performance)Sep 17, 2026: no incidentsSep 18, 2026: 96.52% uptime, 2 incidents (Degraded performance)Sep 19, 2026: 85.00% uptime, 1 incident (Degraded performance)Sep 20, 2026: 88.47% uptime, 1 incident (Degraded performance)Sep 21, 2026: no incidentsSep 22, 2026: 99.37% uptime, 1 incident (Degraded performance)Sep 23, 2026: no incidentsSep 24, 2026: 99.46% uptime, 1 incident (Degraded performance)Sep 25, 2026: no incidentsSep 26, 2026: 98.26% uptime, 1 incident (Degraded performance)Sep 27, 2026 – Sep 30, 2026: no incidentsOct 1, 2026: 99.45% uptime, 1 incident (Degraded performance)Oct 2, 2026 – Oct 8, 2026: no incidentsOct 9, 2026: 99.76% uptime, 1 incident (Degraded performance)Oct 10, 2026: 99.27% uptime, 1 incident (Degraded performance)Oct 11, 2026 – Oct 22, 2026: no incidentsOct 23, 2026: 99.48% uptime, 1 incident (Degraded performance)Oct 24, 2026 – Oct 25, 2026: no incidentsOct 26, 2026: 99.76% uptime, 1 incident (Degraded performance)Oct 27, 2026 – Nov 1, 2026: no incidents
90 days ago99.398% average daily uptimeToday
  • No incidents
  • Degraded
  • Partial outage
  • Major outage
  • No data

Key facts about Resend's reliability

  • Since Jul 30, 2026, the earliest date its published history covers, Resend published 25 incidents on its status page, 4 of them partial or major outages.
  • Its longest outage on record in that time was “Increased API and SMTP Error Rates” on Aug 8, 2026, which lasted 2h 39m.
  • The part of Resend most often affected was Dashboard (2 of 25 incidents).
  • Incidents most often began on a Thursday (7 of 25, UTC).
  • Resend's 90-day uptime of 99.39% is below the average for transactional email APIs (99.76%).
  • It resolves incidents more slowly than the typical transactional email API: 3h 39m on average, against a median of 1h 51m.

Score breakdown

Uptime · 40% weight
48
99.399% effective uptime
Incident frequency · 20% weight
34
4.33 weighted incidents per 30 days
Time to resolve · 20% weight
74
3h 39m average
Transparency · 20% weight
100
No unreported outages detected

How the score is calculated →

Incidents per month

036912DecJan ’26FebMarAprMayJun2 degraded performance incidents2Jul2 partial outage incidents4 degraded performance incidents1 informational incident7Aug1 major outage incident1 partial outage incident8 degraded performance incidents1 informational incident11Sep5 degraded performance incidents5OctNov
  • Major outage
  • Partial outage
  • Degraded
  • Informational

Response time

Daily average response time of Resend's public pages, measured by our probes.

Not enough data yet — this chart fills in as our monitoring runs.

Score trend

Daily reliability score (rolling 90-day window).

Not enough data yet — this chart fills in as our monitoring runs.

Resend incident history (last 90 days)

Source: Resend status page · last checked

Our independent monitoring

We check these public Resend pages every 5 minutes. An outage is recorded after two consecutive failed checks.

PageLast checkUptime (30d)Avg response
HomepageUp 100%310 ms
LoginUp 100%375 ms
API rootUp 100%161 ms

How Resend compares

Resend vs Mailjet

99.39% vs 100% uptime

Resend vs Mailtrap Email Sending

99.39% vs 99.99% uptime

Resend vs Loops

99.39% vs 99.98% uptime

Resend vs Twilio SendGrid

99.39% vs 99.98% uptime

Resend vs SparkPost (Bird)

99.39% vs 99.90% uptime

Resend vs Mailgun

99.39% vs 99.84% uptime

Most reliable Resend alternatives →

Resend status FAQ

Is Resend down right now?

No, Resend is up and running. Resend's status page currently reports all systems operational, and all 3 of the Resend pages we check every five minutes are responding. This page updates automatically when that changes.

How reliable is Resend?

Resend has a reliability score of 60.5 out of 100, ranking #10 of 11 transactional email APIs. Over the last 90 days it had 99.39% effective uptime.

How often does Resend have outages?

Resend published 23 incidents on its status page in the last 90 days (4 partial or major outages) and 25 in the past 12 months.

How long do Resend outages last?

Resend resolves incidents in 3h 39m on average. Its longest outage in the past year lasted 2h 39m, on Aug 8, 2026.

Does Resend have a status page?

Yes. Resend's official status page is resend-status.com. We read it every five minutes and keep its full incident history.