MPG Degraded clusters in AMS, IAD and SIN regions
Update - We are continuing to work on restoring all clusters to full health.
Feb 05, 2026 - 20:58 UTC
Update - With the underlying incident stabilizing (https://status.flyio.net/incidents/3npj6935byt4) we are seeing improvements amongst impacted clusters. We continue to work on restoring all clusters to full health.
Feb 05, 2026 - 20:16 UTC
Update - A number of clusters in IAD, AMS, and SIN regions continue to see degraded replicas and PGBouncers at this time. A smaller number of clusters in these regions are also seeing disruption to their primaries.
We continue to work on restoring full cluster health in all regions.
Feb 05, 2026 - 19:01 UTC
Identified - A small number of MPG clusters in the AMS and IAD region are currently in degraded states due to downstream impact from this Machines API issue: https://status.flyio.net/incidents/3npj6935byt4

Most of the impacted clusters may see a degraded replica or PG Bouncer in their statuspage. A very small number may be unable to connect to their MPG primary node, the team is working to restore connectivity as the top priority.
Users may also see delays registering new clusters in these regions at this time.
Feb 05, 2026 - 17:03 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.

Uptime over the past 90 days. View historical uptime.
Customer Applications Operational
Dashboard Operational
Machines API Operational
Regional Availability Operational
AMS - Amsterdam, Netherlands Operational
ARN - Stockholm, Sweden Operational
BOM - Mumbai, India Operational
CDG - Paris, France Operational
DFW - Dallas, Texas (US) Operational
EWR - Secaucus, NJ (US) Operational
FRA - Frankfurt, Germany Operational
GRU - Sao Paulo, Brazil Operational
IAD - Ashburn, Virginia (US) Operational
JNB - Johannesburg, South Africa Operational
LAX - Los Angeles, California (US) Operational
LHR - London, United Kingdom Operational
NRT - Tokyo, Japan Operational
ORD - Chicago, Illinois (US) Operational
SIN - Singapore Operational
SJC - San Jose, California (US) Operational
SYD - Sydney, Australia 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
*.flyio.net Nameservers Operational
flydns.net Operational
Billing Operational
Usage Metrics API Operational
Stripe API Connection Operational
Corrosion Operational
Managed Postgres Partial Outage
90 days ago
99.9 % uptime
Today
Management Plane - ORD Operational
90 days ago
99.92 % uptime
Today
Management Plane - IAD Partial Outage
90 days ago
99.81 % uptime
Today
Management Plane - FRA Operational
90 days ago
99.92 % uptime
Today
Management Plane - GRU Operational
90 days ago
99.92 % uptime
Today
Management Plane - LAX Operational
90 days ago
99.92 % uptime
Today
Management Plane - SYD Operational
90 days ago
99.92 % uptime
Today
Management Plane - AMS Partial Outage
90 days ago
99.9 % uptime
Today
Management Plane - LHR Operational
90 days ago
100.0 % uptime
Today
Management Plane - NRT Operational
90 days ago
100.0 % uptime
Today
Management Plane - SIN Partial Outage
90 days ago
99.95 % uptime
Today
Management Plane - SJC Operational
90 days ago
100.0 % uptime
Today
Management Plane - YYZ Operational
90 days ago
100.0 % uptime
Today
Phoenix.new Operational
Support Portal 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.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Network maintenance in NRT Feb 7, 2026 18:00 - Feb 8, 2026 00:00 UTC

An upstream provider is performing network maintenance in NRT on 2026-02-07, from 18:00 UTC (2026-02-08 03:00am local time) to 2026-02-08 00:00 UTC (09:00am local time). Apps may experience multiple short periods of loss of connectivity within the scheduled maintenance window.
Posted on Jan 22, 2026 - 17:00 UTC
Feb 5, 2026
Delayed Machine Registration + Token Errors
Resolved - This incident has been resolved.
Feb 5, 20:53 UTC
Monitoring - A fix has been deployed across all impacted hosts. We are seeing a sharp reduction in Token errors since 20:00 UTC and other metrics are recovering as well. We are continuing to monitor closely
Feb 5, 20:11 UTC
Update - We saw some improvement from the previous fix, however errors remained elevated on some hosts.
We have identified the root cause of the remaining errors as a communication issue between the hosts and our Token database. We are preparing a fix that should resolve these.
Feb 5, 19:03 UTC
Identified - We have rolled out an initial fix for the token issues and are monitoring for improvements.
Feb 5, 18:19 UTC
Investigating - While Machine registration error rates have improved, we are now seeing elevated error rates verifying user tokens during some actions.

Users may see errors like "failed to launch VM: permission_denied: bolt token: failed to verify service token: no verified tokens" when deploying or creating machines.

We are investigating
Feb 5, 17:42 UTC
Update - A fix has been rolled out and most hosts are registering machines as normal. A few hosts remain with elevated error rates, we are continuing to fix these.
Users who experience an error creating or deploying a new machine should re-try the operation.
Feb 5, 16:59 UTC
Identified - We have identified elevated error rates registering new machines with our global state tracking service on some hosts. We have identified the issue and are deploying a fix.

Users may have seen elevated machine create, start, or deployment failures over the past ~20 minutes.
Feb 5, 16:43 UTC
Network maintenance in YYZ
Resolved - Network maintenance has concluded.
Feb 5, 09:22 UTC
Monitoring - Managed Postgres clusters in YYZ should be operating normally.
Feb 5, 09:01 UTC
Identified - An upstream network provider is performing an emergency network maintenance in the YYZ region. Machines in YYZ may see some packet loss.

Managed Postgres clusters in YYZ are experiencing management plane issues. Clusters may see delayed fail-overs and changes in cluster size may not be possible during the maintenance period.
Feb 5, 05:46 UTC
Feb 4, 2026

No incidents reported.

Feb 3, 2026
IPv6 Issues in YYZ
Resolved - This incident has been resolved.
Feb 3, 15:53 UTC
Monitoring - A fix has been implemented and we're seeing IPv6 networking return to normal in YYZ. We'll continue to monitor to ensure full recovery.
Feb 3, 15:44 UTC
Investigating - We are currently investigating degraded IPv6 networking in the YYZ (Toronto) region.

Users with machines in this region may see issues connecting to their machines over IPv6. Users with static egress IPs may see issues connecting outbound over IPv6 from this region at this time. IPv4 is not impacted and continues to work normally.
Feb 3, 15:33 UTC
Elevated latency and packetloss in North American regions
Resolved - This incident has been resolved.
Feb 3, 03:43 UTC
Monitoring - Network performance issues between North American regions have resolved and we're continuing to monitor.
Feb 3, 03:26 UTC
Investigating - We are currently investigating intermittent spikes of increased latency and packet loss between North American regions over the past hour. Users may see degraded network performance on traffic in and out of the IAD and SJC regions at this time.

We are working with our upstream networking providers to investigate and mitigate these issues.
Feb 3, 02:56 UTC
Feb 2, 2026
Network maintenance in IAD
Completed - The scheduled maintenance has been completed.
Feb 2, 20:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 2, 19:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Feb 2, 18:21 UTC
Scheduled - An upstream provider is performing network maintenance in IAD on 2026-02-02 between 19:00 and 20:00 UTC (2:00PM to 3:00PM local time). Apps on a subset of hosts in the region may experience a momentary connectivity interruption sometime within this window.
Jan 30, 18:30 UTC
Feb 1, 2026
Congestion in CDG and FRA
Resolved - This incident has been resolved.
Feb 1, 21:37 UTC
Investigating - We are experiencing elevated weekend congestion in CDG (France) and FRA (Germany).
Feb 1, 20:15 UTC
Sprites are returning not found or unauthorized when they shouldn't be.
Resolved - This incident has been resolved.
Feb 1, 05:48 UTC
Monitoring - We've been able to restore missing sprites and tokens. We're monitoring for any additional issues.
Feb 1, 05:32 UTC
Update - We're working on a fix to restore missing sprites and tokens.
Feb 1, 04:52 UTC
Identified - We identified the source of the problem as an upstream DNS issue Tigris experienced, now resolved. We're currently assessing the impact on Sprites.
Feb 1, 03:02 UTC
Update - We are continuing to investigate this issue.
Feb 1, 02:51 UTC
Investigating - We're currently investigating this issue.
Feb 1, 02:16 UTC
Jan 31, 2026
Grafana Log Search Display Issue
Resolved - This has been resolved. If you are still experiencing any issues, you may need to log out and then back in.
Jan 31, 18:29 UTC
Update - No logs are displayed in Grafana Log Search when using the default `*` query.

You can try the following workarounds:
1. Replace the default `*`query with `NOT ""`
2. Viewing logs from the “fly app” tab or the “explore” tab,

Thank you for your kind understanding as we work through resolving this!
Jan 31, 17:49 UTC
Investigating - No logs are displayed in Grafana Log Search when using the default `*` query.

As a temporary workaround, please replace `*` with `NOT ""` query. Thank you for your kind understanding as we work through resolving this!
Jan 31, 17:35 UTC
Jan 30, 2026

No incidents reported.

Jan 29, 2026
Delayed metric reporting in NRT and SIN regions
Resolved - This incident has been resolved. All hosts in SIN and NRT are reporting up to date metrics.
Jan 29, 20:04 UTC
Update - Currently one host in SIN is still finishing working through it's metrics backlog and is reporting delayed metrics. Other hosts in NRT and SIN are reporting metrics correctly.

If needed, users with impacted machines on the remaining host can use `fly machine clone` to create new machines in the region, which should land on a different host.
Jan 29, 15:15 UTC
Update - Most hosts in NRT and SIN have completed backfilling their metrics and are up to date in fly-metrics.net.

Four hosts are still working through the backlog; machines on those hosts are still reporting delayed metrics at this time.
Jan 28, 15:27 UTC
Update - We are continuing to process the metrics backlog in NRT and SIN. Progress is being made, but due to the volume of metrics this may still take some time to fully complete.

At this time users with machines on impacted hosts will see metrics beginning to backfill into fly-metrics.net. However many will not be fully caught up yet.

This impacts metrics only, the underlying machines continue to work normally.
Jan 28, 02:49 UTC
Identified - A small number of hosts in the NRT (Tokyo) and SIN (Singapore) are reporting delayed metrics to the hosted Grafana charts at fly-metrics.net. Users with machines on impacted hosts will see delayed or spotty metrics in their Grafana charts.

Only metrics for these machines are impacted. The underlying machines continue to receive and serve traffic as usual, and all machine actions(stopping, starting, deploys etc.) continue to work normally.

We are processing the backlog of metrics on these hosts, but metrics will be delayed until this is complete.
Jan 27, 19:40 UTC
Jan 28, 2026
Jan 27, 2026
Jan 26, 2026

No incidents reported.

Jan 25, 2026

No incidents reported.

Jan 24, 2026
Congestion in CDG and FRA
Resolved - We are experiencing elevated weekend congestion in CDG (France) and FRA (Germany).
Jan 24, 16:00 UTC
Jan 23, 2026
Network maintenance in CDG
Completed - The scheduled maintenance has been completed.
Jan 23, 05:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 23, 00:00 UTC
Scheduled - An upstream provider is performing network maintenance in CDG on 2026-01-23, from 00:00 UTC (01:00am local time) to 05:00 UTC (06:00am local time). Apps may experience up to 30 minutes loss of connectivity within the scheduled maintenance window.
Jan 18, 13:01 UTC
Jan 22, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage