Fly.io 37.16.18.81 IP not connecting from Starlink network

1

Hello, I am using a residential Starlink network whose public address is 129.222.187.227
This network is not connecting to the service even though DNS works alright.

PING fly.io (37.16.18.81): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
— fly.io ping statistics —
3 packets transmitted, 0 packets received, 100.0% packet loss

From normal broadband.
PING fly.io (37.16.18.81): 56 data bytes
64 bytes from 37.16.18.81: icmp_seq=0 ttl=53 time=107.667 ms
^C
— fly.io ping statistics —
1 packets transmitted, 1 packets received, 0.0% packet loss

Any ideas on where the issue is?

2

FYI, it has been working for weeks. Just stopped some time today

3

can you run a mtr or traceroute? mtr -rwbzo "LSD NABVW" 37.16.18.81
this should show where the issue is.

4

/opt/homebrew/sbin/mtr -rwbzo “LSD NABVW” 37.16.18.81 ─╯
Start: 2026-06-13T15:14:54+0300
HOST: Zemuldos-MacBook-Pro.local Loss% Snt Drop Last Avg Best StDev Wrst

  1. AS??? 192.168.1.1 0.0% 10 0 2.7 2.2 1.8 0.2 2.7
  2. AS??? 100.64.0.1 0.0% 10 0 22.2 27.2 20.5 5.5 35.6
  3. AS??? 172.16.253.86 0.0% 10 0 26.0 30.2 23.9 3.6 34.1
  4. AS??? ??? 100.0 10 10 0.0 0.0 0.0 0.0 0.0
  5. AS14593 undefined.hostname.localhost (206.224.70.244) 0.0% 10 0 18.7 23.3 18.7 3.4 30.5
  6. AS30844 197.155.93.57.liquidtelecom.net (197.155.93.57) 40.0% 10 4 144.4 145.4 140.0 3.9 150.7
  7. AS30844 et-0-1-1.lke-p5-nbi.liquidtelecom.net (41.60.137.58) 50.0% 10 5 114.9 116.1 113.9 1.9 118.7
  8. AS30844 et-1-1-6.lke-pe3-nbi.liquidtelecom.net (197.155.94.47) 20.0% 10 2 138.2 147.4 138.2 12.2 174.3
  9. AS30844 41.220.224.98.liquidtelecom.net (41.220.224.98) 40.0% 10 4 142.7 142.9 140.4 1.5 144.1
  10. AS3491 31713 hu0-0-0-20.br03.jnb01.as3491.net (63.223.48.142) 30.0% 10 3 143.7 142.4 137.7 3.5 148.1
  11. AS??? ??? 100.0 10 10 0.0 0.0 0.0 0.0 0.0
5

FYI this has also happened to our services hosted on fly with direct HTTP termination on Fly proxy. The app has the shared public ip 66.241.125.77. We have had to terminate within Cloudflare to make the services accessible behind Starlink