Flightcontrol incident

Consul cluster degradation

Resolved after 3 hours 19 minutes, on June 4, 2026.

resolved Jun 04, 2026, 05:03 PM UTC

We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.

Started
Jun 04, 2026, 01:44 PM UTC
Resolved
Jun 04, 2026, 05:03 PM UTC
Duration
3h 19m
Detected by Pingoru
Jun 04, 2026, 01:44 PM UTC

Update timeline

  1. identified Jun 04, 2026, 01:44 PM UTC

    One of our Consul clusters is in degraded state due to a failed node. This can cause issues with LiteFS primary node selection, Unmanaged Postgres (14.x and older *only*), and creation of new Unmanaged Postgres clusters. Impact is limited to these legacy products and does not affect deployments, running Fly applications in general, or Managed Postgres clusters.

  2. monitoring Jun 04, 2026, 04:02 PM UTC

    We have restored the degraded Consul cluster and are monitoring for stability. All affected functionality should now be working correctly: Unmanaged Postgres and LiteFS with dynamic leases.

  3. resolved Jun 04, 2026, 05:03 PM UTC

    We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.

Your product runs on more than Flightcontrol

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →