Wanted- someone on aol to do a cogent/verio test
 

Over the last week, I have heard all sorts of horror stories about Cogent and AOL. Well frankly, this has me a little worried, since I do have a couple of dedicated boxes on Cogent.

What I'm looking for is someone on the board that is on AOL to do a connect and download test to 2 of my servers. One of the test servers is on Cogent, the other is on Verio...they are both in the same city in California, and both have a load of approx 7mbps sustained.

Any takers?

Post a url and it will get done.:)

It's not just AOL. Cogent sites are slow right now for me and I'm not on AOL right now.

Post a URL and I'll see if I can do a test for you too.

Willing here as well, I have an aol account and a non aol account.

we just scrapped the cogent and sales immediately went up 30%, go figure.

Thanks for the offers. I am uploading a page to the 2 test servers right now, and will post the URL's shortly.

Here's the Cogent URL:

http://209.126.184.9/cogent-test.html

Please post your AOL tracerts

I'm not on AOL right now and your cogent trace looks fine from here for some reason. When I did a trace on Shempland (also Cogent) earlier, it was horrible.

Here is the end of your trace from where I am:

#11 p13-0.core02.sfo01.atlas.cogentco.com (66.28.28.57): TTL Exceeded, ttl=246, 30 ms
#12 p15-0.core01.sfo01.atlas.cogentco.com (66.28.4.69): TTL Exceeded, ttl=245, 21 ms
#13 p4-0.core01.sjc01.atlas.cogentco.com (66.28.4.94): TTL Exceeded, ttl=244, 30 ms
#14 p13-0.core01.lax01.atlas.cogentco.com (66.28.4.73): TTL Exceeded, ttl=243, 30 ms
#15 p5-0.core01.san01.atlas.cogentco.com (66.28.4.78): TTL Exceeded, ttl=242, 30 ms
#16 g7.ba21.b006588-1.san01.atlas.cogentco.com (66.28.66.106): TTL Exceeded, ttl=241, 30 ms
#17 ge1-2.gw65-02.kmc01.sdcix.net (66.28.28.126): TTL Exceeded, ttl=240, 40 ms
#18 Unavailable (209.126.184.9): Echo Reply, ttl=239, 40 ms

Here is the end of Shempland's trace:

#11 p13-0.core02.sfo01.atlas.cogentco.com (66.28.28.57): TTL Exceeded, ttl=246, 30 ms
#12 p15-0.core01.sfo01.atlas.cogentco.com (66.28.4.69): TTL Exceeded, ttl=245, 20 ms
#13 p4-0.core01.sjc01.atlas.cogentco.com (66.28.4.94): TTL Exceeded, ttl=244, 30 ms
#14 p13-0.core01.lax01.atlas.cogentco.com (66.28.4.73): TTL Exceeded, ttl=243, 40 ms
#15 p5-0.core01.san01.atlas.cogentco.com (66.28.4.78): TTL Exceeded, ttl=242, 40 ms
#16 p6-0.core01.iah01.atlas.cogentco.com (66.28.4.5): TTL Exceeded, ttl=241, 70 ms
#17 p15-0.core01.tpa01.atlas.cogentco.com (66.28.4.46): TTL Exceeded, ttl=241, 3045 ms
#18 g50.ba01.b001841-0.tpa01.atlas.cogentco.com (66.28.66.94): TTL Exceeded, ttl=240, 3114 ms
#19 Sago_Networks-4.demarc.cogentco.com (66.250.6.82): TTL Exceeded, ttl=239, 3075 ms
#20 gi-2-0-0.cr-1.core.tpa.sagonet.net (66.118.132.2): TTL Exceeded, ttl=238, 3064 ms
#21 gi-1-2.csw-1.core.tpa.sagonet.net (66.118.132.26): TTL Exceeded, ttl=237, 3085 ms
#22 Unavailable (66.118.160.3): Echo Reply, ttl=45, 3114 ms

Here is another cogent site, FreakyDink.com

#11 p13-0.core02.sfo01.atlas.cogentco.com (66.28.28.57): TTL Exceeded, ttl=246, 20 ms
#12 p15-0.core01.sfo01.atlas.cogentco.com (66.28.4.69): TTL Exceeded, ttl=245, 20 ms
#13 p4-0.core01.sjc01.atlas.cogentco.com (66.28.4.94): TTL Exceeded, ttl=244, 30 ms
#14 p13-0.core01.lax01.atlas.cogentco.com (66.28.4.73): TTL Exceeded, ttl=243, 30 ms
#15 p5-0.core01.san01.atlas.cogentco.com (66.28.4.78): TTL Exceeded, ttl=242, 30 ms
#16 p6-0.core01.iah01.atlas.cogentco.com (66.28.4.5): TTL Exceeded, ttl=241, 70 ms
#17 p15-0.core01.tpa01.atlas.cogentco.com (66.28.4.46): TTL Exceeded, ttl=241, 3095 ms
#18 p5-0.core01.mia01.atlas.cogentco.com (66.28.4.57): TTL Exceeded, ttl=242, 3104 ms
#19 g0-2.na01.b006097-0.mia01.atlas.cogentco.com (66.250.11.22): TTL Exceeded, ttl=241, 3075 ms
#20 NetFree.demarc.cogentco.com (38.112.0.170): TTL Exceeded, ttl=240, 3004 ms
#21 freakydink.com (64.83.108.121): Echo Reply, ttl=239, 3054 ms

So it's not all cogent sites that are slow for me, I guess.

Thanks...anyone else available to run a tracert? Still interested in AOL results...

Man, those are horrible traces:1orglaugh If your using cogent, like cherrylula posted above, your now losing money:(

from comcast.net its unreachable.

I'm on Road Runner and it is extremely slow loading. If I was a potential member, I would move on to a faster site because it just is not fun waiting for every little picture to load.

Seems that alot of people on roadrunner are havin probs with anything cogent...but, that may have to do with the fact that Roadrunner is owned by Time-Warner, as is AOL.
http://www.roadrunner.net/rdrun/

{shrugs} that's just an educated guess, though.

When I did a trace, my times werent all too bad, and just over 10 hops. I'm in SoCal, and for some reason this thing with cogent doesnt seem to be affecting us too much...well, at least not those of us on pacbell dsl...ok well, maybe just me, hehe!

I'm guessin' you must be hosted by 2 different companies..say, phatservers.net and cologroup.com (or should that be phatservers.com, instead of cologroup?) funny thing, when typed into the address bar, phatservers.com redirects to .net...but when ya trace it, it ends up at cologroup.

{shrugs} go figure...

AOL is basically re-routing most of their RoadRunner traffic through LEVEL3. LEVEL3 is completely saturated now. Not sure if you have read any of the other posts, but basically AOL has disconnected it's peer to Cogent.

yep...I've read about it. thats why I suggested the possibility. anything and everything that has to do with aol/time-warner will be rerouted...sux for those on cogent, but maybe some useful knowledge will come of it, and hopefully, they put that knowledge to good use.

{shrugs} just my :2 cents:

I'm on aol dial-up and this is what I get

Input Query: 209.126.184.9/cogent-test.html

Started at: 01:25:32
Stopped at: 01:25:32


--------------------------------------------------------------------------------

Unable to resolve target system name 209.126.184.9/cogent-test.html.


Does it matter which tracert I use? If I'm from the U.S is it ok if I use the ones in other countries like Argentine or whatever???

Oops, it worked now

Tracing route to 209.126.184.9 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms rt1.altair7.com [209.11.155.129]
2 <10 ms 16 ms 16 ms 209.10.41.130
3 <10 ms 15 ms 16 ms ge-6-1-0.core1.sjc1.globix.net [209.10.2.193]
4 <10 ms 16 ms 16 ms so-4-2-0.core1.sjc4.globix.net [209.10.11.221]
5 62 ms 63 ms 62 ms so-1-0-0.core2.cgx2.globix.net [209.10.10.150]
6 46 ms 63 ms 62 ms so-0-0-0.core1.cgx2.globix.net [209.10.10.157]
7 62 ms 63 ms 62 ms pos1-0-peer1.cgx3.globix.net [209.10.12.82]
8 63 ms 62 ms 63 ms p11-4.pr01.ord03.atlas.psi.net [154.54.10.133]
9 62 ms 63 ms 62 ms p12-0.core01.ord01.atlas.cogentco.com [154.54.2.237]
10 62 ms 63 ms 62 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62]
11 63 ms 78 ms 78 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33]
12 78 ms 79 ms 93 ms p5-0.core02.dfw01.atlas.cogentco.com [66.28.4.37]
13 78 ms 78 ms 94 ms p15-0.core01.dfw01.atlas.cogentco.com [66.28.4.25]
14 78 ms 94 ms 78 ms p13-0.core01.iah01.atlas.cogentco.com [66.28.4.98]
15 109 ms 125 ms 110 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6]
16 109 ms 125 ms 109 ms g8.ba21.b006588-1.san01.atlas.cogentco.com [66.28.66.110]
17 109 ms 125 ms 125 ms ge1-2.gw65-02.kmc01.sdcix.net [66.28.28.126]
18 109 ms 125 ms 110 ms 209.126.184.9

Trace complete.


Is that good or bad?