
Fly.io Status
Real-time updates of Fly.io issues and outages
Fly.io status is Operational
Fly.io Machines API
BOM - Mumbai, India
GRU - Sao Paulo, Brazil
SJC - San Jose, California (US)
*.fly.dev Nameservers
Active Incidents
No active incidents
Recently Resolved Incidents
We have identified an upstream issue that prevented static egress IPv6 addresses in BOM from reaching parts of the Internet and are currently working with upstreams for a fix. Machines without a static egress IPv6 address are not affected. For affected machines, consider forcing IPv4 for outbound connectivity or de-allocating the egress IP if not needed via fly m egress-ip release.
One of our upstream providers is performing an emergency network maintenance in BOM. Apps in BOM may experience temporary connectivity issues.
An upstream provider in SJC region is experiencing network issues. Apps on affected hosts may be unavailable.
An upstream provider in SJC region is experiencing network issues. Apps on affected hosts may be unavailable.
We are currently investigating an issue with the Machines API. You might see increased error rate
We are currently investigating network issues in GRU. Apps may see elevated response times and errors.
Fly.io Outage Survival Guide
Fly.io Components
Fly.io Customer Applications
Fly.io AMS - Amsterdam, Netherlands
Fly.io Dashboard
Fly.io Machines API
We are currently investigating an issue with the Machines API. You might see increased error rate
API
Fly.io Regional Availability
Fly.io ARN - Stockholm, Sweden
AMS - Amsterdam, Netherlands
ARN - Stockholm, Sweden
API
ATL - Atlanta, Georgia (US)
BOG - Bogotá, Colombia
Fly.io ATL - Atlanta, Georgia (US)
BOM - Mumbai, India
We have identified an upstream issue that prevented static egress IPv6 addresses in BOM from reaching parts of the Internet and are currently working with upstreams for a fix. Machines without a static egress IPv6 address are not affected. For affected machines, consider forcing IPv4 for outbound connectivity or de-allocating the egress IP if not needed via fly m egress-ip release.
One of our upstream providers is performing an emergency network maintenance in BOM. Apps in BOM may experience temporary connectivity issues.
API
CDG - Paris, France
Fly.io BOG - Bogotá, Colombia
DEN - Denver, Colorado (US)
DFW - Dallas, Texas (US)
API
EWR - Secaucus, NJ (US)
Fly.io BOM - Mumbai, India
EZE - Ezeiza, Argentina
API
FRA - Frankfurt, Germany
GDL - Guadalajara, Mexico
Fly.io BOS - Boston, Massachusetts (US)
GIG - Rio de Janeiro, Brazil
API
GRU - Sao Paulo, Brazil
We are currently investigating network issues in GRU. Apps may see elevated response times and errors.
Fly.io CDG - Paris, France
HKG - Hong Kong
API
IAD - Ashburn, Virginia (US)
JNB - Johannesburg, South Africa
LAX - Los Angeles, California (US)
Fly.io DEN - Denver, Colorado (US)
LHR - London, United Kingdom
API
MAD - Madrid, Spain
Fly.io DFW - Dallas, Texas (US)
MEL - Melbourne, Australia
API
MIA - Miami, Florida (US)
NRT - Tokyo, Japan
Fly.io EWR - Secaucus, NJ (US)
ORD - Chicago, Illinois (US)
OTP - Bucharest, Romania
API
PHX - Phoenix, Arizona (US)
QRO - Querétaro, Mexico
Fly.io FRA - Frankfurt, Germany
API
SCL - Santiago, Chile
SEA - Seattle, Washington (US)
SIN - Singapore
Fly.io GRU - Sao Paulo, Brazil
API
MAA - Chennai (Madras), India
SJC - San Jose, California (US)
An upstream provider in SJC region is experiencing network issues. Apps on affected hosts may be unavailable.
An upstream provider in SJC region is experiencing network issues. Apps on affected hosts may be unavailable.