Is Resend down?
For agents
proceed
Proceed.
GET upbutler.com/status/resend/status.agent.json
MCP: upstream_status {"service":"resend"}
Transactional email API. Outages drop sign-up and password emails without an error in the browser.
What Resend reports
Operational
Taken as is from Resend's own status page API. Incident titles and component names below are theirs.
Open resend-status.comUpButler's independent probe
API edge is answeringHTTP 401 · 208 ms
One request without credentials to api.resend.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
Resend components
12 operational
- Single EmailOperational
- Batch EmailsOperational
- Broadcast EmailsOperational
- Scheduled EmailsOperational
- SMTPOperational
- General APIOperational
- Email EventsOperational
- AutomationsOperational
- WebhooksOperational
- DashboardOperational
- WebsiteOperational
- MCP ServerOperational
Resend incidents, last 90 days
3 finished incidents seen since UpButler started tracking on 2026-10-10. A typical one lasted 52 min; the longest 2 h 46 min.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Delayed new team provisioning and contact webhook delivery | minor | 23 min | |
| Resend API with elevated error rate | minor | 52 min | |
| Delayed function processing | minor | 2 h 46 min |
Tell your outage from Resend's
Declare that your project depends on Resend. When one of your monitors fails while Resend has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- resendcurl -s https://upbutler.com/status/resend/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "resend",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Resend down right now?
- No. As of 2026-10-10 05:11 UTC, Resend is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Resend's own status page API at https://resend-status.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Resend's words.
- What does UpButler's own Resend check prove?
- Every two minutes UpButler sends one request without credentials to the Resend API edge (api.resend.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Resend reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Resend status?
- Fetch https://upbutler.com/status/resend/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"resend"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Resend's?
- Add "resend" to the dependencies of your UpButler workspace. When one of your monitors fails while Resend has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in email
UpButler is not affiliated with Resend. Status and incident text belong to Resend and are read from their public status source; the probe result is UpButler's own measurement.