Skip to content
OutageDeck

Incident detail

Consul cluster degradation

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Fly.io breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Fly.io alerts work

Timeline

Incident updates

Every update Fly.io posted, oldest to newest, exactly as it appeared on their official status page.

  1. Identified

    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

    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

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

Keep exploring

More from Fly.io

Neighboring incidents on Fly.io's timeline and the rest of their record on OutageDeck.

← Older incident

Issues with flyctl ssh console and Machines OIDC

Newer incident →

Capacity issues in ARN region

All Fly.io incidentsFly.io live status