Telia peering at Chicago has some strange routes. I get this from Telia's LG.
Traffic goes from Chicago to San Jose then back to Chicago (can't seem to traceroute past 72.52.92.70, but that's not the issue).
TeliaSonera Looking Glass - traceroute core1.chi1.he.net as-number-lookup
Router: Chicago
Command: traceroute core1.chi1.he.net as-number-lookup
traceroute to core1.chi1.he.net (216.218.252.168), 30 hops max, 40 byte packets
1 sjo-bb1-link.telia.net (213.248.80.25) 46.633 ms 46.598 ms 46.622 ms
2 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 55.959 ms 52.225 ms 49.541 ms
3 10gigabitethernet4-1.core1.sjc2.he.net (72.52.92.70) [AS 6939] 48.043 ms 48.031 ms 48.113 ms
This seems to be the reason: The whole /17 that is routed through San Jose. Please take a look at this! Unless there is some reason this was done, then nevermind.
TeliaSonera Looking Glass - show route protocol bgp core1.chi1.he.net
Router: Chicago
Command: show route protocol bgp core1.chi1.he.net
inet.0: 310197 destinations, 2230193 routes (310060 active, 67 holddown, 1170 hidden)
@ = Routing Use Only, # = Forwarding Use Only
+ = Active Route, - = Last Active, * = Both
216.218.128.0/17 *[BGP/170] 10w4d 21:20:27, MED 1, localpref 200, from 213.248.80.244
AS path: 6939 6939 I
> to 213.248.80.25 via so-6/1/0.0
[BGP/170] 10w4d 21:20:27, MED 1, localpref 200, from 213.248.80.240
AS path: 6939 6939 I
> to 213.248.80.25 via so-6/1/0.0
[BGP/170] 10w4d 21:20:27, MED 1, localpref 200, from 213.248.80.247
AS path: 6939 6939 I
> to 213.248.80.25 via so-6/1/0.0
[BGP/170] 10w4d 21:20:27, MED 1, localpref 200, from 213.248.80.241
AS path: 6939 6939 I
> to 213.248.80.25 via so-6/1/0.0
[BGP/170] 3d 02:28:46, MED 0, localpref 150
AS path: 3549 6939 6939 I
> to 64.212.107.141 via xe-0/2/0.0
Hitting a router's IP won't usually give you great results due to filter rules. Hitting something through it tends to be more useful. What is the trace you're trying to do that doesn't involve the router's IP?
I didn't think before I picked a point to trace against.
I'm trying to get to the Chicago tunnel server of course.
Here's a more useful trace to the tunnel server (tserv9.chi1.ipv6.he.net) from Telia Chicago. Still jumps around the US even though it's already there.
TeliaSonera Looking Glass - traceroute 209.51.181.2 as-number-lookup
Router: Chicago
Command: traceroute 209.51.181.2 as-number-lookup
traceroute to 209.51.181.2 (209.51.181.2), 30 hops max, 40 byte packets
1 dls-bb1-link.telia.net (213.248.80.149) 20.960 ms 20.924 ms 21.004 ms
2 atl-bb1-link.telia.net (213.248.80.145) 45.157 ms 42.314 ms 42.500 ms
3 hurricane-ic-129712-atl-bb1.c.telia.net (213.248.79.70) 40.912 ms 44.937 ms 40.899 ms
4 10gigabitethernet6-4.core1.ash1.he.net (72.52.92.157) [AS 6939] 47.176 ms 57.934 ms 46.305 ms
5 10gigabitethernet1-2.core1.nyc4.he.net (72.52.92.85) [AS 6939] 45.139 ms 47.737 ms 47.831 ms
6 10gigabitethernet1-2.core1.chi1.he.net (72.52.92.102) [AS 6939] 50.131 ms 52.581 ms 49.958 ms
7 tserv9.chi1.ipv6.he.net (209.51.181.2) [AS 6939] 46.751 ms 45.423 ms 56.568 ms
I'm getting the same route from a Chicago provider who uses Telia for transit. Does Telia peer with you guys in Chicago?