Ok Reddit hive-mind, here’s a puzzle for you. What the heck is going on with my network routing.

I’ve been having speed issues connecting to things like deb.debian.org, started to investigate, and uncovered some trace route weirdness I’m hoping someone can explain. I do get traffic through to deb.debian.org, but at around 60kbps on a gigabit fiber connection. This doesn’t happen on all sites, just some of them, so I’m thinking this is an external ISP issue?

Linux Box - regular traceroute:

XXX@YYY:/etc# traceroute deb.debian.org
traceroute to deb.debian.org (151.101.126.132), 30 hops max, 60 byte packets
1 REDACTED 0.279 ms 0.244 ms 0.230 ms
2 REDACTED 2.765 ms 3.398 ms 3.380 ms
3 208-40-16-73.ipv4.firstcomm.com (208.40.16.73) 3.860 ms 3.844 ms 3.827 ms
4 xe-3-1-2.bar2.cleveland1.level3.net (4.53.198.53) 4.306 ms 4.278 ms 4.196 ms
5 ae1.9.bar1.toronto1.level3.net (4.69.151.109) 9.754 ms 9.736 ms 9.767 ms
6 * * *
…
30 * * *
XXX@YYY:

Huh… Same results on windows box? = nope; results are normal on windows

C:\Users\XXX>tracert deb.debian.org
Tracing route to debian.map.fastlydns.net [151.101.126.132]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms REDACTED
2 3 ms 3 ms 27 ms REDACTED
3 3 ms 3 ms 3 ms 208-40-16-73.ipv4.firstcomm.com [208.40.16.73]
4 4 ms 3 ms 3 ms xe-3-1-2.bar2.cleveland1.level3.net [4.53.198.53]
5 9 ms 9 ms 11 ms ae1.9.bar1.toronto1.level3.net [4.69.151.109]
6 17 ms 17 ms 17 ms 4.16.49.70
7 9 ms 9 ms 9 ms 151.101.126.132
Trace complete.

So… TCP traceroute on linux box? = matches windows:

XXX@YYY:/etc# traceroute -T deb.debian.org
traceroute to deb.debian.org (151.101.126.132), 30 hops max, 60 byte packets
1 REDACTED 0.093 ms 0.065 ms *
2 REDACTED 3.609 ms * *
3 208-40-16-73.ipv4.firstcomm.com (208.40.16.73) 3.263 ms 3.324 ms 3.391 ms
4 xe-3-1-2.bar2.cleveland1.level3.net (4.53.198.53) 3.825 ms * *
5 * * ae1.9.bar1.toronto1.level3.net (4.69.151.109) 11.826 ms
6 4.16.49.70 (4.16.49.70) 17.343 ms * *
7 * * 151.101.126.132 (151.101.126.132) 9.489 ms
XXX@YYY:/etc#

Ok, so what about google (normally working site) on the linux box with a regular traceroute = totally normal results:

XXX@YYY:/etc# traceroute google.com
traceroute to google.com (142.251.32.78), 30 hops max, 60 byte packets
1 REDACTED 0.298 ms 0.274 ms 0.261 ms
2 REDACTED 2.941 ms 2.983 ms 3.047 ms
3 208-40-16-73.ipv4.firstcomm.com (208.40.16.73) 3.528 ms 3.506 ms 3.487 ms
4 xe-3-1-2.bar2.cleveland1.level3.net (4.53.198.53) 4.049 ms 4.011 ms 3.992 ms
5 ae14.14.bar2.toronto1.level3.net (4.69.216.246) 10.756 ms ae0.11.bar2.toronto1.level3.net (4.69.151.242) 9.326 ms 9.353 ms
6 72.14.195.72 (72.14.195.72) 9.665 ms 9.531 ms 9.504 ms
7 74.125.244.161 (74.125.244.161) 18.851 ms 74.125.244.145 (74.125.244.145) 11.404 ms 74.125.244.161 (74.125.244.161) 18.728 ms
8 142.251.68.25 (142.251.68.25) 19.333 ms 19.346 ms 19.303 ms
9 yyz12s07-in-f14.1e100.net (142.251.32.78) 10.376 ms 19.454 ms 10.336 ms
XXX@YYY:/etc#

​

​

What the heck is going on here?

Are those *'s in the last trace route indicative of packet loss?

Is this a me firewall setting, or external network shenanigans?

Any help appreciated. Thanks.