
Fly.io Status
Real-time updates of Fly.io issues and outages
Fly.io status is Partially Degraded Service
JNB - Johannesburg, South Africa
SIN - Singapore
Fly.io Deployments
Fly.io Remote Builds
Fly.io Logs
Fly.io Managed Postgres
Management Plane - LAX
Active Incidents
No active incidents
Recently Resolved Incidents
A bad deploy of an internal service in JNB region may cause Machines API requests for JNB region machines to fail. At this time, it may not be possible to create or update machines in JNB region, but apps continue to run. The deploy is being reverted.
App logs after 12:00 UTC may be delayed to show up on fly-metrics.net. We are monitoring log insert rate and will update once log insertion is current.
Log streaming via flyctl logs or NATS is current.
We are investigating network issues in SIN region. Apps running in this region may experience elevated latency or packet loss.
We are investigating high memory utilization on some hosts in ORD. Customers may notice timeouts or errors in reserving resources when updating or creating new Machines in the region.
We are rebalancing workloads in ORD to relieve memory pressure on impacted hosts.
We are currently investigating an outage with app logs in Grafana. Logs are still available through flyctl and through the dashboard.
Fly.io Outage Survival Guide
Fly.io Components
Fly.io Customer Applications
Fly.io Dashboard
Fly.io AMS - Amsterdam, Netherlands
Fly.io Machines API
API
Fly.io Regional Availability
AMS - Amsterdam, Netherlands
Fly.io ARN - Stockholm, Sweden
ARN - Stockholm, Sweden
API
ATL - Atlanta, Georgia (US)
BOM - Mumbai, India
CDG - Paris, France
BOG - Bogotá, Colombia
Fly.io ATL - Atlanta, Georgia (US)
API
DFW - Dallas, Texas (US)
DEN - Denver, Colorado (US)
EWR - Secaucus, NJ (US)
FRA - Frankfurt, Germany
Fly.io BOG - Bogotá, Colombia
GRU - Sao Paulo, Brazil
EZE - Ezeiza, Argentina
API
IAD - Ashburn, Virginia (US)
GDL - Guadalajara, Mexico
JNB - Johannesburg, South Africa
A bad deploy of an internal service in JNB region may cause Machines API requests for JNB region machines to fail. At this time, it may not be possible to create or update machines in JNB region, but apps continue to run. The deploy is being reverted.
Fly.io BOM - Mumbai, India
LAX - Los Angeles, California (US)
API
GIG - Rio de Janeiro, Brazil
LHR - London, United Kingdom
HKG - Hong Kong
NRT - Tokyo, Japan
Fly.io BOS - Boston, Massachusetts (US)
ORD - Chicago, Illinois (US)
API
SIN - Singapore
We are investigating network issues in SIN region. Apps running in this region may experience elevated latency or packet loss.
Fly.io CDG - Paris, France
SJC - San Jose, California (US)
API
SYD - Sydney, Australia
Fly.io DEN - Denver, Colorado (US)
YYZ - Toronto, Canada
MAD - Madrid, Spain
API
Fly.io Persistent Storage (Volumes)
MEL - Melbourne, Australia
Fly.io Deployments
We are investigating high memory utilization on some hosts in ORD. Customers may notice timeouts or errors in reserving resources when updating or creating new Machines in the region.
We are rebalancing workloads in ORD to relieve memory pressure on impacted hosts.
MIA - Miami, Florida (US)
Fly.io Remote Builds
We are investigating high memory utilization on some hosts in ORD. Customers may notice timeouts or errors in reserving resources when updating or creating new Machines in the region.
We are rebalancing workloads in ORD to relieve memory pressure on impacted hosts.
Fly.io DFW - Dallas, Texas (US)
Fly.io Logs
We are currently investigating an outage with app logs in Grafana. Logs are still available through flyctl and through the dashboard.
App logs after 12:00 UTC may be delayed to show up on fly-metrics.net. We are monitoring log insert rate and will update once log insertion is current.
Log streaming via flyctl logs or NATS is current.