32 ms·
My ISP breaks traceroute outside of the network. Their transit is cut out of my traceroutes. Full technical story at https://blog.habets.se/2022/05/Another-way
by thomashabets2 4y ago
My ISP breaks traceroute outside of the network. Their transit is cut out of my traceroutes.
Full technical story at
https://blog.habets.se/2022/05/Another-way-MPLS-breaks-traceroute.html https://blog.habets.se/2022/05/Another-way-MPLS-breaks-trace...
- ShroudedNight 4y agoHuh, I remember back in the day seeing weird latency cliffs like that when trying to troubleshoot latency issues when playing World of Warcraft. There always seemed to be one between basically any ISP I was connected to and the AT&T network blizzard was running their servers on.
- thomashabets2 4y agoThe weird part is not any latency numbers (TTL exceeded is not handled by a router's fast path), but hops missing. Hops marked with "* * *" do not count as "missing" here.
- mike_d 4y agoIt looks like someone technical from your ISP also replied in the comments of your post and offered to set up a call to explain it to you. That is far better than you can expect from almost any other provider.
- thomashabets2 4y agoYeah, long story short I had a call with him, and he agreed that's probably right but it's not a priority to fix. I hope they'll fix it soon, but not if it delays IPv6. If I had a choice of FTTP providers then IPv6 support would weigh really high on my choice, but only one has dug up the street.