Hi Fly team,
Since today, traffic from Bharti Airtel broadband in Gurugram, India (AS24560) reaches Fly’s anycast IPv4 through the São Paulo (gru) edge instead
of an Asian one. Our app runs in sin, so every request goes India → Brazil → Singapore and back.
App: multitec-sales (one machine in sin, v160, no deploys since 22 Sep)
Anycast IP: 66.241.125.107
Client IP: 122.160.70.45 (Airtel, AS24560, Gurugram, IN)
Time: 2026-09-28 ~14:30–14:40 UTC, still happening
It is not just our app. https://debug.fly.dev/ from the same connection returns Fly-Region: gru.
Request IDs (all land on gru, each about 1.2s for a static CSS file):
- 01M3M7A9NPR2BMAKS2C919NH9N-gru
- 01M3M7ACKFA8GHB2Q8FGRH5STG-gru
- 01M3M7AF6BMXSKQXNTHWFV86PC-gru
Ping to 66.241.125.107: avg 292 ms (min 277). Google from the same line: about 14 ms connect.
Traceroute:
1 192.168.3.2 29.9 ms (home router)
2 122.161.47.255 8.8 ms (Airtel)
3 125.18.73.17 4.9 ms (Airtel)
4 116.119.121.16 130.4 ms (Airtel international)
5 187.16.209.245 262.0 ms (IX.br São Paulo)
6 79.127.195.140 271.6 ms (Fly, gru)
7+ *
Airtel seems to be picking up the Fly anycast prefix at IX.br São Paulo, not at a nearby exchange. Could you check how 66.241.125.0/24 is announced
to AS24560, and whether the SIN or BOM path has dropped?
Thanks!