Fly.io status
Is Fly.io down? This is Fly.io’s current status, its components and its recent incidents, read from Fly.io’s official status page and refreshed every 2 minutes.
All Systems Operational
As reported by Fly.io’s status page, read Nov 15, 2026, 08:06 UTC.
Components
| Component | Status |
|---|---|
| Customer Applications | Operational |
| Dashboard | Operational |
| Machines API | Operational |
| AMS - Amsterdam, Netherlands | Operational |
| ARN - Stockholm, Sweden | Operational |
| BOM - Mumbai, India | Operational |
| CDG - Paris, France | Operational |
| DFW - Dallas, Texas (US) | Operational |
| EWR - Secaucus, NJ (US) | Operational |
| FRA - Frankfurt, Germany | Operational |
| GRU - Sao Paulo, Brazil | Operational |
| IAD - Ashburn, Virginia (US) | Operational |
| JNB - Johannesburg, South Africa | Operational |
| LAX - Los Angeles, California (US) | Operational |
| LHR - London, United Kingdom | Operational |
| NRT - Tokyo, Japan | Operational |
| ORD - Chicago, Illinois (US) | Operational |
| SIN - Singapore | Operational |
| SJC - San Jose, California (US) | Operational |
| SYD - Sydney, Australia | Operational |
| YYZ - Toronto, Canada | Operational |
| Persistent Storage (Volumes) | Operational |
| Deployments | Operational |
| Remote Builds | Operational |
| Logs | Operational |
What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.
Recent Fly.io incidents
- LAX region outage · Nov 12, 2026, 00:08 UTC · resolved, critical impact, lasted 48 h 11 min
The LAX datacenter has remained stable, and all hosts in the region are healthy. This incident is now resolved.
- GitHub connections reset - sign in with GitHub again to restore GitHub deploys · Nov 12, 2026, 18:09 UTC · resolved, lasted 3 h 37 min
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…
- Intermittent errors pushing images to Fly.io Registry · Nov 11, 2026, 16:17 UTC · resolved, lasted 0 min
Between 04:17 UTC to 13:24 UTC today we saw intermittent errors pushing to the Fly registry from some hosts. Customers may have seen deployments fail due to image push errors when using Fly or Depot hosted remote builders during this period. A fix was implemented and we are no…
- IPv6 egress issues on a subset of IAD hosts · Nov 6, 2026, 09:55 UTC · resolved, minor impact, lasted 23 min
All affected hosts are back to normal.
- Emergency network maintenance on a subset of hosts in ORD · Nov 4, 2026, 05:01 UTC · resolved, minor impact, lasted 14 min
The affected hosts are back online
- Elevated Machine start failures in ARN · Nov 2, 2026, 12:34 UTC · resolved, minor impact, lasted 1 h 1 min
We have fixed the underlying issue caused failed Machine starts in ARN
- Emergency maintenance in IAD · Nov 2, 2026, 11:19 UTC · resolved, major impact, lasted 38 min
This maintenance is complete.
- Outbound IPv4 connectivity failures in ARN, JNB, and GRU · Nov 1, 2026, 18:50 UTC · resolved, minor impact, lasted 2 h 10 min
We've fixed affected regions and everything is back to normal.
- Slow image pulls delaying Machine starts in IAD · Oct 30, 2026, 20:24 UTC · resolved, minor impact, lasted 1 h 28 min
Image pull times in IAD have returned to normal.
- Elevated Depot Failures · Oct 29, 2026, 22:52 UTC · resolved
Between 22:00 and 22:30 UTC, we saw elevated errors provisioning Depot hosted Builders due to [an upstream incident impacting Depot's control plane](https://status.depot.dev/incidents/01M64NVFDKM930PX39YM4275DN). During this time customers may have seen deploys fail with an…
- Elevated issues with the Machines API · Oct 29, 2026, 20:40 UTC · resolved, minor impact, lasted 48 min
The incident has been resolved.
- Creating WireGuard peers in ARN is currently broken · Oct 29, 2026, 11:01 UTC · resolved, lasted 4 h 48 min
The ARN WireGuard gateways are up
- Degraded networking to AWS IPs · Oct 26, 2026, 14:34 UTC · resolved, lasted 6 h 6 min
This incident has been resolved, connectivity from AWS to all of our hosts is back to normal.
- Packet loss in IAD · Oct 26, 2026, 01:50 UTC · resolved, minor impact, lasted 2 h 33 min
The congestion affecting our upstream provider has been resolved. We are observing a return to normal levels of networking performance in IAD region.
- MPGv2 IAD control plane is read-only · Oct 25, 2026, 10:46 UTC · resolved, minor impact, lasted 17 min
Control plane operations in IAD, including resizing and changing plans, are working normally again.
Source: Fly.io, Fly.io’s public status page, read Nov 15, 2026, 08:06 UTC. Uptimely is not affiliated with Fly.io; incident text is Fly.io’s own.
Is it down for you, or for everyone?
A status page shows what the vendor has confirmed, which often lags what users see. Run a live check of fly.io to see whether it answers right now.
Get alerted when Fly.io has an incident
Uptimely’s External Status Page monitor watches Fly.io’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services.
Status of similar services
- Vercel status
- Netlify status
- Render status
- DigitalOcean status
- Linode status
- Webflow status
- Squarespace status
- Wix status
Is Fly.io down right now?
The status at the top of this page is Fly.io's own, read from its public status page every couple of minutes. It shows what Fly.io's team has confirmed. For an independent check of whether fly.io answers right now, use the live check on the is-it-down page.
Where is Fly.io's official status page?
Fly.io publishes its status at https://status.flyio.net. This page shows the same data with the recent incident history in one place, and links each incident to Fly.io's own write-up.
Why does Fly.io not work for me when its status says operational?
A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause.
How can I get alerted when Fly.io has an incident?
Add an External Status Page monitor in Uptimely pointed at https://status.flyio.net. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when Fly.io reports a problem, beside the monitors for your own services.
Verified by the Uptimely team.