Vendor record
Resend
Checked
Front door check counts and Resend’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Resend endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,874 of 2,874 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
5 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.resend.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Resend product, region or your app worked.
How we count front door checksResend says
Incident posts from Resend’s status page, with its titles, impact levels and times. They say what Resend chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
15
incidents Resend posted, last 90 days
Median recorded duration: 1h. From 15 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Delayed new team provisioning and contact webhook delivery
Not specifiedStarted, per Resend
Closed in our record(34m)
Delayed new team provisioning and contact webhook delivery
Not specifiedStarted, per Resend
Closed in our record(28m)
Resend API with elevated error rate
Not specifiedStarted, per Resend
Closed in our record(1h 1m)
Delayed function processing
MinorResend’s postStarted, per Resend
Closed in our record(2h 46m)
Intermittent errors on some dashboard and API requests
MinorResend’s postStarted, per Resend
Closed in our record(1h 42m)
10 older records
Failing to verify new domains
MinorResend’s postStarted, per Resend
Closed in our record(1h)
Delayed email sending
MajorResend’s postStarted, per Resend
Closed in our record(1h 19m)
Delays in background processes are affecting webhooks, domain verifications, and other important features
MinorResend’s postStarted, per Resend
Closed in our record(32m)
Delay in contact webhooks delivery
MinorResend’s postStarted, per Resend
Closed in our record(39m)
Increased latency across API endpoints
MinorResend’s postStarted, per Resend
Closed in our record(24m)
Contact webhook events are delayed in delivery
MinorResend’s postStarted, per Resend
Closed in our record(14h 8m)
Delayed contact webhook events
Not specifiedResend’s postStarted, per Resend
Closed in our record(38m)
Delayed contact related webhook events
MinorResend’s postStarted, per Resend
Closed in our record(24m)
Increased failure rate in Domain verifications
MinorResend’s postStarted, per Resend
Closed in our record(1h 25m)
Increased returned error rates
CriticalResend’s postStarted, per Resend
Closed in our record(1h 23m)
Your code, your dependencies
See which of your code paths call Resend
Connect GitHub or GitLab to find where your public or private repository uses Resend. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Resend status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Resend currently down?
Resend's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Resend last have an outage?
The most recent closed incident record began 6 days ago and spans 34 minutes. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Resend?
No. CheckUpstream checks Resend’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Resend in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Resend?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.