Resend experienced a minor incident on September 16, 2026 affecting Batch Emails and Single Email and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 15, 2026, 03:49 PM UTC
Status: 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. Affected components Broadcast Emails (Partial outage)
- monitoring Sep 15, 2026, 04:22 PM UTC
Status: 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. Affected components Broadcast Emails (Degraded performance)
- resolved Sep 15, 2026, 05:09 PM UTC
Status: 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. Affected components Broadcast Emails (Operational)
- resolved Sep 16, 2026, 03:04 PM UTC
Status: 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. Affected components Single Email (Operational) SMTP (Operational) Broadcast Emails (Operational) Batch Emails (Operational)