Fly.io outage, 12 November 2026
GitHub connections reset - sign in with GitHub again to restore GitHub deploys
- Started
- Resolved
- 12 Nov 2026, 21:46 UTC (after 3 h 37 min)
- Impact
- Not stated
Is this still happening?
No. Fly.io marked this incident resolved on 12 Nov 2026, 21:46 UTC, 3 h 37 min after it began.
Right now: Fly.io reports a major outage. (as of 13 Nov, 20:53 UTC) Live Fly.io status
At a glance
- Fly.io did not rate the impact of this incident.
- It was resolved after 3 h 37 min. That is longer than a typical Fly.io incident: the median of the 30 other resolved ones we recorded is 1 h 15 min.
- Fly.io had 18 other incidents in the 30 days before it.
Our summary from the Fly.io incidents we have recorded since 30 Aug 2026 - how we count.
Last update from Fly.io
At 17:34 UTC on November 12 we reset all connections between [Fly.io](http://Fly.io) accounts and GitHub. Running apps and machines are not affected, and you have not been signed out of [Fly.io](http://Fly.io). Until you reconnect: - The dashboard may show “Your GitHub SSO token seems to have expired”. - Automatic deploys on push to a connected GitHub repository will fail. - Launching or redeploying an app from a GitHub repository in the dashboard will fail. To reconnect, sign in to [Fly.io](http://Fly.io) with GitHub again and approve the authorization screen GitHub shows. Auto-deploys for a repository resume once the person who originally connected it has done this. Deploys wit...
Other Fly.io incidents
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.