outages.live
Live
Fly.ioIncident · 2026-10-26 01:50 UTC

Packet loss in IAD

ResolvedOfficial update

The congestion affecting our upstream provider has been resolved. We are observing a return to normal levels of networking performance in IAD region.

The latest update from Fly.io.

State

Resolved

Started

6 d ago

2026-10-26 01:50 UTC

Lasted

2 h 33 min

until 2026-10-26 04:24 UTC

Worst impact

Degraded

Timeline

2 updates
01:5002:2903:0703:4504:24
DegradedUpdate postedTimes in UTC

Identified

2 h 33 min 100%

Updates

Times in UTC

As posted by Fly.io

Resolved2026-10-26 04:24 UTC

The congestion affecting our upstream provider has been resolved. We are observing a return to normal levels of networking performance in IAD region.

Identified2026-10-26 01:50 UTC

A subset of hosts in IAD region are experiencing elevated packet loss due to congestion at an upstream provider. We are working with the provider to resolve this issue. Apps hosted in IAD region may experience packet loss at this time.

Fly.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

19

Days with an incident

15

Median duration

1 h 38 min

This incident

1.6× the median

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

12 h 53 min
median 1 h 38 min
90 days agoToday

Other Fly.io incidents

All incidents

Fly.io·Slow image pulls delaying Machine starts in IAD

Image pull times in IAD have returned to normal.

Resolvedresolved 1 d ago

Fly.io·Elevated issues with the Machines API

The incident has been resolved.

Resolvedresolved 2 d ago

Fly.io·Creating WireGuard peers in ARN is currently broken

The ARN WireGuard gateways are up

Resolvedresolved 3 d ago

Fly.io·Degraded networking to AWS IPs

This incident has been resolved, connectivity from AWS to all of our hosts is back to normal.

Resolvedresolved 5 d ago

Fly.io·MPGv2 IAD control plane is read-only

Control plane operations in IAD, including resizing and changing plans, are working normally again.

Resolvedresolved 7 d ago

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.cc/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.cc/feed.xml?providers=fly
Slack
/feed subscribe https://outages.cc/feed.xml?providers=fly

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane