Fly.io: GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Is it fixed? Yes.
Resolved after 3 h 41 min. First reported Nov 12, 18:09 UTC, resolved Nov 12, 21:50 UTC. The vendor posted it on its status page first.
What happened
Fly.io reset all connections between accounts and GitHub, causing automatic and dashboard-initiated deploys from GitHub repositories to fail. Running apps and machines remain unaffected, but users must manually sign in with GitHub again to restore deploys.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on status page
GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Source - Official statement
Status: Monitoring At 17:34 UTC on November 12 we reset all connections between Fly.io: http://Fly.io accounts and GitHub.
Source - Official statement
⚠️ Fly.io is reporting an incident: GitHub connections reset - sign in with GitHub again to restore GitHub deploys Monitoring: io: http://Fly.io accounts and GitHub.
Source - Official statement
✅ Resolved: Fly.io - GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
Show all 6 updatesHide the full timeline
- First report on status page
GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Source - Official statement
Status: Monitoring At 17:34 UTC on November 12 we reset all connections between Fly.io: http://Fly.io accounts and GitHub.
Source - Confirmed on Bluesky post
⚠️ Fly.io is reporting an incident: GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Source - Official statement
⚠️ Fly.io is reporting an incident: GitHub connections reset - sign in with GitHub again to restore GitHub deploys Monitoring: io: http://Fly.io accounts and GitHub.
Source - Official statement
✅ Resolved: Fly.io - GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
Evidence
3 reports · 1 Status, 2 BlueskyShow
- [1]Status First reportGitHub connections reset - sign in with GitHub again to restore GitHub deploys(opens official status page in a new tab)
Status: Monitoring 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…
by flyio status
- [2]Bluesky⚠️ Fly.io is reporting an incident: GitHub connections reset - sign in with GitHub again to restore GitHub deploys(opens the official status page in a new tab)
⚠️ Fly.io is reporting an incident: GitHub connections reset - sign in with GitHub again to restore GitHub deploys Monitoring: 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 r… t.lpl.dev/jWlJfJx
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 1comments96% match
- [3]Bluesky✅ Resolved: Fly.io - GitHub connections reset - sign in with GitHub again to restore GitHub deploys(opens the official status page in a new tab)
✅ Resolved: Fly.io - GitHub connections reset - sign in with GitHub again to restore GitHub deploys
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments94% match
FAQ
What happened in the Fly.io outage?
Fly.io reset all connections between accounts and GitHub, causing automatic and dashboard-initiated deploys from GitHub repositories to fail. Running apps and machines remain unaffected, but users must manually sign in with GitHub again to restore deploys.
What is affected by the Fly.io outage?
Fly.io. Also affected at the same time: GitHub.
When did the Fly.io outage start and end?
It started Nov 12, 18:09 UTC and was resolved Nov 12, 21:50 UTC, after 3 h 41 min.
How do I get alerts for Fly.io?
Subscribe to the Fly.io RSS feed for every new Fly.io incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Fly.io is down. Fly.io feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 3 reports from 2 independent sources, including the vendor’s own status page.