Live  /  Fly.io  /  Incident

Fly.io: Capacity issues in GRU region

Fly.io · fly.ioMinor incidentResolved2026-10-20 23:53 UTC
Public — what happened

Summary

Fly.io reported a minor incident beginning at 16:54 UTC on 2026-10-20 in which servers in its GRU region were running low on available room. The company said that launching or starting Machines there might not work, and that remote builders in that region were affected too. Fly.io said it was adding more capacity and suggested that customers temporarily use the EWR or IAD regions instead. The incident was marked resolved at 23:53 UTC the same day.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 44, 2026, our weekly internet health report.

The full archive is on the Fly.io status & history page.

Related: Fly.io status & history. SquidGrid is not affiliated with Fly.io.