Keep sending with Amazon SES. 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 Amazon SES setup.
Amazon SES
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/amazon_ses/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through Amazon SES. Tatami only reads the events it reports.
An accepted SES API request does not tell you how delivery ended. Connect Amazon SES event publishing through SNS to Tatami for a view of bounces, complaints, delivery delays, and other outcomes. Keep configuration-set and message-tag context available while investigating your application's sending traffic across AWS email workflows.
Review SES bounce types, subtypes, diagnostic information, and complaint details where supplied. Identify the recipient domains and sending traffic involved before changing your email practices.
Bring DeliveryDelay, Reject, and RenderingFailure events into your investigation. Understand whether the reported problem happened during delivery or before the message could be sent.
Include customer, campaign, and category identifiers as SES message tags. Keep that context alongside configuration-set details so your team can investigate the relevant application traffic.
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 Amazon SES webhook at Tatami. Your mail keeps sending the same way.
Create an Amazon SES source in Tatami and copy its webhook URL. Name the source for the AWS account or email workload you want to monitor.
Add an SNS event destination to an SES configuration set. Subscribe the Tatami URL to the SNS topic over HTTPS and enable delivery, bounce, complaint, reject, rendering failure, and delivery delay events.
Confirm that the SNS subscription is active, then send a test email using the configuration set. Verify its delivery outcome and any message tags in Tatami.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
The documented integration uses an SES configuration set with an SNS event destination and an HTTPS subscription to your Tatami webhook. Make sure your application specifies that configuration set when sending; messages outside it will not publish through that destination.
Yes, when RenderingFailure events are enabled in SES event publishing. Tatami retains those events as bounced outcomes with the original payload. They describe a template-rendering problem, so inspect the event details rather than assuming the recipient address is invalid.
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
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 Amazon SES events arrive in minutes.