Dev APIs / Email API / Resend

Resend

OPERATIONAL

Since Jul 2026 · 25 incidents · resend-status.com · checked just now

User reportsVisitors who said it's down for them, per hour over 24 hours. Not from the status page. Never counted in grades.
…
CompareAdd to stackStatus page
GradeBLast 85 days
BPRODASHIP

Overview

30d90d1y
Admitted uptimeCustomer time not hit, by the provider's own account. Regional and partial incidents count in part.
99.874%Grade B
IncidentsEverything posted on the status page except scheduled maintenance.
250 Sev 1
Fully downMost customers down, by the provider's own account.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
24m
LongestLongest Sev 1–2 incident, start to resolved.
2d 0h
Since lastTime since the last counted incident was resolved.
23h 15m

By area

BProduction
17INCIDENTS
2d 22hAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Aug 18, 2026 · 14h 09m · one model or featureContact webhook events are delayed in delivery
SEV 2Sep 26, 2026 · 2h 46mDelayed function processing
SEV 2Aug 8, 2026 · 43m · some customersIncreased API and SMTP Error Rates
17 in the last 6 months.
AShipping
8INCIDENTS
2d 2hAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 3Oct 1, 2026 · 52mResend API with elevated error rate
SEV 3Oct 10, 2026 · 34mDelayed new team provisioning and contact webhook delivery
SEV 3Sep 18, 2026 · 2d 0hDegraded performance
8 in the last 6 months.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

25 in the last 6 months.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down15
Sev 3 · Can't shipCan't deploy, build or manage it7
Sev 4 · PapercutDocs, status page, slow dashboard3

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Communication

Updates eachStatus page updates per incident, on average.
2.8Last 12 months
Update gapMedian time between status page updates during an incident.
22mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 15Sev 1–2

Incident history

Show all 25
Oct 23, 202649mSEV 4
Intermittent latency spikes on our emails APIEmail sending through the SMTP service and API was delayed from about 15:57 to 16:47 UTC on 23 October 2026 due to increased latency. The provider identified the issue, pushed a fix, and resolved it. The text does not give the share of requests affected or the root cause.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Email sending via SMTP and API was delayed for about 50 minutes; the text gives no breadth or error rate.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 16:01 UTC · investigating
    We are currently investigating increased latency in email sending. At this time, you may experience delays when sending emails via our SMTP service and API.
  2. 16:31 UTC · identified
    We have identified the issue and we are working on a fix now.
  3. 16:36 UTC · monitoring
    The fix has been pushed and we are now monitoring the situation.
  4. 16:47 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Oct 10, 202634mSEV 3
Delayed new team provisioning and contact webhook deliveryNew teams took longer than usual to finish account setup, and some contact activity webhooks were delivered late. Email sending and receiving were not affected. The provider fixed the underlying issue and resumed service about 35 minutes after it started.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 17M
    New team provisioning was delayed and some contact-related webhooks arrived late for about 35 minutes; email sending and receiving were not affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 14:00 UTC · identified
    We've identified an issue on our infrastructure affecting new team provisioning and contact webhook delivery. Email sending and receiving is not affected. • Newly created teams may take longer to have their account resources fully setup. • Some webhooks related to contact activity are being delivered with a delay. Our team is working on fixing this issue.
  2. 14:52 UTC · monitoring
    A fix is in place and we are monitoring to ensure the issue has been fixed.
  3. 15:09 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Oct 9, 202623mSEV 2
Delayed new team provisioning and contact webhook deliveryContact activity webhooks were delivered late and new team provisioning was slow; email sending and receiving were unaffected.AI-graded · some customers
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Contact activity webhooks were delivered late and new team provisioning was slow; email sending and receiving were unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 21:47 UTC · identified
    We've identified an issue on our infrastructure affecting new team provisioning and contact webhook delivery. Email sending and receiving is not affected. • Newly created teams may take longer to have their account resources fully setup. • Some webhooks related to contact activity are being delivered with a delay. Our team is working on fixing this issue.
  2. 22:06 UTC · monitoring
    Our team is monitoring to ensure the issue has been fixed.
  3. 22:10 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Oct 1, 202652mSEV 3
Resend API with elevated error rateResend's general API failed about 24% of requests from 12:28 to 13:20 UTC on October 1. The root cause was identified and fixed. Email sending was not affected.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    About 24% of general Resend API requests failed for roughly 50 minutes; email sending was not affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 12:28 UTC · investigating
    We are currently investigating increased error rate our API. At this time, you may experience erros when sending requests to our API.
  2. 12:43 UTC · identified
    Our general API is failing ~24% of the requests. The team has identified the root cause and is mitigating it. Email sending is not affected.
  3. 13:05 UTC · monitoring
    The fix has been pushed and we are now monitoring the situation.
  4. 13:20 UTC · resolved
    We have resolved the underlying issue and service has been resumed
Source
Sep 26, 20262h 46mSEV 2
Delayed function processing Async function processing ran with increased delays for about 3 hours; sending was unaffected and domain verification took longer.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Async function processing ran with increased delays for about 3 hours; sending was unaffected and domain verification took longer.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 06:29 UTC · investigating
    We are currently investigating increased a delay in async functions, sending is not affected. You may experience longer times for domain verification
  2. 06:43 UTC · monitoring
    We are seeing functions going back to being processed at normal rates and we’re monitoring
  3. 09:15 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 24, 202651mSEV 3
Intermittent errors on some dashboard and API requestsEmail sending via SMTP and API was delayed for about 50 minutes; the scope across customers is not stated.AI-graded · some customers
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 22M
    Email sending via SMTP and API was delayed for about 50 minutes; the scope across customers is not stated.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 14:31 UTC · investigating
    We are currently investigating increased latency in email sending. At this time, you may experience delays when sending emails via our SMTP service and API.
  2. 14:53 UTC · monitoring
    We've been monitoring the operations and see no new errors in the past minutes, we're monitoring
  3. 15:22 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 22, 202619mSEV 2
Failing to verify new domainsEmail sending via SMTP and API was delayed and new domain verification failed for about 40 minutes; the scope was not stated.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Email sending via SMTP and API was delayed and new domain verification failed for about 40 minutes; the scope was not stated.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 21:50 UTC · investigating
    We are currently investigating an issue while verifying new domains. At this time, you may experience delays when sending emails via our SMTP service and API.
  2. 22:38 UTC · monitoring
    We identified the cause and we're seeing a decrease in errors, we are now monitoring
  3. 22:50 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 18, 20262d 0hSEV 2
Degraded performanceResend saw increased latency in webhooks, account creation and confirmation, and domain provisioning. Services recovered about 8 minutes later and were monitored. The incident was later marked resolved, with no cause given.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 8M
    Webhook latency and account creation/confirmation and domain provisioning slowed for about 8 minutes; the scope was not specified.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 18:26 UTC · investigating
    We are currently investigating increased latency webhooks, account creation/confirmation and domain provisioning.
  2. 18:34 UTC · monitoring
    Services recovered and we are now monitoring the situation.
  3. 18:26 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
  4. 18:27 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 18, 20260mSEV 2
Degraded performanceEmail API performance was degraded for an unspecified time and set of customers; the update gives no detail on impact.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Email API performance was degraded for an unspecified time and set of customers; the update gives no detail on impact.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 16:17 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
  2. 16:54 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 16, 20265mSEV 4
Increased latency in WebHooksWebhook delivery to customer apps saw increased latency for about five minutes; no outage or failures were reported.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Webhook delivery to customer apps saw increased latency for about five minutes; no outage or failures were reported.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 15:58 UTC · monitoring
    We're experiencing increased latency in webhook delivery.
  2. 16:03 UTC · resolved
    Service has been resumed.
Source
Sep 16, 20260mSEV 2
High latency on General-API General API requests experienced high latency for an unstated period and scope; the provider gave no component or region detail.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    General API requests experienced high latency for an unstated period and scope; the provider gave no component or region detail.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
1 update
  1. 12:06 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 15, 20261h 20mSEV 2
Delayed email sendingBroadcast sends queued and stalled from about 15:05 UTC on 15 Sept, and a later database issue from the fix held about 9,200 transactional emails for up to 25 minutes between 16:41 and 17:05. All emails were delivered and none were lost. Some customers also saw errors loading email details and lists. Resolved at 17:09 UTC.AI-graded · some customers
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Broadcast sends stalled for about 75 minutes and transactional emails were held up to 25 minutes for some customers; no emails were lost.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 15:49 UTC · identified
    We are investigating delays in broadcast sending. Broadcasts started after 15:05 UTC may stay in a queued state and make little or no progress. No emails have been lost. Affected broadcasts remain queued and will continue sending once the backlog clears. We have identified the cause and are working on a mitigation. Next update in 30 minutes.
  2. 16:22 UTC · monitoring
    Broadcast sending has recovered and the queued backlog is draining. Broadcasts that were delayed are sending now. No emails were lost and no action is required: affected broadcasts continue automatically and do not need to be resent. We are monitoring until the backlog is fully clear.
  3. 17:09 UTC · resolved
    Broadcast sending is fully recovered and the backlog has cleared. All broadcasts delayed during this incident have been sent or are sending normally. No emails were lost and no action is required.
  4. 15:04 UTC · resolved
    Follow-up: the impact was wider than we reported at the time. Between 16:41 and 17:05 UTC, roughly 9,200 transactional emails were accepted by our API and then held before delivery, by up to 25 minutes. This came from a database issue caused by the action we took to clear the broadcast backlog. All of those emails were delivered and none were lost. Some customers also saw errors loading email details or lists during the same minutes.
Source
Sep 11, 20260mSEV 2
Unresponsive remote MCP serverResend's remote MCP server had a full outage returning 5xx errors; the text gives no scope and the fix was announced in the same update.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Resend's remote MCP server had a full outage returning 5xx errors; the text gives no scope and the fix was announced in the same update.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 15:36 UTC · investigating
    We are currently investigating a full outage in the remove MCP server. During this time, requests are returning 5xx.
  2. 15:37 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 4, 202632mSEV 3
Delays in background processes are affecting webhooks, domain verifications, and other important featuresBackground processing was delayed from 19:02 to 19:34 UTC, affecting webhook deliveries, domain verifications, exports and account confirmations. Email sending was not affected. Events processing recovered at 19:08 and the backlog was drained; the underlying issue was resolved at 19:34.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Background jobs ran late for about 30 minutes, delaying webhooks, domain verifications and exports; email sending was unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 19:02 UTC · investigating
    We are currently investigating delays affecting our background processes. At this time, you may experience delays when taking actions that rely on asynchronous operations, such as: • Domain verifications • Webhook deliveries • Exports generation • Account confirmation • etc. Email sending is not affected.
  2. 19:08 UTC · monitoring
    Events processing have been recovered and we're now draining the backlog. We're still monitoring the situation.
  3. 19:26 UTC · monitoring
    Delayed processes have been executed. The team is still monitoring the background processes.
  4. 19:34 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 3, 202639mSEV 3
Delay in contact webhooks deliveryContact event webhooks to customer apps were delayed for about 40 minutes; scope and count of affected customers were not stated.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Contact event webhooks to customer apps were delayed for about 40 minutes; scope and count of affected customers were not stated.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 10:05 UTC · investigating
    We are currently investigating increased latency in contact webhooks delivery. At this time, you may experience delays to receive webhooks related to contact events.
  2. 10:45 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Aug 20, 202624mSEV 4
Increased latency across API endpointsLatency rose on non-email Resend API endpoints for about 24 minutes; email sending was not mentioned as affected.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 19M
    Latency rose on non-email Resend API endpoints for about 24 minutes; email sending was not mentioned as affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 04:58 UTC · investigating
    We are currently investigating increased latency in non-email sending API endpoints. Our team is investigating it.
  2. 05:17 UTC · identified
    We have identified the issue and deployed a fix. API latency has recovered since then. Our team is still monitoring to ensure it remains stable over the next few minutes.
  3. 05:22 UTC · resolved
    We have resolved the underlying issue and service latency has been recovered.
Source
Aug 18, 202614h 09mSEV 2
Contact webhook events are delayed in deliveryContact webhook events were delivered late, with delays peaking at about 3 hours, after an infrastructure change created a backlog. The provider said no webhooks were lost. A fix was deployed, the backlog was worked down, and the incident was resolved about 14 hours after it started.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Contact webhook deliveries to customer apps were delayed up to 3 hours; the dashboard and contact API were unaffected.
  3. Claude Haiku 5.5 · prompt v10 · Oct 24, 2026 · Raw record
6 updates
  1. 19:53 UTC · investigating
    We are currently investigating increased latency in contact webhook delivery. We have noticed a delay of approximately 50 minutes in sending webhooks related to contact events. The team is investigating and mitigating this processing delay issue. Contact management via dashbaord and its API are not affected.
  2. 21:11 UTC · identified
    We have identified the issue and are working on mitigating its effects. The volume of contact webhooks processed over time was affected by an infrastructure change, and now we have an increasing backlog of contact webhooks to process. The team is working on increasing the speed of processing the backlog. No contact webhooks were lost.
  3. 22:33 UTC · monitoring
    A fix has been deployed to the underlying infrastructure and we can now confirm we're processing the backlog with the correct volume. Delayed webhooks are now being delivered. We will post another update in 30 minutes to share more about the progress on processing the backlog.
  4. 23:01 UTC · monitoring
    We are still monitoring the progress on processing the backlog. The impact has been reduced from a peak 3-hour delay in delivering a contact webhook to 2h 20 min. The delay is being reduced further as we process the backlog. Within 2-3 hours, the backlog will be completely processed.
  5. 01:06 UTC · monitoring
    We have processed more than 66% of the backlog at this point. Within the next hour, the backlog will be fully processed, and this incident will be marked as resolved.
  6. 10:01 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Aug 16, 20260mSEV 2
API instabilityAPI returned 5xx errors for about 7% of requests for roughly three minutes; no components were listed.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    API returned 5xx errors for about 7% of requests for roughly three minutes; no components were listed.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
1 update
  1. 12:57 UTC · resolved
    API became unstable from 12:54 to 12:57 UTC, returning 5xx for approximately 7% of the requests. We have resolved the underlying issue and service has been resumed.
Source
Aug 13, 20260mSEV 2
Errors during the domain creation processFor about 13 minutes, requests to add a new domain failed in the dashboard and via POST /domains, and verification of domains added in that window was also affected. The fix restored normal domain creation. Failed requests did not partially create domains, so retrying works. Existing email sending was not affected.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · HIGH CONFIDENCE
    Adding new domains failed in the dashboard and API for about 13 minutes; email sending for existing domains was unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 17:30 UTC · investigating
    We identified an increase in errors during the domain creation process
  2. 17:43 UTC · resolved
    Between approximately 17:30 and 17:43 UTC, requests to add a new domain failed in the dashboard and through the public API (POST /domains). Verification of domains added during this window was also affected. The issue was identified and fixed, and domain creation has returned to normal. No domains were partially created: affected requests failed immediately, so retrying the domain creation will succeed. Email sending for existing domains was not affected.
Source
Aug 9, 202638mSEV 2
Delayed contact webhook eventsContact-related webhook events to customer apps were delayed for about 38 minutes; other Resend services were not reported affected.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Contact-related webhook events to customer apps were delayed for about 38 minutes; other Resend services were not reported affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 18:44 UTC · investigating
    We are currently investigating increased latency in sending contact related webhook events. At this time, you may experience delays when receiving those requests on your end.
  2. 19:17 UTC · monitoring
    We have worked on a couple improvements and the queue has caught up and events should be starting to arrive normally now.
  3. 19:22 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –LoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mPaddleGrade A99.99% up3 incidentsMTTR 47mAblyGrade A99.98% up7 incidentsMTTR 7mMailgunGrade A99.96% up9 incidentsMTTR 42mPusherGrade A99.96% up2 incidentsMTTR 3h 45mResendGrade B99.87% up25 incidentsMTTR 24mInngestGrade B99.75% up14 incidentsMTTR 43mMapboxGrade C99.91% up2 incidentsMTTR 12h 38mClerkGrade C99.92% up10 incidentsMTTR 3h 26mWorkOSGrade C99.49% up21 incidentsMTTR 1h 05mStytchGrade C99.79% up7 incidentsMTTR 57mPlaidGrade F98.16% up18 incidentsMTTR 3h 38mTwilioGrade F96.40% up56 incidentsMTTR 7h 26m

README badge

Resend's live grade, for your README.

Resend grade badge
[![resend on downagain.dev](https://downagain.dev/badge/resend.svg)](https://downagain.dev/p/resend)