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
GradeCLast 86 days
CPRODA+SHIP

Overview

30d90d1y
Admitted uptimeCustomer time not hit, by the provider's own account. Regional and partial incidents count in part.
99.845%Grade C
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.
38h 08m

By area

CProduction
20INCIDENTS
3d 0hAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Aug 8, 2026 · 43mIncreased API and SMTP Error Rates
SEV 2Sep 3, 2026 · 39mDelay in contact webhooks delivery
SEV 2Oct 23, 2026 · 49mIntermittent latency spikes on our emails API
20 in the last 6 months.
A+Shipping
6INCIDENTS
2d 1hAFFECTED
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 3Sep 18, 2026 · 2d 0hDegraded performance
SEV 3Oct 9, 2026 · 23m · some customersDelayed new team provisioning and contact webhook delivery
6 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 down20
Sev 3 · Can't shipCan't deploy, build or manage it4
Sev 4 · PapercutDocs, status page, slow dashboard1

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 20Sev 1–2

Incident history

Oct 23, 202649mSEV 2
Intermittent latency spikes on our emails APIResend's email sending via SMTP and API experienced increased latency, causing delays, from about 15:57 to 16:47 UTC on 23 October 2026. The provider identified the issue, pushed a fix, and resolved it after monitoring.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 for about 50 minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 9–10, 202617h 22mSEV 2
Delayed new team provisioning and contact webhook delivery2 incidents
  1. Fri, Oct 9 21:47 UTC23mSEV 2
    Delayed new team provisioning and contact webhook deliveryNew team provisioning was slow and some contact-activity webhooks were delayed for about 23 minutes; 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
      New team provisioning was slow and some contact-activity webhooks were delayed for about 23 minutes; email sending and receiving were unaffected.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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
  2. Sat, Oct 10 14:35 UTC34mSEV 2
    Delayed new team provisioning and contact webhook deliveryResend had an infrastructure issue on 2026-10-10 that delayed some contact-activity webhooks and slowed setup of newly created teams. Email sending and receiving were not affected. A fix was deployed and the incident was resolved 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 2 · UNCLEAR · MEDIUM CONFIDENCE
      Contact activity webhooks were delivered late and new team setup took longer for about 35 minutes; email sending and receiving were not affected.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 1, 202652mSEV 3
Resend API with elevated error rateThe general Resend API failed about 24% of requests from 12:28 to 13:20 UTC on 1 October 2026. Email sending was not affected. The team identified the root cause, pushed a fix, and resumed service.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
    General Resend API requests failed about 24% of the time for roughly 50 minutes; email sending was not affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 was delayed for an unspecified share of customers for about 2h45m; 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 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 14M
    Async function processing was delayed for an unspecified share of customers for about 2h45m; sending was not affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 15–24, 20268d 23hSEV 2
Delayed email sending2 incidents
  1. Tue, Sep 15 15:49 UTC1h 20mSEV 2
    Delayed email sendingBroadcast emails queued and sent slowly from about 15:05 UTC on 15 September, and recovered by 17:09 UTC. A database issue from the backlog fix held about 9,200 transactional emails up to 25 minutes between 16:41 and 17:05 UTC, and some customers saw errors loading email details or lists. All emails were delivered; none were lost.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 and transactional emails were held up to 25 minutes for some accounts; no emails were lost.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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
  2. Thu, Sep 24 14:31 UTC51mSEV 2
    Intermittent errors on some dashboard and API requestsEmail sending via SMTP and API was delayed for about 50 minutes; the text does not say how many customers were hit.AI-graded · some customers
    Why this grade
    1. RULES · SEV 4
      Sev 4 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
      Email sending via SMTP and API was delayed for about 50 minutes; the text does not say how many customers were hit.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 for about 30 minutes while new domains failed verification; scope 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 for about 30 minutes while new domains failed verification; scope not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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–20, 20262d 1hSEV 2
Degraded performance2 incidents
  1. Fri, Sep 18 16:48 UTC0mSEV 4
    Degraded performanceResend reported degraded performance with no components listed and no detail on what slowed or who was hit.AI-graded
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 4 · UNCLEAR · LOW CONFIDENCE
      Resend reported degraded performance with no components listed and no detail on what slowed or who was hit.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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
  2. Fri, Sep 18 18:26 UTC2d 0hSEV 2
    Degraded performanceResend reported increased latency for webhooks, account creation and confirmation, and domain provisioning. Services recovered within about ten minutes per the monitoring update, but the incident stayed open until a resolution on 2026-09-20 without further detail on cause or scope.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
      Increased latency for webhooks, account confirmation and domain provisioning; the text does not say how widely it was hit.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 16, 20265mSEV 2
Increased latency in WebHooksWebhook delivery to customer apps was delayed for about five minutes; the text does not say how many customers were hit.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
    Webhook delivery to customer apps was delayed for about five minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 latency was high for an unstated share of requests; the text does not say which customers or regions were hit.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 latency was high for an unstated share of requests; the text does not say which customers or regions were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
1 update
  1. 12:06 UTC · resolved
    We have resolved the underlying issue and service has been resumed.
Source
Sep 11, 20260mSEV 2
Unresponsive remote MCP serverResend's remote MCP server had a full outage returning 5xx errors until it was resumed; other products were not mentioned as affected.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Resend's remote MCP server had a full outage returning 5xx errors until it was resumed; other products were not mentioned as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 2
Delays in background processes are affecting webhooks, domain verifications, and other important featuresBackground processing delays for about 30 minutes delayed webhook deliveries, domain verifications, export generation and account confirmations. Email sending was not affected. Events backlog was drained, delayed processes executed, and the underlying issue resolved.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
    Background jobs ran late, delaying webhook deliveries, domain verifications and account confirmations for about 30 minutes; email sending was unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 2
Delay in contact webhooks deliveryContact event webhooks to customers' apps were delayed for about 40 minutes; scope across customers 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
    Contact event webhooks to customers' apps were delayed for about 40 minutes; scope across customers was not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 2
Increased latency across API endpointsNon-email sending API endpoints had increased latency for about 25 minutes; no components or regions were named.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 19M
    Non-email sending API endpoints had increased latency for about 25 minutes; no components or regions were named.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 deliveryA backlog from an infrastructure change delayed contact-event webhooks by up to 3 hours. Processing was sped up and the backlog cleared by 10:01 UTC on 19 August. The provider said no contact webhooks were lost.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 event webhooks to customer apps were delayed up to 3 hours for about 14 hours; the dashboard and API were unaffected.
  3. Claude Haiku 5.5 · prompt v11 · 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 requests returned 5xx for about 7% of requests for roughly three minutes; no components were listed.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    API requests returned 5xx for about 7% of requests for roughly three minutes; no components were listed.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 3
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 affected. The fix restored normal domain creation. No domains were partially created, so retries succeed. Email sending for existing domains was unaffected.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Adding domains failed in the dashboard and public API for about 13 minutes; email sending was not affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 7–9, 20262d 4hSEV 2
Delayed contact related webhook events2 incidents
  1. Fri, Aug 7 15:19 UTC24mSEV 2
    Delayed contact related webhook eventsContact-related webhook events to customer apps were delayed for about 24 minutes; the provider did not say how many customers were hit.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 24 minutes; the provider did not say how many customers were hit.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    3 updates
    1. 15:19 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. 15:37 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. 15:43 UTC · resolved
      We have resolved the underlying issue and service has been resumed.
    Source
  2. Sun, Aug 9 18:44 UTC38mSEV 2
    Delayed contact webhook eventsContact webhook events to customer apps arrived late for about 40 minutes while the queue backlog cleared.AI-graded · some customers
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
      Contact webhook events to customer apps arrived late for about 40 minutes while the queue backlog cleared.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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
Aug 8, 202643mSEV 2
Increased API and SMTP Error RatesEmail sending API and SMTP requests returned intermittent 500 errors for some customers; the provider gave no scope or duration beyond the resolution time.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Email sending API and SMTP requests returned intermittent 500 errors for some customers; the provider gave no scope or duration beyond the resolution time.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 19:50 UTC · identified
    Our team has identified an issue causing intermittent error rates across our APIs and SMTP services. The impact is currently affecting email sending requests, which may result in intermittent 500 errors for some customers. We are actively working on mitigation and will provide further updates as we make progress.
  2. 22:29 UTC · resolved
    Our team has mitigated the issue and this incident is fully resolved. All services are operational.
Source
Aug 4, 20260mSEV 2
Contact webhook delivery backlogContact event webhooks were delivered late, with delays of up to 8 hours, starting July 30. The provider changed infrastructure to process the backlog faster. All delayed contact webhooks were delivered and latency recovered by August 1.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-related webhook deliveries were delayed by up to 8 hours for customers' endpoints; other services were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 00:00 UTC · investigating
    We are currently investigating increased latency in contact-related webhook deliveries. At this time, you may experience delays in receiving contact events on your webhook endpoints.
  2. 02:00 UTC · monitoring
    We are still noticing increased latency in contact-related webhook deliveries. Events can be delayed by up to 8 hours before being delivered. We have identified the issue and implemented infrastructure changes to process the backlog faster.
  3. 00:00 UTC · resolved
    The backlog is gone, and all delayed contact webhooks have been delivered. Delivery latency has now recovered. The new infrastructure configurations prevent this same issue from happening again.
Source
Aug 4, 20260mSEV 3
Test domain resend.dev failing test emailsTest emails from the resend.dev test domain failed with a false 'not verified' error until the fix; the main sending API was not described as 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 3 · SINGLE · MEDIUM CONFIDENCE
    Test emails from the resend.dev test domain failed with a false 'not verified' error until the fix; the main sending API was not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 09:58 UTC · identified
    Performance degradation when sending test emails from the [resend.dev](http://resend.dev) domain, which is causing the API to return a validation error stating that the domain is not verified.
  2. 16:23 UTC · resolved
    We have resolved the underlying issue, and sending test emails from [resend.dev](http://resend.dev) has resumed.
Source
Jul 30, 20260mSEV 3
Increased failure rate in Domain verificationsDomain verification failed in the dashboard and public API for an unspecified period; the text does not say how many customers were hit.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
    Domain verification failed in the dashboard and public API for an unspecified period; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 20:00 UTC · identified
    We have identified the issue with domain verifications both through the dashboard and public API.
  2. 21:25 UTC · resolved
    We have resolved the underlying issue, and service has resumed. Domain verification has been restored, and affected verifications were re-triggered.
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –MapboxGrade A+99.99% up2 incidentsMTTR 12h 38mPaddleGrade A+100.00% up3 incidentsMTTR 47mLoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mAblyGrade A99.98% up7 incidentsMTTR 7mMailgunGrade A99.96% up9 incidentsMTTR 42mPusherGrade A99.97% up2 incidentsMTTR 3h 45mInngestGrade B99.63% up14 incidentsMTTR 43mClerkGrade C99.91% up10 incidentsMTTR 3h 26mResendGrade C99.85% up25 incidentsMTTR 24mStytchGrade C99.83% up6 incidentsMTTR 2h 29mWorkOSGrade C99.42% up21 incidentsMTTR 1h 05mTwilioGrade D99.10% up60 incidentsMTTR 6h 43mPlaidGrade D98.13% up18 incidentsMTTR 3h 38m

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)