I'm in Denver on CenturyLink (AS209) and used to route to tsrv1.den1 without leaving Denver. Sometime in the recent past though, CL has been routing me to Dallas to to get to the HE network which then sends me back to Denver via Kansas City. The loop causes my 60/30 DSL to act like 25/20 for IPV6.
traceroute tserv1.den1.he.net
traceroute to tserv1.den1.he.net (184.105.250.46), 30 hops max, 60 byte packets
1 67.41.xxx.xxx (67.41.xxx.xxx) 0.280 ms 0.249 ms 0.242 ms
2 hlrn-dsl-gw06.hlrn.qwest.net (207.225.112.6) 22.104 ms 22.086 ms 22.087 ms
3 hlrn-agw1.inet.qwest.net (71.217.188.41) 22.074 ms 22.109 ms 22.106 ms
4 dal-pcor-03.inet.qwest.net (67.14.2.178) 38.492 ms 38.951 ms 38.958 ms
5 10ge6-2.core1.dal1.he.net (184.105.35.233) 39.471 ms 39.455 ms 39.423 ms
6 10ge5-3.core1.mci3.he.net (184.105.222.9) 52.718 ms 49.903 ms 51.848 ms
7 10ge15-4.core1.den1.he.net (184.105.222.21) 93.292 ms 67.881 ms 81.341 ms
8 tserv1.den1.he.net (184.105.250.46) 68.314 ms 68.322 ms 68.766 ms
CenturyLink was no help of course. This was their response...
QuoteThank you for contacting CenturyLink.
Based on the information you have provided, we don?t see any issue as described, we have Peering Agreements that are based on efficiency and cost and we can't investigate any unless ping rates are very high , when pinging to a URL or IP address. If you can?t get to a certain site please provide the URL/IP, the ping and tracert to that site.
Can you guys help at all?
ipv6@he.net is probably your best bet
Same issue here. I used to get to the Denver tunnel with almost zero latency, now I get about 45ms added to my ping time via IPv4 to the tunnel IP:
traceroute to 184.105.250.46 (184.105.250.46), 30 hops max, 60 byte packets
1 corona.wildlava.net (10.1.2.1) 0.299 ms 0.302 ms 0.417 ms
2 hlrn-dsl-gw07.hlrn.qwest.net (207.225.112.7) 18.690 ms 18.847 ms 19.053 ms
3 hlrn-agw1.inet.qwest.net (71.217.188.49) 18.820 ms 19.310 ms 19.035 ms
4 dap-brdr-05.inet.qwest.net (67.14.2.178) 35.638 ms 35.774 ms 35.782 ms
5 10ge6-2.core1.dal1.he.net (184.105.35.233) 35.831 ms 35.967 ms 35.974 ms
6 100ge12-2.core1.mci3.he.net (184.105.81.205) 49.143 ms 47.279 ms 47.435 ms
7 10ge15-4.core1.den1.he.net (184.105.222.21) 64.619 ms 70.856 ms 70.192 ms
8 tserv1.den1.he.net (184.105.250.46) 64.504 ms 64.514 ms 63.822 ms