Tokyo tunnel server routing

[rm]

Hello,

As we can see on http://www.tunnelbroker.net/usage/tunnels_by_latency.php, only about 19 tunnels on the Tokyo tunnel server have ping less than 100 msec (the 20th tunnel in the top list has 108ms).

The traceroutes look like this:

Code Select Expand

Host                                          Loss%   Snt   Last   Avg  Best  Wrst StDev
1. cloud1.japan.so.cm                          0.0%    11    0.0   0.1   0.0   0.1   0.0
2. ge3-42.ar1.tko1.jp.scnet.net                0.0%    10   11.1   6.8   0.4  53.9  16.9
3. xe-0-0-0.cr1.tko1.jp.scnet.net              0.0%    10    0.3   2.0   0.3  17.0   5.3
4. ???
5. tserv1.tyo1.he.net                          0.0%    10  120.1 120.2 120.1 120.2   0.0


Code Select Expand


core1.tyo1.he.net> traceroute 50.31.254.105 source-ip 27.50.33.5 numeric
1 126 ms 126 ms 126 ms 10gigabitethernet3-3.core1.sjc2.he.net (72.52.92.237)
2 134 ms 134 ms 127 ms 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69)
3 127 ms 127 ms 127 ms softbanktelecom.10gigabitethernet2-2.core1.pao1.he.net (216.218.244.234)
4 233 ms 233 ms 233 ms STOrw-51-tengiga7-4.gw.odn.ad.jp (210.142.163.169)
5 233 ms 233 ms 233 ms STOrk-07G4-0-0.nw.odn.ad.jp (143.90.33.117)
6 277 ms 401 ms 345 ms STOrw-12T2-1.nw.odn.ad.jp (143.90.192.134)
7 246 ms 240 ms 237 ms 26.143090232.odn.ne.jp (143.90.232.26)
8 118 ms 124 ms 128 ms xe-0-0-1.gw402.ty2.ap.equinix.com (183.177.32.153)
9 122 ms 125 ms 125 ms xe-0-1-1.gw401.ty2.ap.equinix.com (183.177.32.140)
10 125 ms 125 ms 125 ms xe-0-0-0.gw401.ty1.ap.equinix.com (202.177.203.49)
11 127 ms 125 ms 125 ms e-1-3.br401.ty1.ap.equinix.com (183.177.32.158)
12 120 ms 125 ms 125 ms 202.177.202.226
13 125 ms 128 ms 122 ms tge2-3.ar1.tko1.jp.scnet.net (75.102.60.153)
14 125 ms 125 ms 117 ms as32780.ge3-42.ar1.tko1.jp.scnet.net (75.102.60.22)
15 117 ms 117 ms 117 ms cloud1.japan.so.cm (50.31.254.105)

So it first goes to San Jose in the US for the outbond transfer from core1.tyo1.he.net, and presumably from the tunnel server too. It's not just to my particular network, according to http://tunnelbroker.net/usage/tunnels_by_tserv.php there are 1490 tunnels on the Tokyo tunnel server, and judging from the top latency list, 1471 of them are affected by this issue and have ping higher than 100 msec to the tunnel server. Can you please look into fixing this situation?

Thanks

[Thinktube]

Yes, this is a problem! The latency from a location in Japan (close to Osaka) to Tokyo is 250ms right now... Traffic gets routed over the US. Is there any plan to fix this soon? If not it would be better to change the endpoint to somewhere in the US...

Here is my traceroute:

root@inet-gw:~# traceroute 74.82.46.6
traceroute to 74.82.46.6 (74.82.46.6), 30 hops max, 38 byte packets
 1  221.113.141.105 (221.113.141.105)  2.289 ms  2.092 ms  2.027 ms
 2  221.113.141.97 (221.113.141.97)  2.189 ms  2.074 ms  1.784 ms
 3  118.23.131.25 (118.23.131.25)  2.077 ms  1.702 ms  1.917 ms
 4  118.23.85.145 (118.23.85.145)  5.997 ms  4.298 ms  4.013 ms
 5  221.184.18.85 (221.184.18.85)  2.424 ms  2.065 ms  2.400 ms
 6  211.122.1.89 (211.122.1.89)  2.682 ms  2.305 ms  2.157 ms
 7  180.37.209.70 (180.37.209.70)  3.007 ms  2.701 ms  2.616 ms
 8  ae-1.r20.osakjp01.jp.bb.gin.ntt.net (129.250.12.29)  12.714 ms  12.814 ms  13.768 ms
 9  as-2.r20.snjsca04.us.bb.gin.ntt.net (129.250.2.164)  122.629 ms  122.630 ms  114.925 ms
10  ae-1.r06.snjsca04.us.bb.gin.ntt.net (129.250.5.13)  125.769 ms  125.691 ms  125.404 ms
11  64.208.27.185 (64.208.27.185)  126.514 ms  te3-3-10G.ar3.SJC2.gblx.net (64.215.195.137)  120.751 ms  te2-3-10G.ar3.SJC2.gblx.net (208.178.58.201)  125.972 ms
12  Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246)  120.979 ms  110.237 ms  117.378 ms
13  10gigabitethernet1-2.core1.tyo1.he.net (72.52.92.238)  245.942 ms  238.383 ms  238.643 ms
14  tserv1.tyo1.he.net (74.82.46.6)  248.392 ms  248.764 ms  249.003 ms

[kasperd]

This sounds like something you should open a ticket with ipv6@he.net to get resolved.

[broquea]

Sounds like you should contact your ISP and get them or their upstreams to peer with HE in JPIX or JPNAP.