Company Logo

Is there an Fly.io outage?

Fly.io status: Systems Active

Last checked: 2 minutes ago

Get notified about any outages, downtime or incidents for Fly.io and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Fly.io outages and incidents

Outage and incident data over the last 30 days for Fly.io.

There have been 5 outages or incidents for Fly.io in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Fly.io

Outlogger tracks the status of these components for Xero:

Corrosion Active
Customer Applications Active
Dashboard Active
Deployments Active
Fly Machine Image Registry 1 Active
Fly Machine Image Registry 2 Active
Logs Active
Machines API Active
Metrics Active
Persistent Storage (Volumes) Active
Remote Builds Active
SSL/TLS Certificate Provisioning Active
UDP Anycast Active
Stripe API Connection Active
Usage Metrics API Active
*.fly.dev Nameservers Active
*.flyio.net Nameservers Active
Fly Machine External DNS Active
Fly Machine .internal DNS Active
Upstash for Redis Active
AMS - Amsterdam, Netherlands Active
ARN - Stockholm, Sweden Active
ATL - Atlanta, Georgia (US) Active
BOG - Bogotá, Colombia Active
BOM - Mumbai, India Active
CDG - Paris, France Active
DEN - Denver, Colorado (US) Active
DFW - Dallas, Texas (US) Active
EZE - Ezeiza, Argentina Active
FRA - Frankfurt, Germany Active
GDL - Guadalajara, Mexico Active
GIG - Rio de Janeiro, Brazil Active
GRU - Sao Paulo, Brazil Active
HKG - Hong Kong Active
IAD - Ashburn, Virginia (US) Active
JNB - Johannesburg, South Africa Active
LAX - Los Angeles, California (US) Active
LHR - London, United Kingdom Active
MAD - Madrid, Spain Active
MEL - Melbourne, Australia Active
MIA - Miami, Florida (US) Active
NRT - Tokyo, Japan Active
ORD - Chicago, Illinois (US) Active
OTP - Bucharest, Romania Active
QRO - Querétaro, Mexico Active
SCL - Santiago, Chile Active
SEA - Seattle, Washington (US) Active
SIN - Singapore Active
SJC - San Jose, California (US) Active
SYD - Sydney, Australia Active
YYZ - Toronto, Canada Active
Component Status
Corrosion Active
Customer Applications Active
Dashboard Active
Deployments Active
Fly Machine Image Registry 1 Active
Fly Machine Image Registry 2 Active
Logs Active
Machines API Active
Metrics Active
Persistent Storage (Volumes) Active
Remote Builds Active
SSL/TLS Certificate Provisioning Active
UDP Anycast Active
Active
Stripe API Connection Active
Usage Metrics API Active
Active
*.fly.dev Nameservers Active
*.flyio.net Nameservers Active
Fly Machine External DNS Active
Fly Machine .internal DNS Active
Active
Upstash for Redis Active
Active
AMS - Amsterdam, Netherlands Active
ARN - Stockholm, Sweden Active
ATL - Atlanta, Georgia (US) Active
BOG - Bogotá, Colombia Active
BOM - Mumbai, India Active
CDG - Paris, France Active
DEN - Denver, Colorado (US) Active
DFW - Dallas, Texas (US) Active
EZE - Ezeiza, Argentina Active
FRA - Frankfurt, Germany Active
GDL - Guadalajara, Mexico Active
GIG - Rio de Janeiro, Brazil Active
GRU - Sao Paulo, Brazil Active
HKG - Hong Kong Active
IAD - Ashburn, Virginia (US) Active
JNB - Johannesburg, South Africa Active
LAX - Los Angeles, California (US) Active
LHR - London, United Kingdom Active
MAD - Madrid, Spain Active
MEL - Melbourne, Australia Active
MIA - Miami, Florida (US) Active
NRT - Tokyo, Japan Active
ORD - Chicago, Illinois (US) Active
OTP - Bucharest, Romania Active
QRO - Querétaro, Mexico Active
SCL - Santiago, Chile Active
SEA - Seattle, Washington (US) Active
SIN - Singapore Active
SJC - San Jose, California (US) Active
SYD - Sydney, Australia Active
YYZ - Toronto, Canada Active

Latest Fly.io outages and incidents.

View the latest incidents for Fly.io and check for official updates:

Updates:

  • Time: May 1, 2024, 12:29 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: May 1, 2024, 12:21 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: May 1, 2024, 12:05 a.m.
    Status: Monitoring
    Update: Most workers are back online and machines on those workers are operating. We are monitoring the final few workers to ensure they start and machines become operational.
  • Time: April 30, 2024, 11:56 p.m.
    Status: Identified
    Update: Data center power has come back online. We are working to get all workers in sjc operational.
  • Time: April 30, 2024, 11:36 p.m.
    Status: Investigating
    Update: Some workers in sjc region are currently offline. We are working with our data center vendor to investigate the issue. Machines that are on affected hosts in sjc are not accessible and shutdown. We recommend deploying in other regions if you are able.
  • Time: April 30, 2024, 11:09 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: April 30, 2024, 11:04 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: May 1, 2024, 12:29 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: May 1, 2024, 12:21 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: May 1, 2024, 12:05 a.m.
    Status: Monitoring
    Update: Most workers are back online and machines on those workers are operating. We are monitoring the final few workers to ensure they start and machines become operational.
  • Time: April 30, 2024, 11:56 p.m.
    Status: Identified
    Update: Data center power has come back online. We are working to get all workers in sjc operational.
  • Time: April 30, 2024, 11:36 p.m.
    Status: Investigating
    Update: Some workers in sjc region are currently offline. We are working with our data center vendor to investigate the issue. Machines that are on affected hosts in sjc are not accessible and shutdown. We recommend deploying in other regions if you are able.
  • Time: April 30, 2024, 11:09 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: April 30, 2024, 11:04 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: April 27, 2024, 3:22 a.m.
    Status: Resolved
    Update: All errors have been fixed.
  • Time: April 27, 2024, 2:27 a.m.
    Status: Monitoring
    Update: We've deployed another fix and are seeing signs of recovery
  • Time: April 27, 2024, 1:37 a.m.
    Status: Investigating
    Update: The iad region is still having issues, which are affecting the platform. We're investigating and will continue to update here. Machines are not able to start. The dashboard is not loading.
  • Time: April 27, 2024, 12:34 a.m.
    Status: Monitoring
    Update: We have deployed a fix to the vast majority of our hosts. We are still working on a small number of remaining hosts.
  • Time: April 27, 2024, 12:09 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: April 26, 2024, 11:59 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: April 26, 2024, 11:52 p.m.
    Status: Investigating
    Update: We are observing elevated errors and connectivity issues across Fly.io

Updates:

  • Time: April 27, 2024, 3:22 a.m.
    Status: Resolved
    Update: All errors have been fixed.
  • Time: April 27, 2024, 2:27 a.m.
    Status: Monitoring
    Update: We've deployed another fix and are seeing signs of recovery
  • Time: April 27, 2024, 1:37 a.m.
    Status: Investigating
    Update: The iad region is still having issues, which are affecting the platform. We're investigating and will continue to update here. Machines are not able to start. The dashboard is not loading.
  • Time: April 27, 2024, 12:34 a.m.
    Status: Monitoring
    Update: We have deployed a fix to the vast majority of our hosts. We are still working on a small number of remaining hosts.
  • Time: April 27, 2024, 12:09 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: April 26, 2024, 11:59 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: April 26, 2024, 11:52 p.m.
    Status: Investigating
    Update: We are observing elevated errors and connectivity issues across Fly.io

Updates:

  • Time: April 24, 2024, 9:28 p.m.
    Status: Resolved
    Update: We experienced a temporary outage in the wireguard mesh connecting all of our physical hosts which resulted in a number of internal systems losing connectivity with each other. The mesh has been repaired, but some regions required manual intervention, notably: AMS, BOM, CDG, HKG, IAD, MIA, SJC, SYD, YYZ. The following was impacted (a non-exhaustive list, this was a full network outage): fly token validation (including github actions and flyctl auth), 6pn networking calls, log delivery, routing requests to user machines.
  • Time: April 24, 2024, 9:28 p.m.
    Status: Resolved
    Update: We experienced a temporary outage in the wireguard mesh connecting all of our physical hosts which resulted in a number of internal systems losing connectivity with each other. The mesh has been repaired, but some regions required manual intervention, notably: AMS, BOM, CDG, HKG, IAD, MIA, SJC, SYD, YYZ. The following was impacted (a non-exhaustive list, this was a full network outage): fly token validation (including github actions and flyctl auth), 6pn networking calls, log delivery, routing requests to user machines.
  • Time: April 24, 2024, 7:56 p.m.
    Status: Monitoring
    Update: We have identified a small number of physical servers that are still impacted and are recovering them.
  • Time: April 24, 2024, 7:56 p.m.
    Status: Monitoring
    Update: We have identified a small number of physical servers that are still impacted and are recovering them.
  • Time: April 24, 2024, 7:25 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: April 24, 2024, 7:25 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: April 24, 2024, 6:58 p.m.
    Status: Investigating
    Update: We are observing elevated errors and connectivity issues across Fly.io
  • Time: April 24, 2024, 6:58 p.m.
    Status: Investigating
    Update: We are observing elevated errors and connectivity issues across Fly.io

Check the status of similar companies and alternatives to Fly.io

Avalara
Avalara

Systems Active

Crisis Text Line
Crisis Text Line

Systems Active

Jamf
Jamf

Systems Active

Mulesoft
Mulesoft

Systems Active

Meltwater
Meltwater

Systems Active

HashiCorp
HashiCorp

Systems Active

Datto
Datto

Issues Detected

Vox Media
Vox Media

Systems Active

Cradlepoint
Cradlepoint

Systems Active

Liferay
Liferay

Systems Active

Zapier
Zapier

Systems Active

Workato US
Workato US

Systems Active

Frequently Asked Questions - Fly.io

Is there a Fly.io outage?
The current status of Fly.io is: Systems Active
Where can I find the official status page of Fly.io?
The official status page for Fly.io is here
How can I get notified if Fly.io is down or experiencing an outage?
To get notified of any status changes to Fly.io, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Fly.io every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free