Skip to main content
Resend logo

Is Resend Down?

No — Resend is up

Reachable from all 8 checked regions

Average response time: 275ms

Last checked · checks run every 6 hours

Official status page: https://resend-status.com

Resend uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
368ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 46 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

46-day clean streak
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 24 checks
Sep 18: 100.00% uptime, 40 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 31 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 8 checks
Sep 13 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

jnb
595ms
DNS 62ms TCP 0ms TLS 79ms TTFB 521ms
lax
119ms
DNS 15ms TCP 1ms TLS 24ms TTFB 95ms
lhr
274ms
DNS 54ms TCP 1ms TLS 9ms TTFB 266ms
nrt
273ms
DNS 7ms TCP 3ms TLS 7ms TTFB 258ms
ord
152ms
DNS 6ms TCP 1ms TLS 24ms TTFB 133ms
sin
228ms
DNS 176ms TCP 1ms TLS 6ms TTFB 222ms
sjc
200ms
DNS 21ms TCP 8ms TLS 8ms TTFB 189ms
syd
364ms
DNS 20ms TCP 0ms TLS 7ms TTFB 357ms

What Resend does

Resend is a transactional email service built for developers, sending through an HTTPS API or an SMTP relay. Applications use it for the mail a product cannot function without: password resets, sign-in codes, receipts and account notifications. Delivery events are reported back over webhooks, so most teams depend on Resend for both sending the message and knowing what happened to it.

What an outage looks like

Calls to the send endpoint fail or time out, and SMTP relay connections are refused. A subtler shape is mail that is accepted while Email Events stop updating, so delivery status in your own database goes stale. Webhooks stop arriving. Resend reports Email Sending, Automations, Webhooks, Dashboard and Website as separate components, so the dashboard can be unreachable while sending works.

What to do about it

Check resend-status.com, which is the real status page and not status.resend.com. Resend retries a webhook that does not return 200 after 5 seconds, 5 minutes, 30 minutes, 2 hours, 5 hours and 10 hours, so a receiver that was briefly down does not need a manual replay. Avoid blind re-sends: a request that timed out may already have been accepted.

Is it down for everyone, or just you?

If this page says Resend is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Postmark
Postmark
Mailgun
Mailgun
SendGrid (Twilio)
SendGrid (Twilio)
Brevo
Brevo

Resend outage FAQ

Is Resend down for everyone or just my app?
Resend publishes Email Sending, Automations, Webhooks, Dashboard and Website as separate components, and breaks Email Sending down further into SMTP, General API and Email Events. Check the specific component your code uses before assuming a full outage. An application sending over SMTP and one sending over the API can see completely different results during the same incident.
Will emails be lost during a Resend outage?
It depends on whether the request was accepted. A send call that returned an error or timed out was not necessarily queued, so those messages are your responsibility to retry. Messages Resend already accepted are tracked through the Email Events component, which is reported separately from sending, so a stale event feed is not proof the mail failed.
Does Resend retry webhooks after an outage?
Yes. If Resend does not receive a 200 response from your webhook server it retries at 5 seconds, 5 minutes, 30 minutes, 2 hours, 5 hours and 10 hours, with each interval starting after the preceding attempt fails. The dashboard shows when a message is next due, so a receiver that was down for a short window catches up without intervention.
The Resend dashboard will not load. Is sending broken too?
Not necessarily. Dashboard and Website are their own components, listed apart from Email Sending. An incident scoped to the dashboard leaves the API and SMTP relay serving normally, so your application keeps delivering mail while you cannot log in to look at it. Confirm against the Email Sending component rather than the page you happen to be on.
What can I send through while Resend is unavailable?
Postmark, Mailgun and SendGrid all offer SMTP relays, so a service already configured for SMTP can usually be repointed by changing host credentials rather than rewriting code. Teams that treat transactional mail as critical often keep a second provider configured and dormant for this reason. Switching providers mid-incident changes your sending domain reputation, so test first.

How we measure this

  • We request Resend's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Resend publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Resend goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required