Is Resend down?
Resend status · Communication · checked (0s ago)
No — Resend is not down. All Resend systems are reported operational.
According to Resend's official status page, Resend was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Resend's feed reported no outage in 100.00% of our checks.
Is Resend down for you right now?
Everything above is read from Resend's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Resend in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Resend is
Resend is a transactional email API aimed at developers, with a React-based templating library and a simple send endpoint. It sits in the same place Mailgun and SendGrid do — password resets, receipts, notifications — with a smaller surface.
What Resend's status feed covers
The status page covers the API, the dashboard and delivery. As with any sending platform, the feed can only speak for Resend's own systems: a message accepted by Resend and then deferred by the recipient's provider is an outcome you have to read in the logs, not something a status page can report.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
Resend uptime, last 30 days
One bar per day. Each shows the share of that day's checks where Resend's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Resend was down.
- No outage reported (99%+)
- 95–99%
- 80–95%
- Under 80%
- No data
Other services reporting problems right now
10 other services isuptime tracks were also reporting a problem as of the same check, 0s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
CloudflarePartial System Outage
- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
GrafanaMinor Service Outage
- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
Resend response time trend
Each point is one check of Resend's status endpoint.
Resend outage history
Resend has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Resend posted itself — not every problem users hit.
- Delayed email status updates
resolved · Oct 26, 02:34 PM (8d ago)
- Intermittent latency spikes on our emails API
resolved · Oct 23, 03:57 PM (11d ago)
- Delayed new team provisioning and contact webhook delivery
resolved · Oct 10, 02:35 PM (24d ago)
- Delayed new team provisioning and contact webhook delivery
resolved · Oct 9, 09:47 PM (25d ago)
- Resend API with elevated error rate
resolved · Oct 1, 12:28 PM (33d ago)
- Delayed function processing
resolved · Sep 26, 06:29 AM (39d ago)
- Intermittent errors on some dashboard and API requests
resolved · Sep 24, 02:31 PM (40d ago)
- Failing to verify new domains
resolved · Sep 22, 10:31 PM (42d ago)
- Degraded performance
resolved · Sep 18, 06:26 PM (46d ago)
- Degraded performance
resolved · Sep 18, 04:48 PM (46d ago)
- Increased latency in WebHooks
resolved · Sep 16, 03:58 PM (48d ago)
- High latency on General-API
resolved · Sep 16, 12:23 PM (48d ago)
- Delayed email sending
resolved · Sep 15, 03:49 PM (49d ago)
- Unresponsive remote MCP server
resolved · Sep 11, 07:27 PM (53d ago)
- Delays in background processes are affecting webhooks, domain verifications, and other important features
resolved · Sep 4, 07:02 PM (60d ago)
- Delay in contact webhooks delivery
resolved · Sep 3, 10:05 AM (61d ago)
- Increased latency across API endpoints
resolved · Aug 20, 04:58 AM (76d ago)
- Contact webhook events are delayed in delivery
resolved · Aug 18, 07:53 PM (77d ago)
- API instability
resolved · Aug 16, 01:17 PM (79d ago)
- Errors during the domain creation process
resolved · Aug 13, 06:03 PM (82d ago)
Resend status — frequently asked
- Is Resend down right now?
- No — Resend is not down. All Resend systems are reported operational. Checked (0s ago).
- What is Resend's status right now?
- Resend is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 479 ms. isuptime reads this from Resend's own published feed and does not test Resend independently.
- When did Resend last go down?
- The most recent incident Resend published was “Delayed email status updates”, opened Oct 26, 02:34 PM UTC (8d ago) and marked resolved Oct 26, 02:57 PM UTC. That is the latest entry in Resend's own incident feed, not every problem users experienced.
- What is Resend's uptime?
- isuptime does not measure Resend's uptime directly — it reads Resend's own published status feed. Over the last 30 days, Resend's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
- Is it just me, or is Resend down for everyone?
- Resend reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
Resend says operational but it is not working for me
Domain verification is the usual culprit — an unverified domain, or missing DKIM and SPF records, is rejected or filtered downstream. Test API keys only deliver to your own address. Rate limits apply per account and per domain, and a batch send from a loop hits them quickly with errors that look like an outage.
Alternatives to Resend
Resend is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
If Resend goes down
Status shown for each is read from that provider's own feed, on the same schedule as this page.