Skip to content

Interpreting this traceroute mystery

General Discussion by Doug 0 replies 150 views
#1

So I'm chasing this weird routing thing and I need fresh eyes. Traceroute from my home connection to my VPS at OVHcloud hits what looks like two different continents in the same hop.

traceroute to ovhcloud.com (203.0.113.47), 30 hops max
 7  peeringdb.com (198.51.100.14)  12.4 ms
 8  peeringdb.com (198.51.100.14)  145.3 ms
 9  ovhcloud.com (203.0.113.1)  146.1 ms

Same IP, two wildly different latencies. It's not congestion—the pattern's stable. My guess is anycast misconfiguration where two POPs announce the same prefix but only one actually routes to OVHcloud's backbone. Anyone seen this flavor of broken before?

Running this from a Contabo residential line if that matters.

grabs popcorn, checks /r/drama

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft