Email shows Delivered in Resend but the recipient never got it

Not specified by the original author.

TL;DR: Delivered only means the recipient's server accepted the message with a 250 OK. After that the server can inbox it, spam-folder it, queue it, or discard it, and providers share nothing about that step. Confirm the cause: in Resend, Delivered is set once the recipient server accepts the email with a 250 OK response. Note the distinction from a bounce: a bounce means the server rejected it and Resend tells you why.

The error

the Resend dashboard and webhooks show delivered, but the recipient insists nothing arrived.

The fix

1. Confirm the cause: in Resend, Delivered is set once the recipient server accepts the email with a 250 OK response. What happens next (inbox, spam, queue, discard) is decided by the inbox provider, corporate filters, or the user's own rules, and providers do not share how they filter afterward.
2. If you can reach the recipient, ask them to check: corporate spam filters or firewalls, personal inbox filtering rules, promotional/spam/deleted folders, and group inboxes or queues. If they find it, have them mark it Not Spam or allowlist your sending domain.
3. If you cannot reach the recipient, improve your odds for next time: configure DMARC to build trust with the provider, warm up new domains slowly before large volumes, make all links use your own sender domain, turn off open and click tracking, reduce images, and keep wording succinct and non-spammy.
4. Note the distinction from a bounce: a bounce means the server rejected it and Resend tells you why. Delivered-then-missing is a downstream filtering decision with no signal back.
5. Verify: ask the recipient to search all folders including spam for your sender address, and check whether corporate quarantine held it.

When to use this

• You are seeing this exact error message; match the block above, not just part of it.
• The failing call matches the scenario in the title: Email shows Delivered in Resend but the recipient never got it.
• You want the fastest verified fix before digging through logs.

When not to use this

• Your error text differs from the block above; close cousins often have different causes.
• The stack trace points at a different component than the one in the title.
• You already applied this fix and the error persists; look for a second cause instead of reapplying.

Compatibility

• Not pinned to a specific version; follows current Email behavior.

Documented in Resend knowledge base: Delivered is marked on the recipient server's 250 OK acceptance; the server may then inbox, queue, spam-folder, or discard; providers share no info on later filtering; recipient should check spam/filters/quarantine and mark Not Spam or allowlist; sender-side improvements include DMARC, warm-up, own-domain links, tracking off, fewer images. Evidence: resend.com/docs/knowledge-base/what-if-an-email-says-delivered-but-the-recipient-has-not-received-it.