Is Resend Down?

No — Resend is up

Resend's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 244 ms

Right now

The verdict is the worse of these two. How we decide

Resend's status page

resend-status.com · read 4 minutes ago · checked every 3 minutes

Operational

Resend's components, as its status page reports them
Component	Status
Single Email	Operational
Batch Emails	Operational
Broadcast Emails	Operational
Scheduled Emails	Operational
SMTP	Operational
General API	Operational
Email Events	Operational
Automations	Operational
Webhooks	Operational
Dashboard	Operational
Website	Operational
MCP Server	Operational

Open their status page

FlareWarden checks

resend.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 244 ms
Checked: 5 hours ago

By region

Ashburn reachable, 212 ms
Chicago reachable, 130 ms
Frankfurt reachable, 81 ms
Johannesburg reachable, 679 ms
London reachable, 101 ms
Los Angeles reachable, 144 ms
São Paulo reachable, 256 ms
Tokyo reachable, 355 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	105 ms	1 ms	7 ms	199 ms
Chicago	7 ms	1 ms	23 ms	109 ms
Frankfurt	14 ms	2 ms	9 ms	69 ms
Johannesburg	63 ms	1 ms	74 ms	552 ms
London	26 ms	3 ms	8 ms	74 ms
Los Angeles	22 ms	1 ms	24 ms	124 ms
São Paulo	215 ms	1 ms	5 ms	248 ms
Tokyo	41 ms	1 ms	9 ms	344 ms

We check that resend.com loads, not every feature behind it. Test it yourself

History

Incidents Resend reported

Since Oct 22, 15 days · from resend-status.com

Incidents: 2
Major or critical: 0
Median to resolve: 36m

Delayed email status updates
minor · Oct 26
lasted 22m
Intermittent latency spikes on our emails API
minor · Oct 23
lasted 49m

Resend website availability

Measured by FlareWarden · resend.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 340ms

Last 30 days

70-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of resend.com from multiple regions every 6 hours. Resend's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 70 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Resend itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Resend goes down

We check Resend every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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