Hmmmmm, supposedly my servers are in san francisco, hwoever i just did a neotrace and it ends up in new jersey everytime.

ServerIp: 66.28.45.97

Does anyone else have a cogent server in sort of sanfrancisco area, if so whats the ip???

Also can people please tracert the above ip and tell me where the server is?

Kind regards,

Thanks in advance!

Matt Brocklehurst

I just did a trace and it's in SF.



11 mae-west-atm-gtei.netrail.net (4.24.145.38) 34.054 ms 33.117 ms 33.848 ms12 GigE2-1.tr1.SanFrancisco1.CA.us.netrail.net (205.215.12.1) 35.325 ms 37.986 ms 34.044 ms
13 p13-0.core02.sfo01.atlas.cogentco.com (66.28.28.57) 34.322 ms 32.612 ms 34.852 ms
14 g50.ba01.b003070-1.sfo01.atlas.cogentco.com (66.28.5.182) 34.390 ms 31.951 ms 34.816 ms
15 66.28.45.97 (66.28.45.97) 33.946 ms 40.268 ms 35.927 ms

Looks like there is a problem.
Trace from San Francisco:
[root admin]# /usr/sbin/traceroute 66.28.45.97
traceroute to 66.28.45.97 (66.28.45.97), 30 hops max, 38 byte packets
1 64.157.93.1 (64.157.93.1) 0.874 ms 0.685 ms 0.636 ms
2 65.56.42.254 (65.56.42.254) 0.479 ms 0.345 ms 0.284 ms
3 f5.ba01.b003070-2.sfo01.atlas.cogentco.com (66.28.28.81) 3.474 ms 2.269 ms 2.457 ms
4 g1-4.core02.sfo01.atlas.cogentco.com (66.28.66.141) 2.929 ms 2.664 ms 2.152 ms
5 g50.ba01.b003070-1.sfo01.atlas.cogentco.com (66.28.5.182) 3.313 ms 2.704 ms 2.341 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
Aborted


Traceroute from Miami:

traceroute to 66.28.45.97 (66.28.45.97), 30 hops max, 38 byte packets
1 * 66.232.6.129 (66.232.6.129) 3.058 ms 1.720 ms
2 66.232.5.5 (66.232.5.5) 1.983 ms 0.241 ms 0.208 ms
3 66.28.76.17 (66.28.76.17) 0.426 ms 0.363 ms 0.321 ms
4 miamfllr1m6-ge-0-0-0-109.ip.epik.net (216.22.64.61) 0.975 ms 0.804 ms 0.796 ms
5 miamfllr2m6-so-6-0-0.ip.epik.net (216.22.67.226) 1.002 ms 0.795 ms 0.798 ms
6 tamsflde1m6-so-3-0-0.ip.epik.net (216.22.67.221) 5.739 ms 5.563 ms 5.761 ms
7 tamsflde2m6-so-6-0-0.ip.epik.net (216.22.67.218) 5.756 ms 5.626 ms 5.586 ms
8 gige8-0-514.hsipaccess2.Tampa1.Level3.net (63.208.0.13) 5.991 ms 5.817 ms 5.883 ms
9 ge-6-0-1.mp2.Tampa1.Level3.net (209.247.11.221) 6.458 ms 6.292 ms 6.263 ms
10 so-2-0-0.mp1.SanJose1.Level3.net (209.247.9.114) 70.334 ms 70.216 ms 70.179 ms
11 gigabitethernet4-2.core1.SanJose1.Level3.net (64.159.2.133) 70.588 ms 70.365 ms 70.354 ms
12 so-2-1-3.pr1.SanFrancisco1.CA.us.netrail.net (205.215.1.229) 71.047 ms 70.928 ms 70.836 ms
13 GigE2-1.tr1.SanFrancisco1.CA.us.netrail.net (205.215.12.1) 71.046 ms 70.926 ms 70.860 ms
14 p13-0.core02.sfo01.atlas.cogentco.com (66.28.28.57) 71.118 ms 70.934 ms 71.312 ms
15 g50.ba01.b003070-1.sfo01.atlas.cogentco.com (66.28.5.182) 73.698 ms 71.447 ms 71.442 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * *
Aborted


From Denver:
traceroute to 66.28.45.97 (66.28.45.97), 30 hops max, 38 byte packets
1 brdr1.co.vianetsol.com (66.28.31.226) 0.535 ms 0.140 ms 0.460 ms
2 f25.ba01.b006467-1.den01.atlas.cogentco.com (66.28.31.225) 1.153 ms 0.555 ms 0.600 ms
3 g9-2.core01.den01.atlas.cogentco.com (66.28.5.21) 0.970 ms 0.385 ms 0.361 ms
4 p4-0.core02.sfo01.atlas.cogentco.com (66.28.4.130) 24.582 ms 24.219 ms 24.486 ms
5 g50.ba01.b003070-1.sfo01.atlas.cogentco.com (66.28.5.182) 24.931 ms 24.554 ms 24.496 ms
6 66.28.45.97 (66.28.45.97) 24.827 ms 24.827 ms 25.000 ms

Looks like your server is in SF but there are some major problems to trace from other Networks.

Thanks guys, owe ya a few beers :D

Hmmmm @ problems

COgent keeps their stuff on their internal network for as long as possible, so sometimes you may see that while it could make it there in a couple of hops they may hop back and forth between a few different citys to arrive at your destination. This is the inherit problem with cogent, but they couldnt stay in business if all the traffic left their network.

Originally posted by cbaker17
COgent keeps their stuff on their internal network for as long as possible, so sometimes you may see that while it could make it there in a couple of hops they may hop back and forth between a few different citys to arrive at your destination. This is the inherit problem with cogent, but they couldnt stay in business if all the traffic left their network.

You ain't joking. Our tech office is 20 minutes from our Cogent colos in San Diego. Just to get to our servers we go to TX - FL - DC- NY - then back.

Just recentally (like a few days ago), we were finally able to just run up the coast to SJ and back down on Cogent. Big improvement.

Are any of you noticing some router issues in SF

Specifically

205.215.12.1 is showing >150 MS

Run a tracert to 66.228.205.41 there appears to be some issues with a netrail router. Anyone else on the west coast seeing this?

Originally posted by JamieT
Are any of you noticing some router issues in SF

Specifically

205.215.12.1 is showing >150 MS

Run a tracert to 66.228.205.41 there appears to be some issues with a netrail router. Anyone else on the west coast seeing this?

There is always problems with the netrail hops, they are congested.

Originally posted by UmBillyCord


You ain't joking. Our tech office is 20 minutes from our Cogent colos in San Diego. Just to get to our servers we go to TX - FL - DC- NY - then back.

Just recentally (like a few days ago), we were finally able to just run up the coast to SJ and back down on Cogent. Big improvement.

Yeah thats a big welcome improvment for anyone located in san diego.

Yeah thats a big welcome improvment for anyone located in san diego.

Did you notice this change too? You are just a little more north.

Also, did you see the new pipe SDColo brought in?

Verio sure does have a lot of routers...

I'm seeing a Verio connection via ATT:

[root@io www.thefishinyourear.com]# /usr/sbin/traceroute www.sdcolo.com
traceroute: Warning: www.sdcolo.com has multiple addresses; using 216.98.128.23
traceroute to www.sdcolo.com (216.98.128.23), 30 hops max, 38 byte packets
1 66.179.15.2 (66.179.15.2) 0.416 ms 0.330 ms 0.310 ms
2 66.179.12.1 (66.179.12.1) 0.403 ms 0.349 ms 0.328 ms
3 12.124.58.17 (12.124.58.17) 0.837 ms 0.829 ms 0.793 ms
4 gbr5-p80.attga.ip.att.net (12.123.21.74) 0.888 ms 1.003 ms 0.813 ms
5 gbr4-p100.attga.ip.att.net (12.122.5.42) 0.951 ms 0.838 ms 0.880 ms
6 gbr4-p10.wswdc.ip.att.net (12.122.2.162) 14.356 ms 14.314 ms 14.263 ms
7 ggr1-p370.wswdc.ip.att.net (12.123.9.53) 14.455 ms 14.376 ms 14.346 ms
8 att-gw.dc.verio.net (192.205.32.210) 17.131 ms 17.193 ms 17.173 ms
9 p4-3-0.r00.asbnva01.us.bb.verio.net (129.250.4.225) 17.106 ms 17.061 ms 17.024 ms
10 p4-4-2-0.r01.mclnva02.us.bb.verio.net (129.250.4.221) 17.770 ms 18.031 ms 17.798 ms
11 p16-0-0-0.r00.atlnga03.us.bb.verio.net (129.250.2.49) 36.229 ms 36.362 ms 36.749 ms
12 p16-5-0-0.r01.atlnga03.us.bb.verio.net (129.250.5.246) 36.686 ms 36.191 ms 36.566 ms
13 p4-1-3-0.r00.hstntx01.us.bb.verio.net (129.250.2.45) 37.075 ms 37.153 ms 37.222 ms
14 p4-6-0.r01.hstntx01.us.bb.verio.net (129.250.2.158) 37.034 ms 37.113 ms 37.140 ms
15 p4-1-0.r00.sndgca01.us.bb.verio.net (129.250.3.186) 69.311 ms 69.347 ms 69.376 ms
16 ge-0-0-0.a05.sndgca01.us.ra.verio.net (129.250.27.86) 69.519 ms 69.509 ms 69.499 ms
17 p1-0-3-0.a05.sndgca01.us.ce.verio.net (207.67.238.114) 70.347 ms 70.228 ms 70.307 ms
18 ge5-8.gw65-01.kmc01.sdcix.net (209.126.155.49) 69.740 ms 69.596 ms 69.945 ms
19 www2.sdcolo.com (216.98.128.23) 70.135 ms 69.664 ms 69.673 ms

traceroute to 66.28.45.97 (66.28.45.97), 32 hops max, 38 byte packets
1 g4-1-0-3.c7513.science.belnet.net (193.190.199.69) 1.014 ms
2 g1-1.c12410.science.belnet.net (193.191.254.9) 0.476 ms
3 g6-0.c12008.brussels.belnet.net (193.190.197.181) 0.380 ms
4 P10-0.BRUBB1.Brussels.opentransit.net (193.251.251.53) 0.561 ms
5 P0-0.LONBB2.London.opentransit.net (193.251.154.229) 6.141 ms
6 P6-0.LONBB1.London.opentransit.net (193.251.154.237) 6.108 ms
7 abovenet-francetel.above.net (193.251.154.66) 74.831 ms
8 core1-core2-oc48.lhr1.above.net (208.185.156.13) 75.038 ms
9 lga1-lhr1-stm4-2.lga1.above.net (216.200.254.77) 75.445 ms
10 core1-lga1-oc192.lga2.above.net (208.185.0.246) 75.205 ms
11 core1-lga2-oc48.lga4.above.net (64.124.232.6) 74.899 ms
12 64.124.51.186.cogentco.com (64.124.51.186) 91.470 ms
13 p4-0.core02.dca01.atlas.cogentco.com (66.28.4.81) 91.760 ms
14 p14-0.core01.atl01.atlas.cogentco.com (66.28.4.125) 92.117 ms
15 p15-0.core01.jax01.atlas.cogentco.com (66.28.4.137) 98.099 ms
16 p14-0.core01.tpa01.atlas.cogentco.com (66.28.4.141) 102.911 ms
17 p5-0.core01.iah01.atlas.cogentco.com (66.28.4.45) 122.887 ms
18 p14-0.core01.san01.atlas.cogentco.com (66.28.4.6) 164.118 ms
19 p4-0.core01.lax01.atlas.cogentco.com (66.28.4.77) 155.843 ms
20 p14-0.core01.sjc01.atlas.cogentco.com (66.28.4.74) 166.997 ms
21 p4-0.core01.sfo01.atlas.cogentco.com (66.28.4.93) 168.172 ms
22 g49.ba01.b003070-1.sfo01.atlas.cogentco.com (66.28.5.178) 168.827 ms
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *
31 *
32 *

Traceroute from Belgium. :) Dunno if you needed that one anyways... :D

traceroute to 66.28.45.97 (66.28.45.97), 30 hops max, 38 byte packets
1 router.linuxwebnet.com (208.231.31.1) 0.425 ms 0.371 ms 0.318 ms
2 sky6509rtr1-vlan2.skynetweb.com (64.23.0.251) 0.706 ms 0.589 ms 0.624 ms
3 core1a.balt.skynetweb.com (208.231.4.2) 1.037 ms 15.739 ms 2.191 ms
4 Serial5-1-0.GW1.DCA3.ALTER.NET (157.130.37.157) 1.424 ms 2.562 ms 1.702 ms
5 555.at-1-1-0.XL2.DCA8.ALTER.NET (152.63.37.162) 4.769 ms 3.771 ms 2.282 ms
6 188.at-4-0-0.XR2.DCA1.ALTER.NET (146.188.163.17) 3.262 ms 2.667 ms 2.391 ms
7 194.ATM6-0.BR2.DCA1.ALTER.NET (152.63.36.89) 2.846 ms 3.161 ms 4.135 ms
8 t3-0-0-0.pr1.Washington1.DC.us.netrail.net (205.215.1.13) 44.378 ms 57.273 ms 58.002 ms
9 pos-6-0.pr1.Washington1.DC.netrail.net (205.215.61.14) 102.082 ms 108.366 ms 110.600 ms
10 g14-1.core01.dca01.atlas.cogentco.com (66.28.28.173) 11.055 ms 12.641 ms 11.911 ms
11 p15-0.core02.dca01.atlas.cogentco.com (66.28.4.22) 8.658 ms 15.533 ms 15.292 ms
12 p14-0.core01.atl01.atlas.cogentco.com (66.28.4.125) 24.878 ms 28.297 ms 26.849 ms
13 p15-0.core01.jax01.atlas.cogentco.com (66.28.4.137) 36.100 ms 26.049 ms 29.101 ms
14 p14-0.core01.tpa01.atlas.cogentco.com (66.28.4.141) 29.560 ms 31.005 ms 33.080 ms
15 p5-0.core01.iah01.atlas.cogentco.com (66.28.4.45) 51.428 ms 56.158 ms 53.318 ms
16 p14-0.core01.san01.atlas.cogentco.com (66.28.4.6) 82.842 ms 76.422 ms 81.057 ms
17 p4-0.core01.lax01.atlas.cogentco.com (66.28.4.77) 83.869 ms 98.731 ms 103.912 ms
18 p14-0.core01.sjc01.atlas.cogentco.com (66.28.4.74) 95.679 ms 103.626 ms 110.446 ms
19 p4-0.core01.sfo01.atlas.cogentco.com (66.28.4.93) 111.290 ms 98.781 ms 107.049 ms
20 g49.ba01.b003070-1.sfo01.atlas.cogentco.com (66.28.5.178) 96.684 ms 84.229 ms 82.803 ms
21 * * *

What do you all think about Cogent? Just a cheep way to provide lots of bandwidth?

Originally posted by MattS
What do you all think about Cogent? Just a cheep way to provide lots of bandwidth?

This has been discussed at length in the past. People either love it, or they hate it.

Well to be honest I nearly had a heart attack, I read some cogent slamming post on WHT and i did a tracert and sure enough my server was on cogent

But they do actually seem quite cool, you do get the odd quirk here and there though, such as someone in Austin, Texas can access the site, but not in Dallas, Texas, but I suppose all cable providers get quirks such as the one listed.

So all in all I give cogent a high rating, the latentcy is like 350ms from the UK, and ICMP packets report (hehehehe if you dont know ping uses icmp - i thought id try and sound techy!!) that other servers on the same coast get about the same, from other providers to my server i get about 40ms-80ms which again isnt that bad.

Just my two cents!!!!!

Matthew Brocklehurst,
TerraStudios