Provider
ResendIncident detail
Inbound emails with incorrect "To" field when forwarded
Active incidentMinor
Timeline window
Started
Outage alerts
Get alerted the next time Resend breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Resend posted, oldest to newest, exactly as it appeared on their official status page.
Resolved
We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed.
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. support@yourcompany.com) rather than the address that actually received the delivery (e.g. your Resend inbound address).
Direct emails and client-side forwards were not affected.
Keep exploring
More from Resend
Neighboring incidents on Resend's timeline and the rest of their record on OutageDeck.