Changes / Honeycomb / Query interuption due to database failover in the EU region

Honeycomb: Major incident: Query interuption due to database failover in the EU region

Summary

Honeycomb reported a major EU-region query outage after an automated database failover at 12:50 UTC affected query engine connection pools; queries failed for roughly 10 minutes before self-resolving. The listed start is 2026-05-01 13:22 UTC and resolution is 2026-05-01 12:30 UTC; computed duration is unknown.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 97%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Query interuption due to database failover in the EU region
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-05-01 13:22 UTC
AddedResolved time#5
Before: not present
After: 2026-05-01 12:30 UTC
AddedUpdateresolved#6
Before: not present
After: At 12:50, our main database underwent an automated failover. This failover led to issues with some of our query engine connection pools, and caused queries to fail for roughly 10 minutes before self resolving.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Query interuption due to database failover in the EU region (this change)
Honeycomb reported a major EU-region query outage after an automated database failover at 12:50 UTC affected query engine connection pools; queries failed for roughly 10 minutes before self-resolving. The listed start is 2026-05-01 13:22 UTC and resolution is 2026-05-01 12:30 UTC; computed duration is unknown.
Major incident

All Honeycomb changes → · Honeycomb profile · Markdown · JSON