outages.live
Live
Fly.ioIncident ยท

IPv6 egress issues on a subset of IAD hosts

ResolvedOfficial update
0

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.

State

Resolved

Started

Lasted

23 min

Worst impact

Degraded

Timeline

3 updates
09:5510:0010:0610:1210:17
DegradedUpdate postedTimes in UTC

Identified

23 min 100%

Updates

Times in UTC

As posted by Fly.io

Resolved

All affected hosts are back to normal.

Identified

Due to an upstream provider issue, IPv6 egress is unavailable on a subset of IAD hosts. Internet-facing IPv6 services are unaffected.

Identified

Due to an upstream provider misconfiguration, IPv6 egress is unavailable on a subset of IAD hosts. Internet-facing IPv6 services are unaffected.

Fly.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

19

Median duration

1 h 22 min

This incident

72% shorter than 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 22 min
90 days agoToday

Other Fly.io incidents

All incidents

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

Fly.ioยทEmergency maintenance in IAD

Fly.io reports an emergency network maintenance in the IAD region. Machines on some hosts were unreachable. Fly.io reports that the maintenance is complete and the incident is resolved. The incident lasted 38 minutes.

Resolved

Fly.ioยทOutbound IPv4 connectivity failures in ARN, JNB, and GRU

Outbound IPv4 connectivity failed for machines with static egress IPs in the ARN, JNB, and GRU regions. IPv6 connectivity was not affected. Fly.io resolved the incident after 2 hours and 10 minutes.

Resolved

Fly.ioยทSlow image pulls delaying Machine starts in IAD

Image pull times in IAD have returned to normal.

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