Between ~18:00 - 18:10 UTC today we saw degraded edge performance across multiple regions. Customers may have noticed elevated numbers of dropped connections or longer than usual connection times reaching their apps during this period.

A fix was applied and edge performance is back to normal levels.

An upstream provider is performing network maintenance on a subset of hosts in IAD on 2026-10-28, from 13:00 UTC to 15:00 UTC. A loss of connectivity of up to 30 minutes is possible within the scheduled maintenance window.

We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal.

All host restarts have been completed and the platform is operating normally.

A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see further updates on the personalized status page viewable at https://fly.io/status

The fly-metrics.net hosted Grafana and log search instance is now fully reachable.

Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.

Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes

This has been resolved

From approximately 2026-10-11 23:30 UTC through 2026-10-12 00:45 UTC some or all hosted sprites on the *.sprites.app subdomain were unavailable due to a certificate error.

As of 00:45 UTC this incident has been resolved.

The issue has been resolved.

This incident has been resolved.

IPv6 upstream issue was solved.

Maintenance has completed

All impacted services are operational now.

Maintenance has completed

This incident has been 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.

This incident has been resolved.

This incident has been resolved.

This incident has been 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.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

The scheduled maintenance has been completed.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.