Payments & messaging APIs
Is Resend down?
Live Resend status, measured independently. We probe 6 Resend endpoints from monitoring regions on every continent and record every outage we detect.
Resend is up
Our probes are reaching Resend normally from every region we check from.
Checked every minute from 6 regions on every continent.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website99.99% uptime, 30 days6 regions, 116 to 507 msCheckingp50314 msMedian responsep951214 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- General API99.99% uptime, 30 days6 regions, 100 to 345 msCheckingp50215 msMedian responsep95421 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- SMTP100% uptime, 30 days6 regions, 154 to 815 msCheckingp50451 msMedian responsep95736 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Dashboard99.99% uptime, 30 days6 regions, 199 to 610 msCheckingp50385 msMedian responsep95591 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Documentation99.97% uptime, 30 days6 regions, 356 to 778 msCheckingp50528 msMedian responsep95681 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- DNS100% uptime, 30 days6 regions, 3 to 19 msCheckingp5013 msMedian responsep95143 msSlowest 5% of checks50 ms25024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Resend goes down
Follow these 6 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Resend goes down. They don't count against your monitor quota. Free plan, no card required.
About Resend outages
Resend is a transactional email API favoured by modern JavaScript teams for its simple SDK and React Email templates. Because it carries signup confirmations, password resets, and receipts, a Resend incident looks like users complaining that emails never arrived.
What we check
Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website resend.com is unreachable. | httpresend.com | HTTP 200 | 1 min |
General API The Resend API is not answering with its normal authentication response. Sends fail. | httpapi.resend.com/emails | HTTP 401 | 1 min |
SMTP The SMTP endpoint is not accepting connections. Apps sending through SMTP instead of the API fail. | tcpsmtp.resend.com:465 | TCP connection accepted | 1 min |
Dashboard The Resend dashboard is unreachable. | httpresend.com/login | HTTP 200 | 2 min |
Documentation Resend's documentation is unreachable. | httpresend.com/docs | HTTP 200 | 5 min |
DNS The API hostname is not resolving. | dnsapi.resend.com | A record resolves | 1 min |
For component-level detail and incident write-ups from the vendor, see Resend's official status page.
Embed a live Resend badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/resend?utm_source=badge)HTML
<a href="https://www.upti.my/status/resend?utm_source=badge"><img src="https://www.upti.my/status/resend/badge.svg" alt="Resend status"></a>Recent Resend outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Resend is up. Is your Resend integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Resend and fail quietly. Here is what teams that rely on Resend monitor on their side.
Delivery webhooks
Track delivered and bounced events. A drop in delivered events is the earliest sign that email is not going out.
Webhook monitoringYour email-sending jobs
Digest and reminder jobs fail silently when the provider errors. A heartbeat per job catches the missing run.
Heartbeat monitoringResend status: frequently asked questions
Sending and delivery are different stages. Resend can accept your request and then queue it behind a provider or recipient-side issue. Delivery webhooks, not API responses, tell you when mail actually lands.
Look at the per-region results above. If our probes fail from every region, Resend has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Resend may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Resend" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Resend: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other payments & messaging apis
Uptimy is not affiliated with Resend. Resend and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.