Live / Fly.io / Incident
Fly.io: LHR network issues
Fly.io · fly.ioMajor incidentResolved2026-10-08 06:00 UTC
Public — what happened
Summary
Fly.io reported a major network problem in its London (LHR) region beginning at 05:40 UTC on 2026-10-08. The company said the issue involved how its network routes were being advertised to the wider internet, which left regional anycast and static outbound IP addresses in London not working, with anycast traffic sent to nearby regions instead. By 05:53 UTC Fly.io said it had restored the affected routing in London and was watching for recovery, and it marked the incident resolved at 06:00.
Timeline
- Started — 2026-10-08 05:40 UTC
- Identified — 2026-10-08 05:40 UTC
- Monitoring — 2026-10-08 05:53 UTC
- Resolved — 2026-10-08 06:00 UTC · 20 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Fly.io against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Fly.io: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Fly.io report →
More from Fly.io
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.