- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Customer Applications
What to do
Check whether you use Fly.io Customer Applications. 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 35m it lasted.
Anything that failed between 2026-08-23 01:28 UTC and 2026-08-23 02:04 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.
Updates from Fly.io 3
- investigating
We are investigating network issues in the Los Angeles region. Apps may experience higher latency or be unreachable at this time.
provider
- monitoring
Upstream networking issues have resolved.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f18458a9d7
Is Fly.io still down?
No, this incident was resolved 2026-08-23 02:04 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
35m, from 2026-08-23 01:28 UTC to 2026-08-23 02:04 UTC, by the times Fly.io posted.
What was affected?
Fly.io named Customer Applications.
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.