- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 29m it lasted.
Anything that failed between 2026-08-26 18:14 UTC and 2026-08-26 18:43 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 4
- investigating
We are investigating issues with our WireGuard gateways. Some CLI commands like flyctl ssh console or flyctl proxy may not work at this time. Apps continue to run.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
Our testing and monitoring indicates gateways should be back to normal; if you are still having problem using flyctl ssh console, try restarting the flyctl agent by flyctl agent restart.
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-14abbbdd62
Is Fly.io still down?
No, this incident was resolved 2026-08-26 18:43 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
29m, from 2026-08-26 18:14 UTC to 2026-08-26 18:43 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.