rewindex

CompaniesHoneycombIncidents

Honeycomb: Delay in SLO and errors in Trigger notifications

No impact listedStatus: resolvedStarted Resolved (34 min)2 updatesstspg.io (opens in new tab)

Affected components: ui.honeycomb.io - US1 Trigger & SLO Alerting

Timeline of updates

  1. monitoring

    An error in our production AWS configuration caused a brief interruption that affected Service Maps and caused an delay in delivering SLO notifications, and errors delivering Trigger notifications between 9:54AM UTC-5 and 10:05AM UTC-5. If any longer Triggers (1 day) would have activated within this window, they may not have sent a notification.

  2. resolved

    This incident has been resolved.

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 this record existed by then and has not been changed since, by anyone, Rewindex included.

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

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Honeycomb, started 2025-07-21 15:25 UTC, resolved after 34 min, 2 update(s).

Title
Delay in SLO and errors in Trigger notifications
Vendor
Honeycomb
Date
URL
https://rewindex.com/company/honeycomb/incidents/d2yt4kbq5n00

Honeycomb profileRecent Honeycomb incidentsAll outages on July 21, 2025Honeycomb in July 2025MarkdownJSON