Honeycomb: Query and trigger degradation
Timeline of updates
- resolved
An investigation into a gradual burn into our SLOs revealed that one of the redundant instances behind one of our storage partitions suffered a hardware fault that caused it to remain online and successfully ingesting traffic, but without being adequately responsive to data queries. The hardware fault occured on 9/11 at 16:50 UTC, but lower amounts of traffic hid the issue until greater platform load earlier today, from 12:30 UTC until 18:15 UTC. Customers whose dataset spans this partition and queried it during that time span may have seen degraded query times or failing results intermittently. We believe that roughly 3% of triggers running every minute may have failed during 12:30 and 18:15 UTC. We have no record of longer triggers being significantly affected. The problem should now be resolved.
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 2021-09-13 13:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Query and trigger degradation
- Vendor
- Honeycomb
- Date
- URL
- https://rewindex.com/company/honeycomb/incidents/c0d45m8zmvwr
Honeycomb profileRecent Honeycomb incidentsAll outages on September 13, 2021Honeycomb in September 2021MarkdownJSON