Consul cluster degradation
Jun 4, 13:44 UTCJun 4, 17:03 UTC
Duration
3h 19m
Impact
Informational
Root cause
Not disclosed
Fly.io, 90 days
52 incidents
Affected
Not listed by the vendor.
Final update
We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.
Timeline
- Resolved · Jun 4, 17:03 UTC
We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.
More from Fly.io
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2416:31 UTC | State database issues in GRU | major | 2h 40m |
| Sep 2414:51 UTC | Private Networking issues (6PN) | major | 46m |
| Sep 2318:44 UTC | Partial Sprites outage | major | 7h 28m |
| Sep 2314:47 UTC | Elevated private networking errors | major | 36m |
| Sep 2312:42 UTC | Upstash unavailability in FRA region | major | 1h 22m |
| Sep 2306:18 UTC | IPv6 Networking Issues in DFW | major | 5h 57m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.