Consul cluster degradation

Summary

Consul cluster degradation

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

• Started

  Jun 4, 2026 · 1:44 PM

• Resolved

  Jun 4, 2026 · 5:03 PM

• Duration

  3h 19m

• Severity

  None

• ◆

  Identified

  Jun 4 · 1:44 PM Fly.io

  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.

• ◉

  Monitoring

  Jun 4 · 4:02 PM Fly.io

  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.

• ✓

  Resolved

  Jun 4 · 5:03 PM Fly.io

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