Keep sending with Resend. Tatami reads its delivery events and shows you what bounced, what got blocked, and what to fix next.
No DNS changes. No rerouting mail. See the Resend setup.
Resend
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/resend/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through Resend. Tatami only reads the events it reports.
Product email needs monitoring after the API call succeeds. Tatami connects to Resend webhooks to show delivery outcomes, delays, bounces, complaints, and failures with message details. Add tenant and category tags to give your team useful context when investigating onboarding emails, account notifications, or traffic from several customers.
Review email.delivery_delayed events alongside delivered outcomes. Use the message identifier and subject to investigate time-sensitive application messages that have not completed delivery.
Tatami retains the bounce message, type, and subtype supplied by Resend. Inspect them with the affected recipient domain before deciding how to address the failure.
Add tenant_id and category tags when sending. Tatami extracts those tags into event metadata, helping you investigate problems associated with a customer or application message type.
Tatami explains each bounce, watches your IPs and domains, and tells your team when something breaks.
1,240 Outlook bounces since 9:00, all from 198.51.100.24.
Microsoft is blocking that IP. Gmail and Yahoo look normal.
Also works in Claude Code and Codex through mcp.tatamimonitor.com.
Google, Yahoo, and Microsoft signals for every IP and domain.
Outlook is bouncing mail from 198.51.100.24 with 550 5.7.1 S3150.
Also sent to
Discord
Email
Rules on bounces, blocklists, volume, and throttling.
One filtered link per customer.
Point the Resend webhook at Tatami. Your mail keeps sending the same way.
Add a Resend source to your Tatami project and copy its webhook URL. Give it a name that identifies the application or sending environment you are connecting.
In the Resend dashboard, add a webhook endpoint using the Tatami URL. Enable email.delivered, email.delivery_delayed, email.bounced, email.complained, and email.failed, then save the endpoint.
Send a test message through Resend and confirm its delivery event appears in Tatami. Include tenant_id and category tags if you need customer and message-type context.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
Tatami extracts tenant_id and category from the tags supplied with Resend events and retains the tags collection. Include those values in your sends when you want customer and message-category context during delivery investigations.
Tatami skips sent, opened, and clicked events. The monitoring view focuses on deliveries, delivery delays, bounces, complaints, and failures. A delivered event indicates acceptance by the receiving server and does not prove inbox placement.
No. A delivery event means the receiving mail server accepted the message. It does not confirm whether it reached the inbox or spam folder. Tatami monitors the delivery events you send, bounce reasons, and sender reputation to help you investigate deliverability issues; it does not measure inbox placement.
Providers are unlimited on every plan. Connect the rest of your email stack the same way.
PostShiba deliverability tool
Amazon SES deliverability tool
Customer.io deliverability tool
Smartico deliverability tool
Bento deliverability tool
$10 per million emails. First 100 IPs free. See pricing
Connect the webhook and watch your first Resend events arrive in minutes.