Resend incident

Inbound emails with incorrect "To" field when forwarded

Resolved after 1 day 2 hours, affecting Batch Emails and General API and 1 more, on May 7, 2026.

resolved May 08, 2026, 05:47 PM UTC

We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed.

Started
May 07, 2026, 02:54 PM UTC
Resolved
May 08, 2026, 05:47 PM UTC
Duration
1d 2h
Detected by Pingoru
May 07, 2026, 02:54 PM UTC

Affected components

Batch EmailsGeneral APIEmail EventsWebhooksWebsiteDashboardSingle EmailSMTPBroadcast Emails

Update timeline

  1. identified May 07, 2026, 02:54 PM UTC

    A recent change to how Resend processes inbound emails affected customers who receive emails via server-side forwarding rules, where a mail server automatically redirects an email to a different address without rewriting its headers. When an email is forwarded this way to a Resend inbound address, the to field in the inbound webhook payload began reflecting the original "To" header (e.g. [email protected]) rather than the address that actually received the delivery (e.g. your Resend inbound address). Direct emails and client-side forwards were not affected.

  2. resolved May 08, 2026, 05:47 PM UTC

    We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed.

Your product runs on more than Resend

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →