rewindex

ChangesHoneycombEmail notifications for SLOs, Triggers, and Anomaly Detection not sending

Honeycomb: Incident updated: Email notifications for SLOs, Triggers, and Anomaly Detection not sending

Incident updateNormal progress (rule, 100%)Changed status.honeycomb.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Honeycomb removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: identified
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-22 17:07 UTC
AddedUpdateresolved#3
Before: not present
After: Between 03:53 PM UTC to 4:08 PM UTC we saw email send failures elevate in which a small number of customers (10 enterprise, 8 self-serve, and 1 pro plan) were impacted. This came to 508 emails in total, or ~1% of our daily email send. We are working to ensure this failure mode is not able to happen again.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Thursday, October 22

2 incident changes

Cite this

Incident updated: Email notifications for SLOs, Triggers, and Anomaly Detection not sending on Honeycomb’s status page, changed 2026-10-22 17:13 UTC (change 2 of 2).

Title
Incident updated: Email notifications for SLOs, Triggers, and Anomaly Detection not sending
Vendor
Honeycomb
Date
URL
https://rewindex.com/change/re45a84103a4afe

All Honeycomb changesHoneycomb profileMarkdownJSON