Resend

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-10 14:00 UTC

   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...

2. monitoring 2026-10-10 14:52 UTC

   A fix is in place and we are monitoring to ensure the issue has been fixed.

3. resolved 2026-10-10 15:09 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-09 21:47 UTC

   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...

2. monitoring 2026-10-09 22:06 UTC

   Our team is monitoring to ensure the issue has been fixed.

3. resolved 2026-10-09 22:10 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 12:28 UTC

   We are currently investigating increased error rate our API. At this time, you may experience erros when sending requests to our API.

2. identified 2026-10-01 12:43 UTC

   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. monitoring 2026-10-01 13:05 UTC

   The fix has been pushed and we are now monitoring the situation.

4. resolved 2026-10-01 13:20 UTC

   We have resolved the underlying issue and service has been resumed

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-26 06:29 UTC

   We are currently investigating increased a delay in async functions, sending is not affected. You may experience longer times for domain verification

2. monitoring 2026-09-26 06:43 UTC

   We are seeing functions going back to being processed at normal rates and we’re monitoring

3. resolved 2026-09-26 09:15 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-24 14:31 UTC

   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. monitoring 2026-09-24 14:53 UTC

   We've been monitoring the operations and see no new errors in the past minutes, we're monitoring

3. resolved 2026-09-24 15:22 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 21:50 UTC

   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. monitoring 2026-09-22 22:38 UTC

   We identified the cause and we're seeing a decrease in errors, we are now monitoring

3. resolved 2026-09-22 22:50 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 18:26 UTC

   We are currently investigating increased latency webhooks, account creation/confirmation and domain provisioning.

2. monitoring 2026-09-18 18:34 UTC

   Services recovered and we are now monitoring the situation.

3. resolved 2026-09-20 18:26 UTC

   We have resolved the underlying issue and service has been resumed.

4. resolved 2026-09-20 18:27 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-18 16:17 UTC

   We have resolved the underlying issue and service has been resumed.

2. resolved 2026-09-18 16:54 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-09-16 15:58 UTC

   We're experiencing increased latency in webhook delivery.

2. resolved 2026-09-16 16:03 UTC

   Service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-16 12:06 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-15 15:49 UTC

   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...

2. monitoring 2026-09-15 16:22 UTC

   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...

3. resolved 2026-09-15 17:09 UTC

   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. resolved 2026-09-16 15:04 UTC

   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...

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-11 15:36 UTC

   We are currently investigating a full outage in the remove MCP server. During this time, requests are returning 5xx.

2. resolved 2026-09-11 15:37 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-04 19:02 UTC

   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....

2. monitoring 2026-09-04 19:08 UTC

   Events processing have been recovered and we're now draining the backlog. We're still monitoring the situation.

3. monitoring 2026-09-04 19:26 UTC

   Delayed processes have been executed. The team is still monitoring the background processes.

4. resolved 2026-09-04 19:34 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 10:05 UTC

   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. resolved 2026-09-03 10:45 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-20 04:58 UTC

   We are currently investigating increased latency in non-email sending API endpoints. Our team is investigating it.

2. identified 2026-08-20 05:17 UTC

   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. resolved 2026-08-20 05:22 UTC

   We have resolved the underlying issue and service latency has been recovered.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 19:53 UTC

   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...

2. identified 2026-08-18 21:11 UTC

   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...

3. monitoring 2026-08-18 22:33 UTC

   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. monitoring 2026-08-18 23:01 UTC

   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...

5. monitoring 2026-08-19 01:06 UTC

   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. resolved 2026-08-19 10:01 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-16 12:57 UTC

   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.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-13 17:30 UTC

   We identified an increase in errors during the domain creation process

2. resolved 2026-08-13 17:43 UTC

   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...

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-09 18:44 UTC

   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. monitoring 2026-08-09 19:17 UTC

   We have worked on a couple improvements and the queue has caught up and events should be starting to arrive normally now.

3. resolved 2026-08-09 19:22 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-08 19:50 UTC

   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...

2. resolved 2026-08-08 22:29 UTC

   Our team has mitigated the issue and this incident is fully resolved. All services are operational.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-07 15:19 UTC

   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. monitoring 2026-08-07 15:37 UTC

   We have worked on a couple improvements and the queue has caught up and events should be starting to arrive normally now.

3. resolved 2026-08-07 15:43 UTC

   We have resolved the underlying issue and service has been resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 00:00 UTC

   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. monitoring 2026-07-31 02:00 UTC

   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. resolved 2026-08-01 00:00 UTC

   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.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-30 09:58 UTC

   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. resolved 2026-07-30 16:23 UTC

   We have resolved the underlying issue, and sending test emails from [resend.dev](http://resend.dev) has resumed.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-30 20:00 UTC

   We have identified the issue with domain verifications both through the dashboard and public API.

2. resolved 2026-07-30 21:25 UTC

   We have resolved the underlying issue, and service has resumed. Domain verification has been restored, and affected verifications were re-triggered.

Excerpts are shortened. Read the full incident on Resend's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-07-29 21:14 UTC

   Between 20:15 and 20:16 UTC, a brief database disruption caused elevated error rates for approximately 45 seconds. During this window, requests to the Resend API, SMTP relay, and dashboard may have returned 5xx errors or timed out. The issue resolved automatically at 20:16 UTC...

Excerpts are shortened. Read the full incident on Resend's status page.