{"id":"INC-fly-01M78F5YHXG03WMZ4E3MMDTZ4B","kind":"incident","aliases":[],"related":[],"title":"Fly.io: GitHub connections reset - sign in with GitHub again to restore GitHub deploys","description":"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).\n\nUntil you reconnect:\n\n- The dashboard may show “Your GitHub SSO token seems to have expired”.\n- Automatic deploys on push to a connected GitHub repository will fail.\n- Launching or redeploying an app from a GitHub repository in the dashboard will fail.\n  \n  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.\n  \n  Deploys with flyctl, and deploys from your own GitHub Actions workflows using a [Fly.io](http://Fly.io) API token, are not affected.","summary":"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.","severity":"low","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[{"name":"Fly.io","fixed":[],"affected":"","ecosystem":"vendor"}],"ecosystems":["vendor"],"tags":["deploys","fly","fly.io","github","hosting","incident","security","vendor"],"not_affected_if":["api-token-deploys","flyctl-deploys","no-github-integration"],"how_to_check":"- Open the Fly.io dashboard and look for the message \"Your GitHub SSO token seems to have expired\" on apps linked to GitHub repositories.\n- Check whether auto-deploys from a connected GitHub repository have failed since 17:34 UTC on November 12.","fix":"- Sign in to Fly.io with GitHub again and approve the GitHub authorization screen; the person who originally connected each repository must do this for its auto-deploys to resume.","status":"open","published_at":"2026-11-12T18:09:07+00:00","first_seen_at":"2026-11-12T18:10:52+00:00","triaged_at":"2026-11-12T18:11:24+00:00","updated_at":"2026-11-12T18:11:24+00:00","category":"vendor","confidence":0.8,"triage":{"at":"2026-11-12T18:11:24Z","model":"claude-haiku-5-5","output":{"fix":"- Sign in to Fly.io with GitHub again and approve the GitHub authorization screen; the person who originally connected each repository must do this for its auto-deploys to resume.","reach":"internet","title":"Fly.io: GitHub connections reset, deploys from GitHub stop until re-authorized","impact":"low","summary":"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.","audience":"businesses","category":"vendor","nicknames":[],"who_cares":["fly.io","github","deploys"],"confidence":0.8,"fix_status":"available","needs_auth":"yes","worst_case":"GitHub-linked automatic deploys fail until the connection is re-authorized","analyst_note":"","how_to_check":"- Open the Fly.io dashboard and look for the message \"Your GitHub SSO token seems to have expired\" on apps linked to GitHub repositories.\n- Check whether auto-deploys from a connected GitHub repository have failed since 17:34 UTC on November 12.","plain_action":"","product_name":"","needs_analyst":false,"not_affected_if":["flyctl-deploys","api-token-deploys","no-github-integration"],"who_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.","user_interaction":"yes","product_ecosystem":"","needs_special_setup":"yes","severity_if_unknown":"low"},"cost_usd":0.000791,"input_tokens":4800,"output_tokens":622,"severity_before":"low"},"analyst_status":null,"analyst_note":null,"search":"'01m78f5yhxg03wmz4e3mmdtz4b':17A '12':38B,84C '17':79C '34':80C 'account':33B,92C 'action':195C 'affect':59B,101C,205C 'api':201C 'app':54B,96C,142C 'approv':163C 'author':165C 'auto':170C 'auto-deploy':169C 'automat':40B,127C 'avail':70B 'confirm':75B 'connect':3A,50B,88C,133C,181C 'custom':32B 'dashboard':42B,116C,149C 'data':76B 'deploy':13A,19B,43B,128C,171C,186C,190C 'done':184C 'expir':126C 'exposur':77B 'fail':47B,137C,151C 'fli':20B 'fly':16A 'fly.io':1A,18A,21B,27B,90C,91C,110C,111C,157C,158C,199C,200C 'flyctl':188C 'github':2A,8A,12A,22B,35B,45B,94C,120C,134C,145C,160C,167C,194C 'host':23B 'inc':15A 'inc-fly-01m78f5yhxg03wmz4e3mmdtz4b':14A 'incid':24B,71B 'launch':138C 'link':30B 'machin':56B,98C 'may':117C 'novemb':37B,83C 'origin':180C 'person':178C 'push':130C 'rather':72B 'reconnect':114C,153C 'redeploy':140C 'repositori':46B,135C,146C,174C 'reset':4A,28B,86C 'restor':11A,52B 'resum':175C 'run':53B,95C 'screen':166C 'secur':25B 'seem':123C 'show':118C,168C 'sign':5A,64B,107C,154C 'sso':121C 'token':122C,202C 'use':197C 'user':61B 'utc':81C 'vendor':26B 'workflow':196C","nicknames":[],"mitigations":[],"who_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.","tier":"C","verified":{},"analyst_revisit_at":null,"fix_status":"available","audience":"businesses","plain_action":null,"pkeys":["flyio"],"ptokens":["fly","io"],"labels":["deploys","fly","flyio","github","hosting","incident","low","security","vendor"],"campaign_type":null,"search_a":"'01m78f5yhxg03wmz4e3mmdtz4b':17A 'connect':3A 'deploy':13A 'fly':16A 'fly.io':1A,18A 'github':2A,8A,12A 'inc':15A 'inc-fly-01m78f5yhxg03wmz4e3mmdtz4b':14A 'reset':4A 'restor':11A 'sign':5A","search_b":"'12':38B 'account':33B 'affect':59B 'app':54B 'automat':40B 'avail':70B 'confirm':75B 'connect':50B 'custom':32B 'dashboard':42B 'data':76B 'deploy':19B,43B 'exposur':77B 'fail':47B 'fli':20B 'fly.io':21B,27B 'github':22B,35B,45B 'host':23B 'incid':24B,71B 'link':30B 'machin':56B 'novemb':37B 'rather':72B 'repositori':46B 'reset':28B 'restor':52B 'run':53B 'secur':25B 'sign':64B 'user':61B 'vendor':26B","search_c":"'12':84C '17':79C '34':80C 'account':92C 'action':195C 'affect':101C,205C 'api':201C 'app':96C,142C 'approv':163C 'author':165C 'auto':170C 'auto-deploy':169C 'automat':127C 'connect':88C,133C,181C 'dashboard':116C,149C 'deploy':128C,171C,186C,190C 'done':184C 'expir':126C 'fail':137C,151C 'fly.io':90C,91C,110C,111C,157C,158C,199C,200C 'flyctl':188C 'github':94C,120C,134C,145C,160C,167C,194C 'launch':138C 'machin':98C 'may':117C 'novemb':83C 'origin':180C 'person':178C 'push':130C 'reconnect':114C,153C 'redeploy':140C 'repositori':135C,146C,174C 'reset':86C 'resum':175C 'run':95C 'screen':166C 'seem':123C 'show':118C,168C 'sign':107C,154C 'sso':121C 'token':122C,202C 'use':197C 'utc':81C 'workflow':196C","cause_entry":null,"cause_path":null,"disclosures_checked_at":null,"first_public_at":"2026-11-12T18:09:07+00:00","kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"statuspage","external_id":"fly:01M78F5YHXG03WMZ4E3MMDTZ4B","url":"https://status.flyio.net/incidents/01M78F5YHXG03WMZ4E3MMDTZ4B","severity":"low","published_at":"2026-11-12T18:09:07+00:00","modified_at":"2026-11-12T18:09:07+00:00","first_seen_at":"2026-11-12T18:10:52+00:00","fetched_at":"2026-11-12T19:03:38+00:00","note":null}],"documents":[],"disclosures":[],"exploit_sources":[],"notice":"Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai"}