Investigating - We are investigating instability in the MPG control plane in the NRT (Toyko, Japan) region causing unexpected cluster failovers. Clusters return to health shortly after, but some users with clusters in NRT may see dropped connections or degraded performance at this time.
Apr 10, 2026 - 18:42 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 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 Degraded Performance
90 days ago
99.94 % uptime
Today
Management Plane - ORD Operational
90 days ago
99.96 % uptime
Today
Management Plane - IAD Operational
90 days ago
99.81 % uptime
Today
Management Plane - FRA Operational
90 days ago
99.95 % uptime
Today
Management Plane - GRU Operational
90 days ago
100.0 % uptime
Today
Management Plane - LAX Operational
90 days ago
100.0 % uptime
Today
Management Plane - SYD Operational
90 days ago
99.96 % uptime
Today
Management Plane - AMS Operational
90 days ago
99.77 % uptime
Today
Management Plane - LHR Operational
90 days ago
100.0 % uptime
Today
Management Plane - NRT Degraded Performance
90 days ago
100.0 % uptime
Today
Management Plane - SIN Operational
90 days ago
99.87 % 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
Sprites 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.
Apr 10, 2026

Unresolved incident: Managed Postgres control plane instability in NRT (Tokyo).

Apr 9, 2026
Resolved - This incident has been resolved.
Apr 9, 20:14 UTC
Investigating - Some hosts in our Chicago (ORD) region are currently inaccessible. We are working with our provider to resolve this issue.
To see if you are affected, please visit the personalized status page: https://fly.io/status

A small amount of Managed Postgres clusters may also be inaccessible at this time.

Apr 9, 19:29 UTC
Resolved - This incident has been resolved.
Apr 9, 05:30 UTC
Monitoring - Control plane operations in SYD have returned to normal and all clusters are healthy at this time. We're continuing to monitor to ensure stable recovery.
Apr 9, 05:20 UTC
Identified - We are seeing an improvement in control plane performance in the SYD region. Some clusters in the region currently are showing degraded standby nodes and we are working to bring those back to full health.
Apr 9, 04:12 UTC
Investigating - We are investigating elevated control plane issues for Managed Postgres clusters in SYD.

The majority of clusters appear to be running fine, but new creates, backup restores, and upgrades may show errors or take longer than usual to complete. Some clusters will have seen a failover event from primary to standby.

Apr 9, 03:50 UTC
Apr 8, 2026
Resolved - This incident has been resolved.
Apr 8, 12:23 UTC
Update - We are continuing to monitor for any further issues.
Apr 8, 11:02 UTC
Monitoring - We have implemented a fix. We're monitoring the cluster for further issues.
Apr 8, 11:00 UTC
Investigating - We are currently investigating an issue with our metrics cluster.
Apr 8, 08:34 UTC
Apr 7, 2026
Resolved - This incident has been resolved.
Apr 7, 18:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 7, 15:39 UTC
Identified - We have restored GraphQL and dashboard availability, but some actions (e.g. app state updates) may still be delayed.
Apr 7, 15:17 UTC
Investigating - We are investigating issues with our GraphQL API and web dashboard
Apr 7, 15:08 UTC
Apr 6, 2026

No incidents reported.

Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

Apr 3, 2026

No incidents reported.

Apr 2, 2026
Completed - The scheduled maintenance has been completed.
Apr 2, 15:30 UTC
Update - Maintenance has been extended by one hour. The new maintenance window is 12:30-15:30 UTC (5:30am-8:30am local time). We will continue to provide updates as necessary.
Apr 2, 14:36 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 2, 12:30 UTC
Scheduled - We will be performing scheduled network maintenance in the SJC (San Jose, California) region between 12:30-14:30 UTC (5:30am-7:30am local time).

During this period a brief outage of ~5m is expected for each machine.

Mar 18, 20:56 UTC
Apr 1, 2026

No incidents reported.

Mar 31, 2026

No incidents reported.

Mar 30, 2026

No incidents reported.

Mar 29, 2026
Resolved - This incident has been resolved.
Mar 29, 16:01 UTC
Update - We've freed up additional room in the SIN and AMS regions and are monitoring capacity.
Mar 29, 15:35 UTC
Monitoring - We've freed up additional room in the SIN and AMS regions and are monitoring capacity.
Mar 29, 15:33 UTC
Update - We are currently investigating capacity issues in SIN and AMS regions that are affecting:
- Machine Create and Start events
- Deployments, due to affected, degraded Remote Builders
- Sprite startup from cold state

Mar 29, 15:19 UTC
Update - This may also affect:
- Remote builders in AMS and SIN regions, which could currently be experiencing degraded performance or failures.
- Sprites starting from a cold state, which may experience failures in starting

Mar 29, 15:13 UTC
Identified - We are currently investigating elevated errors when creating and starting machines in the SIN and AMS regions. Choosing other regions to create or deploy may help in the meantime
Mar 29, 15:00 UTC
Mar 28, 2026

No incidents reported.

Mar 27, 2026
Resolved - This incident has been resolved.
Mar 27, 21:51 UTC
Monitoring - With the additional capacity we've brought online, machine start failure rates in IAD have now recovered. We'll continue to monitor IAD capacity.
Mar 27, 21:09 UTC
Identified - We've brought some additional capacity online in IAD and are seeing improvements, and we're continuing to work on adding more and freeing up additional room.
Mar 27, 19:21 UTC
Update - We're continuing to evaluate our options for increasing short-term capacity in the IAD region.
Mar 27, 18:47 UTC
Investigating - We're currently investigating capacity issues in IAD that is preventing machine starts (machine creates are currently unaffected). This may result in deploys failing to complete (even for apps outside of the IAD region). As a workaround, using legacy Fly builders explicitly located in another region (i.e., `FLY_REMOTE_BUILDER_REGION=lhr fly deploy --depot=false --recreate-builder`) may help in the meantime.
Mar 27, 18:08 UTC