outages.live
Live
Fly.ioIncident ยท 2026-11-01 18:50 UTC

Outbound IPv4 connectivity failures in ARN, JNB, and GRU

ResolvedOfficial update
0

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 on 1 November 2026 after 130 minutes.

State

Resolved

Started

6 h ago

2026-11-01 18:50 UTC

Lasted

2 h 10 min

until 2026-11-01 21:00 UTC

Worst impact

Degraded

Timeline

5 updates
18:5019:2319:5520:2721:00
DegradedUpdate postedTimes in UTC

Identified

1 h 36 min 74%

Monitoring

33 min 26%

Updates

Times in UTC

As posted by Fly.io

Resolved2026-11-01 21:00 UTC

We've fixed affected regions and everything is back to normal.

Monitoring2026-11-01 20:27 UTC

We've rolled out fixes to the affected regions and are monitoring for any additional issues.

Identified2026-11-01 19:27 UTC

We have identified the issue and are working to resolve in the affected regions. Newly created static egress IPs may continue to see problems while we roll out fixes.

Identified2026-11-01 18:57 UTC

We are working to resolve an issue with outbound IPv4 connectivity failures affecting machines with in the ARN, JNB, and GRU regions.

Identified2026-11-01 18:51 UTC

We are working to resolve an issue with outbound IPv4 connectivity failures affecting machines with static egress IPs in the ARN, JNB, and GRU regions. IPv6 connectivity is unaffected at this time.

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