Loading status…
Loading status…
Resend status · Communication · checked (1m 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.
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.
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.
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.
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.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Resend's status endpoint.
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.
monitoring · Sep 18, 06:26 PM (1d ago)
resolved · Sep 18, 04:48 PM (1d ago)
resolved · Sep 16, 03:58 PM (3d ago)
resolved · Sep 16, 12:23 PM (3d ago)
resolved · Sep 15, 03:49 PM (4d ago)
resolved · Sep 11, 07:27 PM (8d ago)
resolved · Sep 4, 07:02 PM (15d ago)
resolved · Sep 3, 10:05 AM (16d ago)
resolved · Aug 20, 04:58 AM (31d ago)
resolved · Aug 18, 07:53 PM (32d ago)
resolved · Aug 16, 01:17 PM (34d ago)
resolved · Aug 13, 06:03 PM (37d ago)
resolved · Aug 9, 06:44 PM (41d ago)
resolved · Aug 8, 09:46 PM (42d ago)
resolved · Aug 7, 03:19 PM (43d ago)
resolved · Aug 4, 06:45 PM (46d ago)
resolved · Aug 4, 06:25 PM (46d ago)
resolved · Jul 30, 09:53 PM (51d ago)
resolved · Jul 29, 09:07 PM (52d ago)
resolved · Jul 29, 04:15 PM (52d ago)
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.
Resend is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.