A Fly.io Consul cluster became degraded due to a failed node, causing issues with LiteFS primary node selection, Unmanaged Postgres (version 14.x and older), and creation of new Unmanaged Postgres clusters. The impact was limited to these legacy products and did not affect general application deployments or Managed Postgres clusters. The degraded Consul cluster was restored after 3.3 hours, resolving all affected functionality.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with