Fly.io incident

Consul cluster degradation

Notice Ongoing View vendor source →

Fly.io is currently experiencing a notice incident, which began 2h ago. The vendor's full update timeline is below.

Started
Jun 04, 2026, 01:44 PM UTC
Resolved
Ongoing
Duration
● 2h 14m
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.