Honeycomb: Degraded Ingest due to database connectivity issues
Affected components: api.honeycomb.io - US1 Event Ingest
Timeline of updates
- investigating
We are currently seeing elevated errors in connecting to some of our databases, which results in low amounts of Ingest traffic being rejected. We are looking into correcting the situation.
- monitoring
We have stabilized the cluster and are monitoring the state while investigating to understand what triggered the degradation. Overall, 0.04% traffic was rejected with an error due to this degradation during the 20 minute window we were impaired.
- resolved
This incident is now resolved.
We are also noting that some other parts of honeycomb (the query UI) may have seen spurious failures as well during the impacted period (13:22—13:44 UTC).
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.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9b004787ce4f7a98…
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: minor) posted by Honeycomb, started 2026-03-10 13:50 UTC, resolved after 24 min, 3 update(s).
- Title
- Degraded Ingest due to database connectivity issues
- Vendor
- Honeycomb
- Date
- URL
- https://rewindex.com/company/honeycomb/incidents/c3r87p5py703
Honeycomb profileRecent Honeycomb incidentsAll outages on March 10, 2026Honeycomb in March 2026MarkdownJSON