Starting next month: a public deliverability report, every month

Most providers talk about deliverability in the abstract. We'd rather publish the actual numbers, on a schedule, and let them speak for themselves. This post is the commitment: what the monthly report will contain and where the numbers come from. It isn't the report itself. We don't have a full calendar month of production traffic yet, and we're not filling that gap with estimates.

What gets published, every month

• Bounce rate and complaint rate, in aggregate across the shared sending pool
• Median and p95 time from accepted to delivered
• Any SES reputation events that affected sending (throttling, pauses) and how long they lasted
• A plain-language note on anything that went wrong, and what changed as a result

Where the numbers come from

Every figure is pulled directly from the same event pipeline that feeds your own dashboard and webhooks (see the data-flow diagram on the GDPR page): SES delivery events ingested into Postgres, aggregated for the calendar month, no manual adjustment. If a number looks bad, it gets published anyway.

Why there's no report yet

A single day or week of data is noisy and easy to cherry-pick. The first report publishes once a full calendar month of real sending volume exists to summarize. Until then, this page is the commitment, not the content.