Resend incident
Inbound emails with incorrect "To" field when forwarded
Resend experienced a minor incident on May 8, 2026 affecting Batch Emails and General API and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 07, 2026, 02:54 PM UTC
Status: Identified 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. Affected components SMTP (Operational) Broadcast Emails (Operational) Batch Emails (Operational) Webhooks (Degraded performance) Single Email (Operational) Dashboard (Operational) Email Events (Operational) General API (Operational) Website (Operational)
- resolved May 08, 2026, 05:47 PM UTC
Status: Resolved We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed. Affected components Single Email (Operational) Dashboard (Operational) General API (Operational) Webhooks (Operational) Email Events (Operational) SMTP (Operational) Broadcast Emails (Operational) Batch Emails (Operational) Website (Operational)