Broken Routing Tables @ 2.120.14.17

xIHydra- — Sat, 21 Jun 2025 13:55:24 GMT

Hello

I'm having issues with connectivity to certain European servers.

I did some quick tests and it appears that `2.120.14.17` - one of your servers is dropping 100% of packets, indicating incorrect/poor routing on your end.

Here are the results of ping and pathping to the server i'm having issues with.

PS C:\WINDOWS\system32> pathping 94.250.199.40

Tracing route to 94.250.199.40 over a maximum of 30 hops

0 DESKTOP-SMN3GQ6.Home [192.168.0.50]

1 SkyRouter.Home [192.168.0.1]

2 2.127.238.243

3 2.120.14.73

4 2.120.14.17

5 fra-eq6-pr1.zet.net [103.246.249.30]

6 * * *

Computing statistics for 125 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 DESKTOP-SMN3GQ6.Home [192.168.0.50] 0/ 100 = 0% |1 2ms 0/ 100 = 0% 0/ 100 = 0% SkyRouter.Home [192.168.0.1] 3/ 100 = 3% | 2 17ms 4/ 100 = 4% 1/ 100 = 1% 2.127.238.243 0/ 100 = 0% | 3 18ms 3/ 100 = 3% 0/ 100 = 0% 2.120.14.73 3/ 100 = 3% | 4 --- 100/ 100 =100% 94/ 100 = 94% 2.120.14.17 0/ 100 = 0% | 5 35ms 6/ 100 = 6% 0/ 100 = 0% fra-eq6-pr1.zet.net [103.246.249.30] Trace complete.

"Pinging 2.120.14.17 with 32 bytes of data: Reply from 2.127.238.243: Destination net unreachable. Reply from 2.127.238.243: Destination net unreachable. Reply from 2.127.238.243: Destination net unreachable. Reply from 2.127.238.243: Destination net unreachable. Reply from 2.127.238.243: Destination net unreachable. Reply from 2.127.238.243: Destination net unreachable. Reply from 2.127.238.243: Destination net unreachable. Reply from 2.127.238.243: Destination net unreachable. Reply from 2.127.238.243: Destination net unreachable."

Pings to 2.120.14.17 fail with ‘Destination net unreachable’, but replies from 2.127.238.243. This is breaking my connectivity to [94.250.199.40]. Please check routing between these nodes.

Regards,

Jack.

Re: Broken Routing Tables @ 2.120.14.17

jamesn123 — Tue, 24 Jun 2025 09:24:32 GMT

@xIHydra-

This is entirely normal, some routers on networks will not respond to pings but will still pass traffic. If it was dropping say 50% of packets then this would likely indicate an issue, however 100% drop just suggests its not configured to respond to pings.

topic Broken Routing Tables @ 2.120.14.17 in Broadband

Broken Routing Tables @ 2.120.14.17

Re: Broken Routing Tables @ 2.120.14.17