CheckUpstream measured Resend at 100.000% availability across 2824 independent checks (global · api). 6 incidents were recorded in the past 12 months; the most recent resolved 12 days ago after 22 minutes. Status signals are polled from Resend's official Atlassian Statuspage status page, alongside independent probes and community reports.
180 days measured availability how this is computed
100.000%
global · api · n=2824 · p95 752ms (30d)
Share of our own checks against Resend endpoints that returned Resend's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 6 incidents · 178 of 180 days with none posted · 1h 26m of declared impact
Fewer incidents in the last 30 days than 21% of 232 tracked services.
Share of each window with no impact declared by Resend
7d
100.000%
30d
99.836%
90d
99.933%
180d
99.967%
1y
99.984%
Downtime like this can be refundable
If you're a paying Resend customer, outages in these windows may count against Resend's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Resend entitlement →Does Resend actually matter to you?
A Resend outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 6 incidents Resend published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Resend takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 20, 04:58 UTC · resolved in 22m · Resolved
Aug 18, 19:53 UTC · resolved in 2h 47m · Resolved
Aug 9, 18:44 UTC · resolved in 16m · Resolved
Aug 7, 15:19 UTC · resolved in 30m · Resolved
4signals across 1 source
Synthetic probes 4
All of these are CheckUpstream's own probes. Nobody else has reported Resend in this window, so nothing here is corroboration.
Live Resend status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/resend)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Resend is currently Operational. CheckUpstream tracks Resend in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Resend's last resolved incident started 12 days ago and lasted 22 minutes (degraded performance).
Looking for the live "is Resend down" view? See the Resend Live status page.
Jul 30, 21:53 UTC · resolved in 52m · Resolved
Jul 29, 16:34 UTC · resolved in 0m · Resolved
Resend's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Resend endpoints. It is the share of checks that returned the expected response, not a figure taken from Resend's status page.
Sign up to CheckUpstream and add Resend to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Resend's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.