Live / Fly.io / Incident
Fly.io: Historical logs are currently delayed
Fly.io · fly.ioMinor incidentResolved2026-10-13 13:50 UTC
Public — what happened
Summary
Fly.io reported a minor issue on 2026-10-13 starting at 09:25 UTC in which historical logs were arriving late. The company said a backlog in the system that takes in logs was the reason, and older log data would lag until that backlog cleared. By 11:09 UTC Fly.io said logs had caught up and it was keeping watch, and the incident was marked resolved at 13:50.
Timeline
- Started — 2026-10-13 09:25 UTC
- Identified — 2026-10-13 09:25 UTC
- Monitoring — 2026-10-13 11:09 UTC
- Resolved — 2026-10-13 13:50 UTC · 4h 25m 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 43, 2026, our weekly internet health report.