Identified - New machine/volume creates in LHR regions are currently unavailable as there is no host capacity available.

Any workloads currently running will continue to run; it is also still possible to update existing machines/volumes.

Increasing `fly scale count` in LHR region is not possible. Blue-green deploys are also not possible at the moment, as well as deploys with `release_command`.

We expect more capacity to become available in the coming weeks. For the time being, please choose a nearby region for new workloads, such as AMS (Amsterdam, Netherlands) or ARN (Stockholm, Sweden).

Mar 14, 2025 - 13:55 UTC

About This Site

This page is for updates about global incidents. It does not include updates about routine hardware failures or isolated infrastructure events that have limited impact. For a personalized view of all events that might affect your apps, please check the personalized status page in your Fly Organization's dashboard. For all internal incidents and other activities, please check Infra Log.

Customer Applications Operational
Dashboard Operational
Machines API Operational
Regional Availability Degraded Performance
AMS - Amsterdam, Netherlands Operational
ARN - Stockholm, Sweden Operational
ATL - Atlanta, Georgia (US) Operational
BOG - Bogotá, Colombia Operational
BOM - Mumbai, India Operational
CDG - Paris, France Operational
DEN - Denver, Colorado (US) Operational
DFW - Dallas, Texas (US) Operational
EWR - Secaucus, NJ (US) Operational
EZE - Ezeiza, Argentina Operational
FRA - Frankfurt, Germany Operational
GDL - Guadalajara, Mexico Operational
GIG - Rio de Janeiro, Brazil Operational
GRU - Sao Paulo, Brazil Operational
HKG - Hong Kong Operational
IAD - Ashburn, Virginia (US) Operational
JNB - Johannesburg, South Africa Operational
LAX - Los Angeles, California (US) Operational
LHR - London, United Kingdom Degraded Performance
MAD - Madrid, Spain Operational
MEL - Melbourne, Australia Operational
MIA - Miami, Florida (US) Operational
NRT - Tokyo, Japan Operational
ORD - Chicago, Illinois (US) Operational
OTP - Bucharest, Romania Operational
PHX - Phoenix, Arizona (US) Operational
QRO - Querétaro, Mexico Operational
SCL - Santiago, Chile Operational
SEA - Seattle, Washington (US) Operational
SIN - Singapore Operational
SJC - San Jose, California (US) Operational
SYD - Sydney, Australia Operational
WAW - Warsaw, Poland Operational
YUL - Montréal, Canada Operational
YYZ - Toronto, Canada Operational
Persistent Storage (Volumes) ? Operational
Deployments ? Operational
Remote Builds Operational
Logs Operational
Metrics ? Operational
SSL/TLS Certificate Provisioning Operational
UDP Anycast ? Operational
Fly Machine Image Registry 1 Operational
Fly Machine Image Registry 2 Operational
Extensions Operational
Upstash for Redis Operational
DNS Operational
Fly Machine .internal DNS ? Operational
Fly Machine External DNS Operational
*.fly.dev Nameservers Operational
*.flyio.net Nameservers Operational
Billing Operational
Usage Metrics API Operational
Stripe API Connection Operational
Corrosion ? Operational
Postgres Flex Clusters Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Mar 20, 2025

No incidents reported today.

Mar 19, 2025

No incidents reported.

Mar 18, 2025
Resolved - We have identified that transoceanic subsea cable faults resulted in degraded connectivity to some registry instances in AMS, FRA, WAW regions. Our monitoring indicates error rates have improved after cordoning the affected instances at 16:40 UTC.
Mar 18, 19:21 UTC
Monitoring - We are continuing to monitor results after cordoning affected registry instances.
Mar 18, 17:23 UTC
Investigating - We are investigating timeouts connecting to instances of registry.fly.io in AMS, FRA, WAW regions. Customers may experience slower image pushes and pulls within Fly Machines in the affected regions.
Mar 18, 17:06 UTC
Monitoring - We have cordoned the affected registry instances in AMS, FRA, WAW and are seeing timeout errors decrease.
Mar 18, 16:40 UTC
Update - We are continuing to investigate the cause of increased connection timeouts to instances of our primary registry in AMS, FRA, WAW. Affected customers may be able to work around by pushing images to an alternate registry, registry2.fly.io:

FLY_REGISTRY_HOST=registry2.fly.io fly deploy

Mar 18, 16:39 UTC
Investigating - We are investigating timeouts connecting to registry.fly.io. Customers may experience slower image pushes and pulls within Fly Machines.
Mar 18, 15:52 UTC
Mar 17, 2025
Resolved - We have provisioned additional capacity in the affected regions.
Mar 17, 22:12 UTC
Monitoring - New machine/volume creates in IAD regions may fail as there is no host capacity available.

Any workloads currently running will continue to run; it is also still possible to update existing machines/volumes.

Increasing `fly scale count` in these regions may not work. Blue-green deploys may also be unavailable at the moment, as well as deploys with `release_command`.

We are provisioning additional capacity in this region.

Mar 17, 20:50 UTC
Mar 16, 2025

No incidents reported.

Mar 15, 2025

No incidents reported.

Mar 14, 2025

Unresolved incident: Capacity issues in LHR region.

Mar 13, 2025

No incidents reported.

Mar 12, 2025

No incidents reported.

Mar 11, 2025

No incidents reported.

Mar 10, 2025

No incidents reported.

Mar 9, 2025

No incidents reported.

Mar 8, 2025

No incidents reported.

Mar 7, 2025

No incidents reported.

Mar 6, 2025
Resolved - This incident has been resolved.
Mar 6, 17:10 UTC
Monitoring - A fix has been implemented and we are monitoring
Mar 6, 16:10 UTC
Investigating - We are investigating an issue where postgres flex clusters are unable to elect a new leader.
Mar 6, 16:08 UTC