Anyone noticed how the pings/traceroute/hop for cogent is faster then other premium providers? I'm using Telstras traceroute util at http://www.telstra.net/cgi-bin/trace . Only thing that comes close is staminus.net

The server below is located in Walnut Creek, CA 94596 US.
traceroute to atrivo.com (66.28.38.228), 30 hops max, 40 byte packets
1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.442 ms 0.337 ms 0.388 ms
2 GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.371 ms 0.366 ms 0.408 ms
3 GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126) 0.555 ms 0.56 ms 0.581 ms
4 Pos4-1.ken-core4.Sydney.telstra.net (203.50.6.69) 4.161 ms 3.96 ms 3.901 ms
5 Pos2-0.pad-core4.Sydney.telstra.net (203.50.6.22) 3.996 ms 3.945 ms 4.027 ms
6 GigabitEthernet0-1.syd-core01.Sydney.net.reach.com (203.50.13.246) 4.158 ms 4.047 ms 3.976 ms
7 202.84.143.21 (202.84.143.21) 191.134 ms 191.195 ms 191.256 ms
8 i-13-0.paix-core01.PaloAlto.net.reach.com (202.84.251.49) 174.803 ms 174.646 ms 174.599 ms
9 ge4-0.mpr2.pao1.us.mfnx.net (198.32.176.11) 174.823 ms 174.703 ms 174.933 ms
10 64.124.11.181.cogentco.com (64.124.11.181) 184.543 ms 184.833 ms 185.378 ms
11 p6-0.core01.sfo01.atlas.cogentco.com (66.28.4.145) 184.861 ms 185.248 ms 184.89 ms
12 g49.ba01.b003070-2.sfo01.atlas.cogentco.com (66.28.66.138) 186.037 ms 185.338 ms 185.388 ms
13 66.28.38.228 (66.28.38.228) 178.489 ms 179.334 ms 178.323 ms


traceroute to verio.com (204.0.52.20), 30 hops max, 40 byte packets
1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.426 ms 0.384 ms 0.428 ms
2 GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.573 ms 0.434 ms 0.432 ms
3 GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126) 0.699 ms 0.528 ms 0.461 ms
4 Pos4-1.ken-core4.Sydney.telstra.net (203.50.6.69) 4.113 ms 3.945 ms 3.856 ms
5 Pos2-0.pad-core4.Sydney.telstra.net (203.50.6.22) 4.157 ms 4.025 ms 3.985 ms
6 GigabitEthernet0-0.syd-core01.Sydney.net.reach.com (203.50.13.242) 4.146 ms 4.128 ms 4.179 ms
7 202.84.143.5 (202.84.143.5) 191.301 ms 191.306 ms 191.27 ms
8 i-13-0.paix-core01.PaloAlto.net.reach.com (202.84.251.49) 174.724 ms 174.701 ms 174.713 ms
9 f0.pao1.verio.net (198.32.176.14) 175.052 ms 175.429 ms 175.233 ms
10 ge-6-1-0.r06.plalca01.us.bb.verio.net (129.250.3.53) 174.937 ms 175.949 ms 175.053 ms
11 p16-1-1-0.r20.plalca01.us.bb.verio.net (129.250.3.80) 175.435 ms 175.142 ms 175.29 ms
12 p16-1-1-1.r20.dllstx01.us.bb.verio.net (129.250.4.104) 276.435 ms 276.812 ms 276.37 ms
13 p16-0-0-0.r02.dllstx01.us.bb.verio.net (129.250.3.23) 276.257 ms 276.41 ms 276.67 ms
14 ge-2-0-0.a10.dllstx01.us.ra.verio.net (129.250.31.58) 278.768 ms 276.526 ms 276.038 ms
15 * * *
~
30 * * *


traceroute to ftp.uu.net (192.48.96.9), 30 hops max, 40 byte packets
1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.408 ms 0.383 ms 0.39 ms
2 GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.714 ms 0.391 ms 0.375 ms
3 GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126) 0.56 ms 0.568 ms 0.565 ms
4 Pos4-0.ken-core4.Sydney.telstra.net (203.50.6.121) 4.026 ms 3.852 ms 3.872 ms
5 Pos2-0.pad-core4.Sydney.telstra.net (203.50.6.22) 3.999 ms 4.019 ms 4.035 ms
6 GigabitEthernet0-0.syd-core01.Sydney.net.reach.com (203.50.13.242) 4.204 ms 4.142 ms 4.035 ms
7 202.84.143.134 (202.84.143.134) 4.205 ms 4.285 ms 4.182 ms
8 i-9-0.wil-core02.net.reach.com (202.84.249.217) 153.592 ms 153.238 ms 153.205 ms
9 p7-0.lsanca2-cr2.bbnplanet.net (4.25.112.29) 153.923 ms 153.351 ms 153.294 ms
10 POS4-0.BR1.LAX9.ALTER.NET (204.255.169.117) 162.158 ms 161.608 ms 161.7 ms
11 0.so-0-1-0.XL1.LAX9.ALTER.NET (152.63.113.10) 163.023 ms 161.704 ms 161.676 ms
12 0.so-1-0-0.TL1.LAX9.ALTER.NET (152.63.115.142) 161.771 ms 161.772 ms 161.811 ms
13 0.so-6-0-0.TL1.DCA8.ALTER.NET (152.63.3.198) 231.15 ms 231.172 ms 231.117 ms
14 0.so-5-0-0.XL1.DCA8.ALTER.NET (152.63.25.38) 230.945 ms 230.923 ms 230.965 ms
15 289.at-1-0-0.CL1.IAD5.ALTER.NET (152.63.34.246) 232.08 ms 232.158 ms 231.962 ms
16 500.ATM6-0.GW3.IAD5.ALTER.NET (152.63.38.5) 232.043 ms 231.942 ms 232.245 ms
17 pos5-0.soesr1.ash.ops.us.uu.net (207.18.173.162) 232.748 ms 233.183 ms 232.897 ms
18 gig1-0.esr-b-10-9-1.ash.ops.us.uu.net (198.5.240.35) 232.071 ms 232.694 ms 233.072 ms
19 neo-ftp.uu.net (198.5.241.101) 232.736 ms 232.998 ms 232.872 ms


traceroute to www.staminus.net (65.215.220.10), 30 hops max, 40 byte packets
1 fastethernet9-0-0.bdr2.syd.connect.com.au (192.189.54.55) 1.237 ms 1.671 ms 1.922 ms
2 g2-0-2.sybr3.global-gateway.net.nz (202.50.119.97) 2.161 ms 1.304 ms 1.385 ms
3 p4-4.pabr2.global-gateway.net.nz (202.50.116.194) 158.572 ms 158.22 ms 158.51 ms
4 g0-0-0-0.pabr3.global-gateway.net.nz (202.50.245.24) 167.484 ms 168.185 ms 167.503 ms
5 sl-st20-pa-6-3.sprintlink.net (144.223.243.17) 159.144 ms 158.164 ms 158.646 ms
6 sl-bb20-sj-8-3.sprintlink.net (144.232.20.43) 159.91 ms 159.763 ms 159.148 ms
7 sl-gw8-sj-9-0.sprintlink.net (144.232.3.110) 158.917 ms 159.139 ms 158.534 ms
8 sl-savvisnet-2-0.sprintlink.net (144.228.44.70) 160.368 ms 160.682 ms 159.855 ms
9 so-2-0-0.0.ussfnc2-j20c-1.savvis.net (64.242.22.81) 168.994 ms 169.506 ms 169.642 ms
10 216.88.159.186 (216.88.159.186) 184.656 ms 184.792 ms 178.532 ms
11 core01.irv.staminus.net (65.215.220.2) 171.913 ms 172.12 ms 171.582 ms
12 web1.staminus.net (65.215.220.10) 179.113 ms 178.89 ms 178.419 ms

Originally posted by VS-Lap
Anyone noticed

Yep, and we use that same point for regular checks. Staminus fluctuates, and can sometimes be much better.

Regards

Gary

To our new server @ fastservers:

traceroute to 216.218.202.96 (216.218.202.96), 30 hops max, 40 byte packets
1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.43 ms 0.376 ms 0.323 ms
2 GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.657 ms 0.299 ms 0.295 ms
3 GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126) 0.761 ms 0.565 ms 0.453 ms
4 Pos4-1.ken-core4.Sydney.telstra.net (203.50.6.69) 4.044 ms 3.873 ms 3.896 ms
5 Pos2-0.pad-core4.Sydney.telstra.net (203.50.6.22) 4.046 ms 3.916 ms 4.014 ms
6 GigabitEthernet0-0.syd-core01.Sydney.net.reach.com (203.50.13.242) 4.068 ms 3.937 ms 3.931 ms
7 202.84.143.41 (202.84.143.41) 191.296 ms 191.181 ms 191.273 ms
8 i-13-0.paix-core01.PaloAlto.net.reach.com (202.84.251.49) 174.902 ms 174.869 ms 174.943 ms
9 paix.he.net (198.32.176.20) 175.087 ms 174.806 ms 174.906 ms
10 gige-g1-0.gsr12008.fmt.he.net (64.71.128.177) 175.906 ms 175.767 ms 175.927 ms
11 64.71.131.174 (64.71.131.174) 177.771 ms 176.993 ms 178.253 ms
12 216.218.202.96 (216.218.202.96) 178.175 ms 177.493 ms 177.077 ms


:D

/me grins at fastservers

Hello,
When running comparisson-check traceroutes, make sure to trace remote hosts near eachother for accurate results. If you're looking to compare accurately, compare the following hops together:

11 p6-0.core01.sfo01.atlas.cogentco.com (66.28.4.145) 184.861 ms 185.248 ms 184.89 ms
9 f0.pao1.verio.net (198.32.176.14) 175.052 ms 175.429 ms 175.233 ms
10 POS4-0.BR1.LAX9.ALTER.NET (204.255.169.117) 162.158 ms 161.608 ms 161.7 ms
5 sl-st20-pa-6-3.sprintlink.net (144.223.243.17) 159.144 ms 158.164 ms 158.646 ms

In each case, I took the router hop immediately after the peering point. Unfortunately UUnet did not peer near the SJC/SF/PA area so I had to use an LA comparisson which is roughly 10 ms away. In all these situations, you notice a clear difference between Cogent and various premium providers.

Telstra used to run directly into UUnet with UUnet running a trans-pacific cable from Australia to LA. Staminus used to achieve ping as low as 150 ms. Since then, the network structure has changed on Telstra's side thus using alternate, slower providers to carry the traffic.

Hi matt! yeah your right about that host accuracy!

I did a boo boo. I used the connect.com.au's traceroute instead of telstra's as I used with the others.

traceroute to 65.215.220.10 (65.215.220.10), 30 hops max, 40 byte packets
1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.479 ms 0.326 ms 0.315 ms
2 GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.378 ms 0.259 ms 0.288 ms
3 GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126) 0.591 ms 0.481 ms 0.573 ms
4 Pos4-1.ken-core4.Sydney.telstra.net (203.50.6.69) 3.88 ms 3.877 ms 3.887 ms
5 Pos2-0.pad-core4.Sydney.telstra.net (203.50.6.22) 4.231 ms 3.987 ms 4.019 ms
6 GigabitEthernet0-1.syd-core01.Sydney.net.reach.com (203.50.13.246) 4.03 ms 4.027 ms 4.052 ms
7 202.84.143.134 (202.84.143.134) 4.243 ms 4.237 ms 4.215 ms
8 i-9-0.wil-core02.net.reach.com (202.84.249.217) 153.147 ms 153.018 ms 153.12 ms
9 p7-0.lsanca2-cr2.bbnplanet.net (4.25.112.29) 153.248 ms 153.202 ms 153.027 ms
10 POS4-0.BR1.LAX9.ALTER.NET (204.255.169.117) 161.446 ms 161.863 ms 161.519 ms
11 0.so-0-1-0.XL1.LAX9.ALTER.NET (152.63.113.10) 161.668 ms 161.862 ms 161.8 ms
12 0.so-3-0-0.XR1.LAX9.ALTER.NET (152.63.115.157) 161.726 ms 161.722 ms 161.505 ms
13 191.ATM6-0.GW1.LAX9.ALTER.NET (152.63.113.25) 161.653 ms 161.706 ms 161.989 ms
14 Staminus-gw.customer.ALTER.NET (157.130.225.166) 202.786 ms 174.18 ms 166.117 ms
15 core01.irv.staminus.net (65.215.220.2) 201.944 ms 202.088 ms 201.978 ms
16 web1.staminus.net (65.215.220.10) 168.372 ms 161.878 ms 168.224 ms

Cogent isnt always super fast...especially thru telstra...

Optus routes faster to DV2 than telstra does unyet they both route thru cogent...

and i have noticed lately that pings to cogent have actually gotten slower:( and slower :(