Honeycomb: Delay in SLO Burn Alert and Service Map Processing
Timeline of updates
- resolved
Service maps and SLOs are now back to being up to date. Burn alerts that might have fired while the service was impaired, but for which the SLO still has remaining budget and is no longer in danger of exhaustion may not have been sent. Any SLO that is still in danger of budget exhaustion or was exhausted during this incident will still have their notifications sent.
From Honeycomb’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.honeycomb.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Honeycomb, started 2023-06-16 22:48 UTC, resolved after 42 min, 1 update(s).
- Title
- Delay in SLO Burn Alert and Service Map Processing
- Vendor
- Honeycomb
- Date
- URL
- https://rewindex.com/company/honeycomb/incidents/d0852flvg56s
Honeycomb profileRecent Honeycomb incidentsAll outages on June 16, 2023Honeycomb in June 2023MarkdownJSON