FLY.IO · Vendor
NO FIX YET · SEE WHAT TO DO
Fly.io reset all links between customer accounts and GitHub on November 12, so automatic and dashboard deploys from GitHub repositories fail until the connection is restored. Running apps and machines are not affected and users were not signed out, so this is an availability incident rather than a confirmed data exposure.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that deploy Fly.io apps automatically from GitHub repositories through the Fly.io GitHub integration are affected, because those deploys fail until the connection is re-authorized. Deploys made with flyctl or with GitHub Actions using a Fly.io API token are not affected, and running apps and machines are not affected.
Not affected if api-token-deploys, flyctl-deploys, no-github-integration
Who cares deploys, fly, fly.io, github, hosting, security
At 17:34 UTC on November 12 we reset all connections between Fly.io accounts and GitHub. Running apps and machines are not affected, and you have not been signed out of 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 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 API token, are not affected.
This page as ·
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.