- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Fly.io. 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 38m it lasted.
Anything that failed between 2026-10-01 01:11 UTC and 2026-10-01 02:49 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 5
- investigating
We're investigating delayed ingestion of app logs across all regions. New logs from machines may not be visible, but past logs are still available.
provider
- identified
We've identified the cause of the slowed log ingestion and are working on a fix.
provider
- identified
We've resolved the ingestion issue and our systems are processing the backlog of app logs. No logs have been lost.
provider
- monitoring
The backlog of app logs has been processed, and we're monitoring the health of the log cluster. No logs were lost.
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-cc1ecbaa65
Is Fly.io still down?
No, this incident was resolved 2026-10-01 02:49 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
1h 38m, from 2026-10-01 01:11 UTC to 2026-10-01 02:49 UTC, by the times Fly.io posted.
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.