Fly.io incident
GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Ongoing since 06:09 PM UTC.
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 with flyctl, and deploys from your own GitHub Actions workflows using a Fly.io: http://Fly.io API token, are not affected.
Update timeline
- monitoring Nov 12, 2026, 06:09 PM UTC
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 with flyctl, and deploys from your own GitHub Actions workflows using a Fly.io: http://Fly.io API token, are not affected.
Your product runs on more than Fly.io
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services