Fly.io Status
Real-time updates of Fly.io issues and outages
Fly.io status is Operational
Fly.io Machines API
EZE - Ezeiza, Argentina
Fly.io Remote Builds
Active Incidents
No active incidents
Recently Resolved Incidents
Fly API operations are currently slow or failing, we're investigating the cause.
This will affect most operations that rely in the machines API, including starting Fly builders, deploying, creating/destroying machines, querying machine or volume data via the API.
Existing, running apps and machines are not affected and continue to serve normally.
Machines deployed in EZE have lost IPv6 connectivity due to an upstream issue. We are actively working with our upstream provider to get this resolved.
Fly.io Outage Survival Guide
Fly.io Components
Fly.io Customer Applications
Fly.io Dashboard
Fly.io AMS - Amsterdam, Netherlands
Fly.io Machines API
Fly API operations are currently slow or failing, we're investigating the cause.
This will affect most operations that rely in the machines API, including starting Fly builders, deploying, creating/destroying machines, querying machine or volume data via the API.
Existing, running apps and machines are not affected and continue to serve normally.
API
Fly.io Regional Availability
Fly.io ARN - Stockholm, Sweden
AMS - Amsterdam, Netherlands
ARN - Stockholm, Sweden
ATL - Atlanta, Georgia (US)
API
BOG - Bogotá, Colombia
Fly.io ATL - Atlanta, Georgia (US)
API
BOM - Mumbai, India
CDG - Paris, France
Fly.io BOG - Bogotá, Colombia
DEN - Denver, Colorado (US)
API
DFW - Dallas, Texas (US)
EZE - Ezeiza, Argentina
Machines deployed in EZE have lost IPv6 connectivity due to an upstream issue. We are actively working with our upstream provider to get this resolved.
Fly.io BOM - Mumbai, India
FRA - Frankfurt, Germany
GRU - Sao Paulo, Brazil
API
HKG - Hong Kong
IAD - Ashburn, Virginia (US)
Fly.io BOS - Boston, Massachusetts (US)
JNB - Johannesburg, South Africa
API
LAX - Los Angeles, California (US)
Fly.io CDG - Paris, France
LHR - London, United Kingdom
API
MAD - Madrid, Spain
Fly.io DEN - Denver, Colorado (US)
MEL - Melbourne, Australia
MIA - Miami, Florida (US)
API
NRT - Tokyo, Japan
ORD - Chicago, Illinois (US)
Fly.io DFW - Dallas, Texas (US)
API
OTP - Bucharest, Romania
QRO - Querétaro, Mexico
Fly.io EWR - Secaucus, NJ (US)
SCL - Santiago, Chile
API
SEA - Seattle, Washington (US)
SIN - Singapore
SJC - San Jose, California (US)
Fly.io FRA - Frankfurt, Germany
SYD - Sydney, Australia
API
YYZ - Toronto, Canada
Fly.io GRU - Sao Paulo, Brazil
Fly.io Persistent Storage (Volumes)
API
MAA - Chennai (Madras), India
Fly.io Deployments
Fly.io Remote Builds
Fly API operations are currently slow or failing, we're investigating the cause.
This will affect most operations that rely in the machines API, including starting Fly builders, deploying, creating/destroying machines, querying machine or volume data via the API.
Existing, running apps and machines are not affected and continue to serve normally.
Fly.io Logs
Fly.io HKG - Hong Kong
MRS - Marseille, France
Fly.io Metrics
API
Fly.io SSL/TLS Certificate Provisioning
Fly.io UDP Anycast
Fly.io IAD - Ashburn, Virginia (US)
API
Fly.io Fly Machine Image Registry 1
Fly.io Fly Machine Image Registry 2
Fly.io Extensions
Fly.io JNB - Johannesburg, South Africa
Upstash for Redis
API
Fly.io DNS
Fly Machine .internal DNS
Fly.io LAX - Los Angeles, California (US)
Fly Machine External DNS
API
*.fly.dev Nameservers
Fly.io LHR - London, United Kingdom
*.flyio.net Nameservers
API
Fly.io Billing
Usage Metrics API
Fly.io MAD - Madrid, Spain
Stripe API Connection
API
Fly.io Corrosion
Fly.io MIA - Miami, Florida (US)
API
Fly.io NRT - Tokyo, Japan
API
Fly.io ORD - Chicago, Illinois (US)
API
Fly.io OTP - Bucharest, Romania
API
Fly.io SCL - Santiago, Chile
API
Fly.io SEA - Seattle, Washington (US)
API
Fly.io SIN - Singapore
API
Fly.io SJC - San Jose, California (US)
API
Fly.io SYD - Sydney, Australia
API
Fly.io YYZ - Toronto, Canada
API
Fly.io Platform and Tools
Upstash Redis
Fly.io Alternatives
Paperspace US (CA1)
We are currently investigating an issue that is preventing CORE machines in CA1 from processing events. Our engineers are working on a fix. We apologize for any inconvenience caused.