GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Fly.io reset all connections between Fly.io accounts and GitHub. Automatic deploys and dashboard deploys from a GitHub repository fail until you reconnect. Running apps and machines are not affected. Fly.io reports the state as monitoring. Sign in to Fly.io with GitHub again and approve the authorization screen to restore GitHub deploys.
State
Monitoring
Started
Ongoing for
45 min
Worst impact
Notice
Timeline
1 updateMonitoring
45 min 100%
Updates
Times in UTCAs posted by Fly.io
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 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. Deploys with flyctl, and deploys from your own GitHub Actions workflows using a [Fly.io](http://Fly.io) API token, are not affected.
Fly.io in the last 90 days
Full historyIncidents in 90 days
26
Days with an incident
20
Median duration
1 h 22 min
This incident
45% shorter than the median
Other Fly.io incidents
All incidentsFly.io·LAX region outage
Fly.io reports a major outage in the LAX region. Apps and Managed Postgres clusters in the LAX region were unreachable. The LAX region is now online and works correctly, but the datacenter has reduced redundancy. Fly.io continues to monitor.
Fly.io·IPv6 egress issues on a subset of IAD hosts
IPv6 egress did not work on a subset of IAD hosts in Fly.io. The issue came from an upstream provider. Fly.io reported that the incident is resolved and that all affected hosts are back to normal. The incident lasted 22 minutes.
Fly.io·Emergency network maintenance on a subset of hosts in ORD
Fly.io reports that some machines in ORD were unreachable. A small subset of MPG clusters ran with reduced HA. Fly.io says the incident is resolved and the affected hosts are back online. The incident lasted about 14 minutes.
Fly.io·Elevated Machine start failures in ARN
Fly.io reported elevated Machine start failures in the ARN region. Fly.io fixed the problem and reports that the incident is resolved. The incident lasted 61 minutes.
Fly.io·Emergency maintenance in IAD
Fly.io reports an emergency network maintenance in the IAD region. Machines on some hosts were unreachable. Fly.io reports that the maintenance is complete and the incident is resolved. The incident lasted 38 minutes.
Follow Fly.io
Your coding agent knows when Fly.io is down, and tells you when a failure is theirs, not yours. You can also get Fly.io incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "fly" and tell me if Fly.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=fly/feed subscribe https://outages.live/feed.xml?providers=flyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane