Is Fly.io down?
No, Fly.io is not down.
Fly.io’s status page reports no incidents, api.machines.dev and api.fly.io responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.flyio.net
- Reachable6 of 6 regionsMachines API 6/6 · Fly GraphQL API 6/6
- Reports in the last hour0Normal
Fly.io’s status page
From status.flyio.net. Read at
- Customer ApplicationsOperational
- DashboardOperational
- Machines APIOperational
- AMS - Amsterdam, Netherlands Regional AvailabilityOperational
- ARN - Stockholm, Sweden Regional AvailabilityOperational
- BOM - Mumbai, India Regional AvailabilityOperational
- CDG - Paris, France Regional AvailabilityOperational
- DFW - Dallas, Texas (US) Regional AvailabilityOperational
Show all 53 components
- EWR - Secaucus, NJ (US) Regional AvailabilityOperational
- FRA - Frankfurt, Germany Regional AvailabilityOperational
- GRU - Sao Paulo, Brazil Regional AvailabilityOperational
- IAD - Ashburn, Virginia (US) Regional AvailabilityOperational
- JNB - Johannesburg, South Africa Regional AvailabilityOperational
- LAX - Los Angeles, California (US) Regional AvailabilityOperational
- LHR - London, United Kingdom Regional AvailabilityOperational
- NRT - Tokyo, Japan Regional AvailabilityOperational
- ORD - Chicago, Illinois (US) Regional AvailabilityOperational
- SIN - Singapore Regional AvailabilityOperational
- SJC - San Jose, California (US) Regional AvailabilityOperational
- SYD - Sydney, Australia Regional AvailabilityOperational
- YYZ - Toronto, Canada Regional AvailabilityOperational
- Persistent Storage (Volumes)Operational
- DeploymentsOperational
- Remote BuildsOperational
- LogsOperational
- MetricsOperational
- SSL/TLS Certificate ProvisioningOperational
- UDP AnycastOperational
- Fly Machine Image Registry 1Operational
- Fly Machine Image Registry 2Operational
- Upstash for Redis ExtensionsOperational
- Fly Machine .internal DNS DNSOperational
- Fly Machine External DNS DNSOperational
- *.flyio.net Nameservers DNSOperational
- flydns.net DNSOperational
- Usage Metrics API BillingOperational
- Stripe API Connection BillingOperational
- CorrosionOperational
- Management Plane - ORD Managed PostgresOperational
- Management Plane - IAD Managed PostgresOperational
- Management Plane - FRA Managed PostgresOperational
- Management Plane - GRU Managed PostgresOperational
- Management Plane - LAX Managed PostgresOperational
- Management Plane - SYD Managed PostgresOperational
- Management Plane - AMS Managed PostgresOperational
- Management Plane - LHR Managed PostgresOperational
- Management Plane - NRT Managed PostgresOperational
- Management Plane - SIN Managed PostgresOperational
- Management Plane - SJC Managed PostgresOperational
- Management Plane - YYZ Managed PostgresOperational
- Phoenix.newOperational
- Support PortalOperational
- SpritesOperational
Planned maintenance, to : Network maintenance in IAD.
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 119 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.machines.dev)
By region
| Region | Machines API api.machines.dev | Fly GraphQL API api.fly.io |
|---|---|---|
| N. Virginia us-east-1 | 401 · 28 ms | 200 · 28 ms |
| Oregon us-west-2 | 401 · 174 ms | 200 · 192 ms |
| Frankfurt eu-central-1 | 401 · 58 ms | 200 · 116 ms |
| Singapore ap-southeast-1 | 401 · 18 ms | 200 · 265 ms |
| Tokyo ap-northeast-1 | 401 · 28 ms | 200 · 199 ms |
| São Paulo sa-east-1 | 401 · 27 ms | 200 · 191 ms |
Two regions check Fly.io every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Fly.io ourselves since Oct 28, 2026. Earlier days come from its status page.
38 days with problems in the last 90 days.
Recent incidents
Incidents: 17 in the last 30 days and 50 in the last 90, lasting a median of 59 min.
- Degraded networking to AWS IPsDegraded6 h 5 min
- Packet loss in IADDegraded2 h 33 min
- MPGv2 IAD control plane is read-onlyDegraded16 min
- Degraded Edge PerformanceDegradedunder 1 min
- Capacity issues in GRU regionDegraded6 h 59 min
- Fly-metrics.net Grafana Dashboard OutagePartial outage1 h 15 min
- Platform Wide Rolling Host RebootsPartial outage12 h 52 min
- Elevated errors creating apps and managing secretsDegraded2 h 3 min
- Partial FRA network issuesDegraded10 min
- Historical logs are currently delayedDegraded4 h 24 min
If Fly.io isn’t working for you
Fly.io runs apps in lightweight virtual machines (Fly Machines) close to users in regions around the world.
Common Fly.io errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
WARNING The app is not listening on the expected address and will not be reachable by fly-proxy. | Your app listens on localhost or the wrong port instead of 0.0.0.0 and internal_port. | Your side | Listen on 0.0.0.0 at the internal_port set in fly.toml. Source |
503 Service Unavailable | No healthy Machines are available: they are stopped, failing health checks, or there is a regional issue. | Your side | Run fly status and fly checks list; if Machines look healthy, check the status page for your region. Source |
502 Bad Gateway | The Fly proxy reached your Machine but the app did not respond correctly, for example because it crashed or is mid-deploy. | Your side | Check fly logs for crashes and the listening port. Source |
Is it just you?
- Run fly status to see whether your Machines are started and passing health checks.
- Check fly logs for out-of-memory kills, which look like crashes to the proxy.
- If only one region fails, check status.flyio.net for that region.
- Try fly deploy again if Machines are stuck mid-deploy.
Alternatives to Fly.io
Questions
Fly's docs say a 503 means no healthy Machines are available: all are stopped, failing health checks, or affected by a regional issue. Check fly status and fly checks list.
Most Fly errors come from the app's listening address, health checks or memory. If many apps in a region fail at once, check Fly's status page.
Sources: docs.fly.io, status.flyio.net
Get alerted when Fly.io breaks your app.
If your product or your team depends on Fly.io, its outage is your outage, and your users will blame you, not Fly.io. Point a Site Qwality monitor at the Fly.io endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.