Status: Resolved All impacted services are operational now. Affected components
 <ul>
 <li>AMS - Amsterdam, Netherlands (Operational)</li>
<li>Management Plane - AMS (Operational)</li>
 </ul>

Partial outage in AMS

Status: Complete Maintenance has completed Affected components
 <ul>
 <li>EWR - Secaucus, NJ (US) (Operational)</li>
 </ul>

Maintenance: Network Maintenance in EWR

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Logs (Operational)</li>
 </ul>

Delayed ingestion of app logs

Status: Scheduled One of our upstream providers is conducting maintenance on a subset of our hosts in ORD on Tuesday, Oct 6th, 2026, from 09:00 - 11:00 UTC (04:00 - 06:00 CDT). Machines on affected hosts are expected to experience a total loss of connectivity for up to 30 minutes within the maintenance window. Affected components
 <ul>
 <li>ORD - Chicago, Illinois (US) (Under maintenance)</li>
 </ul>

Maintenance: Network Maintenance in ORD

Status: Resolved We observed networking issues affecting a subset of our hosts in GRU from 19:37 UTC through 19:59 UTC. This affected platform operations requiring leases, private networking, and internet connectivity to some endpoints.

GRU Networking Issues

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>AMS - Amsterdam, Netherlands (Operational)</li>
 </ul>

Network outage in AMS region

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>GRU - Sao Paulo, Brazil (Operational)</li>
 </ul>

State database issues in GRU

Status: Resolved This incident has been resolved Affected components
 <ul>
 <li>Customer Applications (Operational)</li>
 </ul>

Private Networking issues (6PN)

Status: Resolved Impact

From about 12:00 to 13:05 UTC, some clients got connection timeouts to their Redis databases. Affected were databases hosted in fra or gig, and clients whose connections were routed through fra or gig, even if their database is hosted in another region.

What happened

During a planned rolling upgrade, replicas in fra and gig did not finish draining and were left out of service. They were returned to Fly routing before they were ready to accept connections. Connections routed to them then timed out.

What we're changing

• We will be adding tooling to return a replica to service safely after maintenance.
• We will be adding safety checks to our upgrade process.
• We will make the upgrade procedure more resilient to errors like this one.

Upstash unavailability in FRA region

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Sprites (Operational)</li>
 </ul>

Partial Sprites outage

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Customer Applications (Operational)</li>
 </ul>

Elevated private networking errors

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>DFW - Dallas, Texas (US) (Operational)</li>
 </ul>

IPv6 Networking Issues in DFW

Status: Complete The scheduled maintenance has been completed. Affected components
 <ul>
 <li>ORD - Chicago, Illinois (US) (Operational)</li>
 </ul>

Maintenance: Network maintenance in ORD

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Deployments (Operational)</li>
 </ul>

Depot builder failures

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>LAX - Los Angeles, California (US) (Operational)</li>
<li>SJC - San Jose, California (US) (Operational)</li>
 </ul>

Network issues in US West Coast

Sprites API Partial Outage

Upstream network issues

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Machines API (Operational)</li>
 </ul>

API background job queue failure

Status: Complete The scheduled maintenance has been completed. Affected components
 <ul>
 <li>Customer Applications (Operational)</li>
 </ul>

Maintenance: 6PN Private Network Maintenance

Status: Resolved A configuration update caused temporary failures for incoming HTTP/2 traffic for Fly Machines located on a subset of hosts for a few minutes. This incident has since been resolved.

Managed Postgres depends on HTTP/2 and some control plane ops may have been affected as well. However, downstream Postgres connections were unlikely to have been affected by this since they do not use the HTTP2 handler.

HTTP/2 traffic disruptions

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>ORD - Chicago, Illinois (US) (Operational)</li>
 </ul>

Packet loss in ORD

Status: Resolved We saw Sprite deletion jobs failing between 21:18 and 22:05 UTC. This issue has been resolved.

Sprite deletion jobs failing

Networking Issues in GRU

Increased packet loss

Status: Complete The scheduled maintenance has been completed. Affected components
 <ul>
 <li>UDP Anycast (Operational)</li>
 </ul>

Maintenance: Anycast Edge Maintenance

Status: Resolved This incident has been resolved.

WireGuard gateway issues

Status: Resolved This is now resolved Affected components
 <ul>
 <li>Metrics (Operational)</li>
 </ul>

Metrics in some regions are lagging behind

Network Issues in LAX Region

Status: Resolved A BGP configuration error caused our Anycast DNS to route to some nodes without the proper DNS infrastructure. The issue was temporary and was resolved as soon as we removed that node from BGP.

Temporary DNS resolution failure

Oauth/Macaroon Errors from flyctl

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Management Plane - ORD (Operational)</li>
 </ul>

MPG (v1) partially down in ORD

Status: Resolved 6PN networking issues between some machines in YYZ during a rollout which was rolled back once we noticed errors. During this time some machines were unable to talk to internal resources like other DBs, other apps or MPG clusters.

6PN Networking issue in YYZ

Status: Resolved The capacity issue in the ARN region has been resolved. Affected components
 <ul>
 <li>Deployments (Operational)</li>
 </ul>

No capacity in ARN

Secrets service outage

IPv6 Networking Issues

Increased app-not-found errors

Status: Resolved Etcd is stable. Services are back to normal. Affected components
 <ul>
 <li>Management Plane - IAD (Operational)</li>
 </ul>

MPG IAD data plane degraded for new clusters

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Management Plane - GRU (Operational)</li>
 </ul>

MPG creation is failing in GRU due to lack of capacity

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>SSL/TLS Certificate Provisioning (Operational)</li>
 </ul>

Certificate issuance delays

Status: Resolved A BGP misconfiguration while provisioning new edge capacity caused most traffic from Europe endpoints to be dropped, between 14:50 UTC and 15:02 UTC. The misconfiguration has been fixed and we are implementing safeguards against this kind of issue in the future.

Inbound connection failure to Fly Apps

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Management Plane - IAD (Operational)</li>
 </ul>

Managed Postgres v2 control plane issues in iad

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>CDG - Paris, France (Operational)</li>
 </ul>

Capacity issues in CDG

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Dashboard (Operational)</li>
 </ul>

Outbound email issues

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Dashboard (Operational)</li>
<li>Deployments (Operational)</li>
<li>Machines API (Operational)</li>
 </ul>

Increased API latency

Status: Complete The scheduled maintenance has been completed. Affected components
 <ul>
 <li>DFW - Dallas, Texas (US) (Operational)</li>
 </ul>

Maintenance: Emergency network maintenance in DFW

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Machines API (Operational)</li>
<li>Dashboard (Operational)</li>
 </ul>

High number of 5XX on the Machines API and dashboard

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>BOM - Mumbai, India (Operational)</li>
 </ul>

Egress IPv6 issues in BOM

Status: Complete The scheduled maintenance has been completed.

The maintenance ended up taking a little bit longer than the scheduled time - it fully wrapped up roughly one hour after the scheduled end time. Affected components
 <ul>
 <li>FRA - Frankfurt, Germany (Operational)</li>
 </ul>

Maintenance: Network maintenance in FRA

Status: Resolved A bad deployment momentarily caused issues with Flycast connectivity, and, by extension, MPG, in our YYZ region. The deployment was immediately rolled back and connectivity was restored shortly after.

Brief Flycast / MPG interruption in YYZ

Edge proxy issues

App creation failing

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>SJC - San Jose, California (US) (Operational)</li>
 </ul>

Partial outage in SJC

Some DFW hosts offline

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Remote Builds (Operational)</li>
<li>Deployments (Operational)</li>
 </ul>

Is Fly.io down?

Fly.io status is UP

Lastest published events

Partial outage in AMS

Maintenance: Network Maintenance in EWR

Delayed ingestion of app logs

Fly.io Services, Components and Regions

Recent Fly.io events

Partial outage in AMS

Maintenance: Network Maintenance in EWR

Delayed ingestion of app logs

Maintenance: Network Maintenance in ORD

GRU Networking Issues

Network outage in AMS region