Skip to content
OutageDeck

Incident detail

GitHub connections reset - sign in with GitHub again to restore GitHub deploys

Active incidentMinor

Timeline window

Started

Get alerted the next time Fly.io breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Fly.io alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Monitoring

    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.

Keep exploring

More from Fly.io

Neighboring incidents on Fly.io's timeline and the rest of their record on OutageDeck.

← Older incident

LAX region outage

All Fly.io incidentsFly.io live status