Live / Fly.io / Incident
Fly.io: Creating WireGuard peers in ARN is currently broken
Fly.io · fly.ioResolved2026-10-29 15:49 UTC
Public — what happened
Summary
Fly.io said that setting up new WireGuard peers in its ARN region was not working, starting at 11:01 UTC on 2026-10-29. The company reported that the gateways for that region could not be reached, and it suggested that customers choose a different region while the problem lasted. Fly.io marked the incident resolved at 15:49 UTC the same day and did not say in its posted text what lay behind it.
Timeline
- Started — 2026-10-29 11:01 UTC
- Identified — 2026-10-29 11:01 UTC
- Resolved — 2026-10-29 15:49 UTC · 4h 48m 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 45, 2026, our weekly internet health report.