Live

Network maintenance in SYD

MaintenanceOfficial update

An upstream provider is performing network maintenance on a subset of hosts in SYD on 2026-11-20 from 17:00 to 19:00 UTC, (on 2026-11-21 from 04:00 - 06:00 local time). A full loss of connectivity for 40 minutes for apps on affected hosts is expected within the maintenance window.

The latest update from Fly.io.

State

Scheduled

Started

Ongoing for

17 h 30 min

Worst impact

Maintenance

Timeline

1 update
17:1921:4202:0406:2710:49
MaintenanceUpdate postedTimes in UTC

Scheduled

17 h 30 min 100%

Updates

Times in UTC

As posted by Fly.io

Scheduled

An upstream provider is performing network maintenance on a subset of hosts in SYD on 2026-11-20 from 17:00 to 19:00 UTC, (on 2026-11-21 from 04:00 - 06:00 local time). A full loss of connectivity for 40 minutes for apps on affected hosts is expected within the maintenance window.

Fly.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

26

Days with an incident

22

Median duration

1 h 33 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 days
median 1 h 33 min
90 days agoToday

Other Fly.io incidents

All incidents

Fly.io·GitHub connections reset - sign in with GitHub again to restore GitHub deploys

Fly.io reset all connections between Fly.io accounts and GitHub. Automatic deploys on push, and launching or redeploying an app from a GitHub repository in the dashboard, failed. The incident is resolved and lasted 3 hours 37 minutes. Sign in to Fly.io with GitHub again to restore GitHub deploys.

Resolved

Fly.io·LAX region outage

A subset of Apps and Managed Postgres clusters in the LAX region did not work. Fly.io reported an upstream datacenter power outage as the cause. Fly.io resolved the incident after 2891 minutes.

Resolved

Fly.io·IPv6 egress issues on a subset of IAD hosts

IPv6 egress did not work on a subset of IAD hosts in Fly.io. The issue came from an upstream provider. Fly.io reported that the incident is resolved and that all affected hosts are back to normal. The incident lasted 22 minutes.

Resolved

Fly.io·Emergency network maintenance on a subset of hosts in ORD

Fly.io reports that some machines in ORD were unreachable. A small subset of MPG clusters ran with reduced HA. Fly.io says the incident is resolved and the affected hosts are back online. The incident lasted about 14 minutes.

Resolved

Fly.io·Elevated Machine start failures in ARN

Fly.io reported elevated Machine start failures in the ARN region. Fly.io fixed the problem and reports that the incident is resolved. The incident lasted 61 minutes.

Resolved

Follow Fly.io

Your coding agent knows when Fly.io is down, and tells you when a failure is theirs, not yours. You can also get Fly.io incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "fly" and tell me if Fly.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=fly
Slack
/feed subscribe https://outages.live/feed.xml?providers=fly

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane