
Fly.io Status
Real-time updates of Fly.io issues and outages
Fly.io status is Operational
Fly.io Machines API
DFW - Dallas, Texas (US)
SJC - San Jose, California (US)
Fly.io Logs
Fly.io Metrics
Management Plane - SJC
*.fly.dev Nameservers
You're checking on Fly.io - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
Using the Logs panel in Grafana at https://fly-metrics.net/ will show a 502 error from the backend and won't show any logs. You can use fly logs or the live log viewer directly on https://fly.io/dashboard to view streaming logs for the time being.
The Machines start failure rate is elevated in DFW.
We are currently investigating an issue with our metrics cluster.
We are investigating intermittent network issues in SJC region impacting outbound public IPv6 access from Machines. Connecting to IPv6 internet resources from apps hosted in SJC region may be slow or fail at this time.
IPv4 access, as well as 6PN private networking, are unaffected.
Between 13:55 and 14:03 UTC machines and MPG clusters hosted in the SJC region saw elevated connection errors. Users may have seen errors connecting to or from most machines in the region, as well as with deployments or updates to machines in the region.
Networking has returned to normal in the region, and we are continuing to monitor closely to ensure stable recovery.
We have identified an issue causing new fly ssh console connections to fail with 500 errors. A fix is in progress.
Fly.io Outage Survival Guide
Fly.io Components
Fly.io Customer Applications
Fly.io Dashboard
Fly.io AMS - Amsterdam, Netherlands
Fly.io Machines API
We have identified an issue causing new fly ssh console connections to fail with 500 errors. A fix is in progress.
Fly.io Regional Availability
API
Fly.io ARN - Stockholm, Sweden
AMS - Amsterdam, Netherlands
ARN - Stockholm, Sweden
BOM - Mumbai, India
ATL - Atlanta, Georgia (US)
API
BOG - Bogotá, Colombia
Fly.io ATL - Atlanta, Georgia (US)
CDG - Paris, France
DEN - Denver, Colorado (US)
DFW - Dallas, Texas (US)
The Machines start failure rate is elevated in DFW.
API
EWR - Secaucus, NJ (US)
Fly.io BOG - Bogotá, Colombia
FRA - Frankfurt, Germany
GRU - Sao Paulo, Brazil
API
EZE - Ezeiza, Argentina
IAD - Ashburn, Virginia (US)
GDL - Guadalajara, Mexico
JNB - Johannesburg, South Africa
Fly.io BOM - Mumbai, India
GIG - Rio de Janeiro, Brazil
LAX - Los Angeles, California (US)
API
LHR - London, United Kingdom
NRT - Tokyo, Japan
Fly.io BOS - Boston, Massachusetts (US)
HKG - Hong Kong
API
ORD - Chicago, Illinois (US)
Fly.io CDG - Paris, France
SIN - Singapore
API
SJC - San Jose, California (US)
Between 13:55 and 14:03 UTC machines and MPG clusters hosted in the SJC region saw elevated connection errors. Users may have seen errors connecting to or from most machines in the region, as well as with deployments or updates to machines in the region.
Networking has returned to normal in the region, and we are continuing to monitor closely to ensure stable recovery.
We are investigating intermittent network issues in SJC region impacting outbound public IPv6 access from Machines. Connecting to IPv6 internet resources from apps hosted in SJC region may be slow or fail at this time.
IPv4 access, as well as 6PN private networking, are unaffected.
SYD - Sydney, Australia
YYZ - Toronto, Canada
Fly.io DEN - Denver, Colorado (US)
MAD - Madrid, Spain
Fly.io Persistent Storage (Volumes)
MEL - Melbourne, Australia
API
MIA - Miami, Florida (US)
Fly.io Deployments
Fly.io DFW - Dallas, Texas (US)
Fly.io Remote Builds
Fly.io Logs
Using the Logs panel in Grafana at https://fly-metrics.net/ will show a 502 error from the backend and won't show any logs. You can use fly logs or the live log viewer directly on https://fly.io/dashboard to view streaming logs for the time being.
API
Fly.io Metrics
We are currently investigating an issue with our metrics cluster.
OTP - Bucharest, Romania
PHX - Phoenix, Arizona (US)
Fly.io SSL/TLS Certificate Provisioning
Fly.io EWR - Secaucus, NJ (US)
QRO - Querétaro, Mexico
API
Fly.io UDP Anycast
Fly.io Fly Machine Image Registry 1
SCL - Santiago, Chile
Fly.io Fly Machine Image Registry 2
Fly.io FRA - Frankfurt, Germany
SEA - Seattle, Washington (US)
API
Fly.io Extensions
Upstash for Redis
Fly.io DNS
Fly.io GRU - Sao Paulo, Brazil
Fly Machine .internal DNS
MAA - Chennai (Madras), India
WAW - Warsaw, Poland
API
YUL - Montréal, Canada
Fly Machine External DNS
*.flyio.net Nameservers
Fly.io HKG - Hong Kong
MRS - Marseille, France
API
flydns.net
Fly.io Billing
Fly.io IAD - Ashburn, Virginia (US)
Usage Metrics API
Stripe API Connection
API
Fly.io Corrosion
Fly.io Managed Postgres
Fly.io JNB - Johannesburg, South Africa
Management Plane - ORD
API
Management Plane - IAD
Management Plane - FRA
Fly.io LAX - Los Angeles, California (US)
API
Management Plane - GRU
Management Plane - LAX
Management Plane - SYD
Fly.io LHR - London, United Kingdom
Management Plane - AMS
API
Management Plane - LHR
Management Plane - NRT
Fly.io MAD - Madrid, Spain
Management Plane - SIN
API
Management Plane - SJC
Between 13:55 and 14:03 UTC machines and MPG clusters hosted in the SJC region saw elevated connection errors. Users may have seen errors connecting to or from most machines in the region, as well as with deployments or updates to machines in the region.
Networking has returned to normal in the region, and we are continuing to monitor closely to ensure stable recovery.