Fly.io: Packet loss in ORD

What to do

Check whether you use Fly.io ORD - Chicago, Illinois (US) in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 1h 44m it lasted.
Anything that failed between 2026-08-31 06:26 UTC and 2026-08-31 08:10 UTC may need a replay.
Subscribe to Fly.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=fly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingAug 31, 2026, 6:26 AM UTC
Due to an upstream provider, we are seeing ~50% packet loss on a subset of hosts in ORD. Some MPG clusters in ORD are slow to replicate as a result.
provider
monitoringAug 31, 2026, 7:39 AM UTC
Packet loss in ORD is improving and impacted services are recovering; we’re continuing to monitor for intermittent issues
provider
resolvedAug 31, 2026, 8:10 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Fly.io still down?

No, this incident was resolved 2026-08-31 08:10 UTC. For Fly.io's live state, see https://down.guide/fly.

How long did it last?

1h 44m, from 2026-08-31 06:26 UTC to 2026-08-31 08:10 UTC, by the times Fly.io posted.

What was affected?

Fly.io named ORD - Chicago, Illinois (US) in us.

What caused it?

Fly.io hasn't published a root cause. If it does, it shows here.

Where does this come from?

Fly.io's official status page, https://status.flyio.net, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.