Live / Fly.io / Incident
Fly.io: GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Fly.io · fly.ioResolved2026-11-12 21:46 UTC
Public — what happened
Summary
Fly.io said it reset every link between customer accounts and GitHub at 17:34 UTC on November 12, and the incident is still being monitored. The company said running apps and machines are unaffected and users were not signed out, but until people reconnect, automatic deploys from GitHub pushes and launching or redeploying apps from a GitHub repository in the dashboard will fail, and the dashboard may show an expired-token message. Fly.io said the fix is to sign in to Fly.io with GitHub again and approve GitHub's authorization screen, and that deploys using flyctl or GitHub Actions with a Fly.io API token are not affected. Fly.io did not state a cause in the text provided.
Timeline
- Started — 2026-11-12 18:09 UTC
- Monitoring — 2026-11-12 18:09 UTC
- Resolved — 2026-11-12 21:46 UTC · 3h 37m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Fly.io against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Fly.io: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Fly.io report →
More from Fly.io
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.