No route to host

1

image
image2662Ă—410 127 KB

image
image3630Ă—234 145 KB

2

Switching from Wifi to 5G solved it. Seems like an internet problem on my end. But it’s still weird that this only fails for the Fly API.

3

If this ever happens again, you can trace the route to api.fly.io.

Linux:

> traceroute api.fly.io

Windows:

> tracert api.fly.io

The trace dump will show at which point the packets get lost.

4

I’m running into the same issue. This is the output of traceroute api.fly.io:

traceroute to api.fly.io (77.83.143.220), 64 hops max, 52 byte packets
 1  dlinkrouter5821.(null) (192.168.11.1)  2.751 ms  2.133 ms  2.202 ms
 2  192.168.1.1 (192.168.1.1)  2.728 ms  2.728 ms  2.356 ms
 3  118.174.216.1 (118.174.216.1)  13.121 ms  20.258 ms  16.130 ms
 4  100.127.0.101 (100.127.0.101)  16.061 ms  12.736 ms  12.426 ms
 5  * * *
 6  node-16zp.pool-125-24.dynamic.totinternet.net (125.24.217.165)  23.851 ms
    node-16zl.pool-125-24.dynamic.totinternet.net (125.24.217.161)  19.827 ms  19.112 ms
 7  203.113.59.174 (203.113.59.174)  20.575 ms
    203.113.61.242 (203.113.61.242)  26.431 ms
    203.113.59.154 (203.113.59.154)  20.603 ms
 8  hu0-11-0-0.kkm-core-01.totiig.net (203.190.250.209)  21.014 ms
    hu0-10-0-0.toth-core-01.totiig.net (203.190.251.69)  20.535 ms
    hu0-19-0-3.toth-core-01.totiig.net (203.190.251.177)  20.846 ms
 9  in-addr.net (180.180.255.39)  75.601 ms *  76.264 ms
10  * * *
11  * * in-addr.net (203.190.251.87)  43.441 ms
12  * * *
13  * * *
14  * * *

Can anyone make sense of this? :slight_smile: After this output it just seems to be adding rows with stars.

5

Can anyone make sense of this?

It looks like the problem lies in the network routing of totiig.net (National Telecom Public Company Limited, Bangkok, Thailand).

Just note how a packet traverses that node:

hu0-19-0-3.toth-core-01.totiig.net (203.190.251.177)  20.846 ms

and then bounces back to the same ISP subnet 203.190.251.0/24:

11  * * in-addr.net (203.190.251.87)  43.441 ms

and then it is dead silent going nowhere:

12  * * *
13  * * *
14  * * *

So this is the problem of a particular ISP. It is always a good idea to contact ISP support and send them this trace dump.

1 Like
6

Thanks for the explanation of that output. Appreciate it!

7

For anyone else that’s running into this issue, this is what worked for me: I configured the DNS server for this WiFi network to use 8.8.8.8 (google public DNS) instead.

For Mac:

System Preferencs → Network → Press “Details” behind your Wifi network → DNS

image
image1384Ă—1184 111 KB