SixXS::Sunset 2017-06-06

Request another tunnel with a different PoP
[ar] Shadow Hawkins on Friday, 28 September 2012 18:21:31
After successfully setting my connection and have it working (thanks for your help!) I've been checking my traceroute anb latency to my current PoP: Brazil Uberlandia brudi01 <code> root@blue:~# traceroute brudi01.sixxs.net traceroute to brudi01.sixxs.net (201.48.254.14), 30 hops max, 38 byte packets 1 host24.200-3-60.telecom.net.ar (200.3.60.24) 29.152 ms 28.887 ms 29.401 ms 2 host237.200-117-79.telecom.net.ar (200.117.79.237) 36.795 ms 36.411 ms 35.837 ms 3 host161.190-224-165.telecom.net.ar (190.224.165.161) 40.436 ms 44.034 ms 47.803 ms 4 host110.186-153-152.telecom.net.ar (186.153.152.110) 40.131 ms 41.206 ms 56.859 ms 5 195.22.220.109 (195.22.220.109) 44.364 ms 39.199 ms 46.938 ms 6 64.208.27.197 (64.208.27.197) 83.221 ms 61.055 ms 61.332 ms 7 ae0-60G.ar4.GRU1.gblx.net (67.16.148.6) 105.153 ms 104.766 ms ae1-60G.ar4.GRU1.gblx.net (67.16.148.10) 149.159 ms 8 ctbc-telecom.ge-1-3-2.ar4.gru1.gblx.net (207.138.122.50) 204.059 ms ctbc-telecom.ge-1-3-2.ar4.gru1.gblx.net (207.138.122.74) 196.422 ms ctbc-telecom.ge-1-3-2.ar4.gru1.gblx.net (207.138.112.242) 108.658 ms 9 xe-1-2-0-0.core-b.spo511.ctbc.com.br (201.48.46.34) 107.431 ms xe-1-3-1-0.core-b.fac001.ctbc.com.br (201.48.44.237) 193.923 ms xe-1-2-0-0.core-b.spo511.ctbc.com.br (201.48.46.34) 106.669 ms 10 ge-1-3-0-0.edge-b.ula001.ctbc.com.br (200.225.199.166) 201.771 ms ae2-0.core-b.ula001.ctbc.com.br (201.48.44.9) 208.666 ms ae1-0.core-b.ula001.ctbc.com.br (201.48.44.13) 209.184 ms 11 brudi01.sixxs.net (201.48.254.14) 200.647 ms 198.608 ms 198.922 ms root@blue:~# ping brudi01.sixxs.net PING brudi01.sixxs.net (201.48.254.14): 56 data bytes 64 bytes from 201.48.254.14: seq=0 ttl=51 time=200.154 ms 64 bytes from 201.48.254.14: seq=1 ttl=51 time=202.513 ms 64 bytes from 201.48.254.14: seq=2 ttl=51 time=202.090 ms 64 bytes from 201.48.254.14: seq=3 ttl=51 time=202.679 ms 64 bytes from 201.48.254.14: seq=4 ttl=51 time=202.744 ms 64 bytes from 201.48.254.14: seq=5 ttl=51 time=220.214 ms 64 bytes from 201.48.254.14: seq=6 ttl=51 time=202.794 ms 64 bytes from 201.48.254.14: seq=7 ttl=51 time=208.917 ms 64 bytes from 201.48.254.14: seq=8 ttl=51 time=202.708 ms 64 bytes from 201.48.254.14: seq=9 ttl=51 time=202.946 ms 64 bytes from 201.48.254.14: seq=10 ttl=51 time=203.023 ms --- brudi01.sixxs.net ping statistics --- 11 packets transmitted, 11 packets received, 0% packet loss round-trip min/avg/max = 200.154/204.616/220.214 ms </code> I've also tried various different ones and with this particular one, I get this: United States: Miami, Florida usmia0 <code> root@blue:~# traceroute usmia01.sixxs.net traceroute to usmia01.sixxs.net (184.22.119.138), 30 hops max, 38 byte packets 1 host24.200-3-60.telecom.net.ar (200.3.60.24) 29.203 ms 30.686 ms 29.067 ms 2 host233.200-117-79.telecom.net.ar (200.117.79.233) 39.075 ms 38.689 ms 39.446 ms 3 host193.190-225-254.telecom.net.ar (190.225.254.193) 46.108 ms 42.490 ms 46.459 ms 4 host110.190-224-165.telecom.net.ar (190.224.165.110) 38.709 ms 38.590 ms 38.079 ms 5 195.22.220.77 (195.22.220.77) 126.702 ms 117.840 ms 119.389 ms 6 ge6-9.br01.mia02.pccwbtn.net (63.218.113.89) 177.225 ms 165.353 ms 177.918 ms 7 arbinet.ge4-9.br01.mia02.pccwbtn.net (63.218.113.170) 177.652 ms 165.920 ms 177.644 ms 8 ec0-64.1a0201.mifl01.hostnoc.net (64.120.243.130) 246.028 ms 182.165 ms 165.315 ms 9 usmia01.sixxs.net (184.22.119.138) 185.561 ms 173.525 ms 173.511 ms root@blue:~# ping usmia01.sixxs.net PING usmia01.sixxs.net (184.22.119.138): 56 data bytes 64 bytes from 184.22.119.138: seq=0 ttl=49 time=175.148 ms 64 bytes from 184.22.119.138: seq=1 ttl=49 time=174.002 ms 64 bytes from 184.22.119.138: seq=2 ttl=49 time=174.186 ms 64 bytes from 184.22.119.138: seq=3 ttl=49 time=174.488 ms 64 bytes from 184.22.119.138: seq=4 ttl=49 time=174.863 ms 64 bytes from 184.22.119.138: seq=5 ttl=49 time=173.748 ms 64 bytes from 184.22.119.138: seq=6 ttl=49 time=174.074 ms 64 bytes from 184.22.119.138: seq=7 ttl=49 time=175.349 ms 64 bytes from 184.22.119.138: seq=8 ttl=49 time=174.333 ms 64 bytes from 184.22.119.138: seq=9 ttl=49 time=174.701 ms 64 bytes from 184.22.119.138: seq=10 ttl=49 time=174.238 ms --- usmia01.sixxs.net ping statistics --- 11 packets transmitted, 11 packets received, 0% packet loss round-trip min/avg/max = 173.748/174.466/175.349 ms </code> So, I know it's not possible to change PoPs, but is it worth requesting another tunnel or the difference in latency and hops is not really that big to make a change? Thanks, Pablo

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker