Degraded Ingest due to database connectivity issues

What to do

• Check whether you use Honeycomb api.honeycomb.io - US1 Event Ingest. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 24m it lasted.

  Anything that failed between 2026-03-10 13:50 UTC and 2026-03-10 14:14 UTC may need a replay.

• Subscribe to Honeycomb's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=honeycomb works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Honeycomb 3

1. investigatingMar 10, 2026, 1:50 PM UTC

   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.

   provider

2. monitoringMar 10, 2026, 1:56 PM UTC

   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.

   provider

3. resolvedMar 10, 2026, 2:14 PM UTC

   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).

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.