rewindex

ChangesFly.ioOutbound IPv4 connectivity failures in ARN, JNB, and GRU

Fly.io: Incident updated: Outbound IPv4 connectivity failures in ARN, JNB, and GRU

Incident updateNormal progress (rule, 100%)Changed status.flyio.net (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Fly.io removed; blue is what they added. Muted text is unchanged context.

AddedUpdateidentified#1
Before: not present
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Sunday, November 1

3 incident changes

Cite this

Incident updated: Outbound IPv4 connectivity failures in ARN, JNB, and GRU on Fly.io’s status page, changed 2026-11-01 19:33 UTC (change 1 of 3).

Title
Incident updated: Outbound IPv4 connectivity failures in ARN, JNB, and GRU
Vendor
Fly.io
Date
URL
https://rewindex.com/change/r46b182397755ed

All Fly.io changesFly.io profileMarkdownJSON