# 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.

- Provider: [Fly.io](https://outages.live/fly.md)
- Type: Incident
- State: Resolved
- Worst impact: Degraded performance
- Started: 2026-11-01 18:50 UTC
- Resolved: 2026-11-01 21:00 UTC (lasted 2 h 10 min)
- Official update: https://status.flyio.net

## Updates from Fly.io

### resolved, 2026-11-01 21:00 UTC

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

### monitoring, 2026-11-01 20:24 UTC

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

### identified, 2026-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.

### identified, 2026-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.

### identified, 2026-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.