All Systems Operational

About This Site


Personalized Status


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 status page in your Fly Organization's dashboard.

View Status page


DNS Operational
Fly Machine .internal DNS ? Operational
Fly Machine External DNS Operational
*.fly.dev Nameservers Operational
*.flyio.net Nameservers Operational
Logs Operational
Metrics ? Operational
Platform and Tools Operational
90 days ago
99.89 % uptime
Today
API Operational
90 days ago
99.63 % uptime
Today
Deployments Operational
90 days ago
99.75 % uptime
Today
Dashboard Operational
90 days ago
99.77 % uptime
Today
Remote Builds Operational
90 days ago
99.96 % uptime
Today
SSL/TLS Certificate Provisioning Operational
90 days ago
100.0 % uptime
Today
Upstash Redis ? Operational
90 days ago
100.0 % uptime
Today
Persistent Storage (Volumes) ? Operational
90 days ago
100.0 % uptime
Today
UDP Anycast ? Operational
90 days ago
100.0 % uptime
Today
Corrosion ? Operational
90 days ago
100.0 % uptime
Today
Fly Machine Image Registry 1 Operational
Fly Machine Image Registry 2 Operational
Regional Availability Operational
90 days ago
99.99 % uptime
Today
AMS - Amsterdam, Netherlands Operational
90 days ago
100.0 % uptime
Today
ARN - Stockholm, Sweden Operational
90 days ago
100.0 % uptime
Today
ATL - Atlanta, Georgia (US) Operational
90 days ago
100.0 % uptime
Today
BOM - Mumbai, India Operational
90 days ago
100.0 % uptime
Today
CDG - Paris, France Operational
90 days ago
100.0 % uptime
Today
DFW - Dallas, Texas (US) Operational
90 days ago
100.0 % uptime
Today
EWR - Secaucus, New Jersey (US) Operational
90 days ago
100.0 % uptime
Today
FRA - Frankfurt, Germany Operational
90 days ago
100.0 % uptime
Today
GRU - São Paulo, Brazil Operational
90 days ago
100.0 % uptime
Today
HKG - Hong Kong Operational
90 days ago
99.97 % uptime
Today
IAD - Ashburn, Virginia (US) Operational
90 days ago
99.95 % uptime
Today
JNB - Johannesburg, South Africa Operational
90 days ago
100.0 % uptime
Today
LAX - Los Angeles, California (US) Operational
90 days ago
99.98 % uptime
Today
LHR - London, United Kingdom Operational
90 days ago
100.0 % uptime
Today
MAA - Chennai (Madras), India Operational
90 days ago
100.0 % uptime
Today
MAD - Madrid, Spain Operational
90 days ago
100.0 % uptime
Today
MIA - Miami, Florida (US) Operational
90 days ago
100.0 % uptime
Today
MRS - Marseille, France Operational
90 days ago
100.0 % uptime
Today
NRT - Tokyo, Japan Operational
90 days ago
99.99 % uptime
Today
ORD - Chicago, Illinois (US) Operational
90 days ago
100.0 % uptime
Today
SCL - Santiago, Chile Operational
90 days ago
100.0 % uptime
Today
SEA - Seattle, Washington (US) Operational
90 days ago
100.0 % uptime
Today
SIN - Singapore Operational
90 days ago
100.0 % uptime
Today
SJC - Sunnyvale, California (US) Operational
90 days ago
99.98 % uptime
Today
SYD - Sydney, Australia Operational
90 days ago
100.0 % uptime
Today
YYZ - Toronto, Canada Operational
90 days ago
100.0 % uptime
Today
DEN - Denver, Colorado (US) Operational
Billing (Stripe API Connection) Operational
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.
API Success Rate
Fetching
Past Incidents
May 22, 2024

No incidents reported today.

May 21, 2024

No incidents reported.

May 20, 2024

No incidents reported.

May 19, 2024

No incidents reported.

May 18, 2024

No incidents reported.

May 17, 2024
Resolved - This incident has been resolved.
May 17, 14:19 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 17, 13:31 UTC
Identified - The issue has been identified and a fix is being implemented.
May 17, 12:39 UTC
May 16, 2024

No incidents reported.

May 15, 2024

No incidents reported.

May 14, 2024
Resolved - One remaining application host had a broken cable which has now been repaired, and the region is now fully back online.
Total unavailability was 45 minutes (2024-05-13 21:00 - 21:45 UTC) for several servers in the region, and ~19 hours (2024-05-13 21:00 - 2024-05-14 15:50 UTC) for one application host.

May 14, 15:57 UTC
Identified - Our datacenter provider has confirmed a network switch failure affecting a portion of hosts in this region, and is working on a resolution.
May 13, 22:02 UTC
Update - We are seeing a partial recovery of services in this region, some application hosts in this region are still unavailable.
May 13, 21:32 UTC
Investigating - We're investigating a network issue affecting the BOG region.
May 13, 21:16 UTC
Resolved - The metrics system has finished processing its backlog and the service is fully operational again.
May 14, 03:03 UTC
Identified - A fix has been applied and metrics are once again being processed. They will continue be delayed until the system finishes processing the accumulated backlog.
May 14, 01:41 UTC
Investigating - We are currently investigating an issue affecting application metrics.
May 14, 00:53 UTC
May 13, 2024
Resolved - This incident has been resolved.
May 13, 13:01 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 13, 12:24 UTC
Investigating - Network operations in SJC may encounter delays leading to timeouts, both for Machines operating in the region and for API requests in the region. We are working with our partners to identify the cause.
May 13, 12:04 UTC
May 12, 2024

No incidents reported.

May 11, 2024

No incidents reported.

May 10, 2024
Completed - The scheduled maintenance has been completed.
May 10, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 10, 13:00 UTC
Scheduled - Our datacenter provider will be performing scheduled maintenance during this time period. No downtime is expected.
May 9, 17:34 UTC
Resolved - On 2024-05-08 13:20 UTC, we deployed a load-balancer update to `ams` that caused registry pushes with large image layers to get stuck, impacting new app builds from this region for ~48 hours. On 2024-05-10 12:30 UTC, this update was deployed globally, impacting new app builds for ~1 hour. We rolled back the update on 2024-05-10 13:30 UTC and the issue is now resolved.
May 10, 13:30 UTC
May 9, 2024
Resolved - This incident has been resolved.
May 9, 00:03 UTC
Update - We are moving App Builders from AMS to IAD to mitigate the impact of the possible network problems.
May 8, 22:59 UTC
Update - We are investigating possible upstream network problems with s3
May 8, 22:21 UTC
Investigating - Our suspected fix was not successful - continuing to investigate other avenues
May 8, 21:36 UTC
Monitoring - We're monitoring a suspected fix to the registry
May 8, 19:58 UTC
Update - Investigating issues relating to registry/tokens with DFW, and issues in CDG
May 8, 19:15 UTC
Investigating - Symptoms look like docker layer uploads hang while pushing the layers. We're investigating this issue!
May 8, 18:33 UTC
May 8, 2024
Resolved - This issue has been resolved
May 8, 16:11 UTC
Update - We are continuing to monitor for any further issues.
May 8, 15:46 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 8, 13:57 UTC
Identified - The issue has been identified and a fix is being implemented.
May 8, 11:29 UTC
Investigating - We are currently investigating this issue.
May 8, 11:13 UTC
Resolved - This incident has been resolved.
May 8, 02:53 UTC
Monitoring - All services are operational and we are monitoring our telemetry.
May 8, 02:44 UTC
Update - We are repairing the last handful of physical servers.
May 8, 02:11 UTC
Update - A small percentage of physical servers have experienced abnormally high memory utilization, resulting in intermittent failures for the machines they are hosting. We are working to repair the problem and restore service to affected machines.
May 8, 01:32 UTC
Identified - The issue has been identified and a fix is being implemented.
May 8, 01:12 UTC
Investigating - We are currently investigating this issue.
May 8, 00:59 UTC