http://biz.yahoo.com/djus/020821/0945000378_1.html

I guess that means they aren't fartin around over there :D

Say hello to profitability, Cogentco!

Ugh, more debt for Cogent. How are they going to survive? They are already having problems getting customers in a lot of the buildings they have already lit.

Should be interesting to see what will happen!

Rackmy, have you seen their last quarter's results? Because, according to them they really don't have problems getting customers...

I have faith in cognet... don't know why others don't. :) I doubt they would want to be the next WorldCom, and everybody wants cheap bandwidth. I have a feeling they are in this for a longterm goal... Go Cognet :)

Originally posted by Gernot
Rackmy, have you seen their last quarter's results? Because, according to them they really don't have problems getting customers...

You said the same in a past thread, can you please post a link to their last quarter's results?

Sure, here you go (http://www.sec.gov/Archives/edgar/data/1158324/000091205702032124/a2087073z10-q.htm).

Originally posted by Gernot
Rackmy, have you seen their last quarter's results? Because, according to them they really don't have problems getting customers...

Cyberwings didn't have a problem getting customers - that's a small piece of success.

Thank you very much.

Here is another article about cogent picking up some universities....

http://news.moneycentral.msn.com/ticker/article.asp?Feed=PR&Date=20020821&ID=1872938&Symbol=US:COI

Walmart is profitable. It doesn't make it a great place to shop.

Let's not forget what happened to Yipes. And another wannabee that shall remain nameless because it has kept the name and came out scott-free from chapter 7 :angry: :angry: :angry:

Yipes wasn't backed by Cisco :)

Isn't Yipes profitable though? I heard that they came out of bankruptcy. Nevertheless, I wish Cogent will survive.

Yipes profitable? :D

They did come out of bancruptcy, the new company is not the same although the have the same name.

After yipes restructure, most of their markets are completely profitable they also have a huge new line of financing, more then i can say for cogent on both accounts. Thats not to say i dont hope cogents does fine, theres alot of people on cogent and id hate to see them all go out of business because cogent made bad business decisions.

I worked for a competitor of Yipes and ally of Cogent, that went out of business. Let's just say I'd never work again for a telecom company.

Still waiting for the "anti-cogent" people who want to see bandwidth prices to rise again to post here.

am definitely not anti-cogent, but its time they got their house in order. what is the use of "growing" your business when you cant handle your existing clients?

example:
http://samspade.org/t/trace?a=internettotal.net

when they fix all those dns errors, we'll talk.

Originally posted by Furton
Still waiting for the "anti-cogent" people who want to see bandwidth prices to rise again to post here.


Looks like you just invited them. Why are you looking for trouble?

The truth hurts?

Originally posted by ben_h
am definitely not anti-cogent, but its time they got their house in order. what is the use of "growing" your business when you cant handle your existing clients?

example:
http://samspade.org/t/trace?a=internettotal.net

when they fix all those dns errors, we'll talk.

Eh, what is exactly is the problem there? Do you mean these DNS errors? These aren't really service-affecting or anything, they just give you these tiny little error message in that trace, but they absolutely don't affect anything at all.

http://samspade.org/t/trace?a=yipes.com
http://samspade.org/t/trace?a=sprintlink.net
http://samspade.org/t/trace?a=exodus.net
http://samspade.org/t/trace?a=nac.net
http://samspade.org/t/trace?a=williamscommunications.com

I was exicted to hear that my local University, Northern Michigan University, will be served by Cogent bandwidth through Michigan's Merit network. I'm really hoping I have an opportunity to tap into this locally, as there really are no affordable options out here in the sticks.

So I did a traceroute from my Charter Cable Modem to www.nmu.edu.:
--------------------------------------------------------
Tracing route to wwweb.nmu.edu [198.110.200.10]
over a maximum of 30 hops:

1 <10 ms 16 ms 16 ms X.X.X.X
2 31 ms 15 ms <10 ms X.X.X.X.up.mi.chartermi.net [X.X.X.X]
3 15 ms 16 ms <10 ms X.X.X.X.up.mi.chartermi.net [X.X.X.X]
4 31 ms 63 ms 46 ms 12.125.124.141
5 31 ms 31 ms 32 ms gbr2-p26.cgcil.ip.att.net [12.123.193.37]
6 31 ms 16 ms 31 ms gbr4-p70.cgcil.ip.att.net [12.122.1.181]
7 15 ms 32 ms 31 ms ggr1-p370.cgcil.ip.att.net [12.123.5.149]
8 125 ms 141 ms 125 ms 154.13.70.13
9 141 ms 125 ms 109 ms sw.peering2.tier1.us.psi.net [154.13.2.108]
10 125 ms 125 ms 109 ms p5-0.br01.lax10.atlas.psi.net [154.54.1.33]
11 110 ms 125 ms 125 ms p15-0.core01.lax01.atlas.cogentco.com [154.54.1.29]
12 156 ms * 109 ms p5-0.core01.san01.atlas.cogentco.com [66.28.4.78]
13 110 ms * 94 ms p6-0.core01.iah01.atlas.cogentco.com [66.28.4.5]
14 109 ms 94 ms 109 ms p5-0.core01.dfw01.atlas.cogentco.com [66.28.4.97]
15 94 ms 109 ms 110 ms p15-0.core02.dfw01.atlas.cogentco.com [66.28.4.26]
16 125 ms 109 ms 109 ms p15-0.core01.mci01.atlas.cogentco.com [66.28.4.38]
17 110 ms 125 ms 125 ms p5-0.core02.ord01.atlas.cogentco.com [66.28.4.34]
18 156 ms 125 ms 125 ms g8.ba21.b002281-1.ord01.atlas.cogentco.com [66.28.66.86]
19 * * * Request timed out.
20 109 ms 125 ms 110 ms atm4-0x6.nl-chi2.mich.net [198.108.23.50]
21 141 ms 172 ms 140 ms s1-0.nmu2.mich.net [198.108.23.109]
22 141 ms 140 ms 157 ms 198.110.192.97
23 141 ms 140 ms 141 ms wwweb.NMU.EDU [198.110.200.10]
--------------------------------------------------------
Neat! I take trip all the way out to California!

Know how far NMU's webserver is from my house? About 10 miles. :)

Brian

$30/Mbps on 100Mbit commitment does NOT justify this... its been like this for 2 days... i thought it would get fixed so i didn't bother mentioning it... but its is bloody ridiculous... !

traceroute to 66.28.242.253 (66.28.242.253), 64 hops max, 40 byte packets
1 209.53.12.254 (209.53.12.254) 12.284 ms 12.433 ms 12.190 ms
2 209.53.75.198 (209.53.75.198) 12.660 ms 12.339 ms 12.341 ms
3 nwmrbc01br01.bb.telus.com (204.174.217.39) 12.506 ms 12.694 ms 12.626 ms
4 sttlwa01br02.bb.telus.com (209.53.75.178) 16.705 ms 16.605 ms 16.531 ms
5 pos3-0.mpr1.sea1.us.mfnx.net (208.185.175.69) 16.758 ms 16.396 ms 16.764 ms
6 so-2-0-0.cr1.sea1.us.mfnx.net (208.185.175.178) 16.768 ms 16.866 ms 16.634 ms
7 pos0-0.mpr1.sea4.us.mfnx.net (64.125.31.86) 16.623 ms 16.666 ms 16.494 ms
8 216.200.249.86.cogent-above.above.net (216.200.249.86) 296.258 ms 296.329 ms 299.018 ms
9 p15-0.core01.den01.atlas.cogentco.com (66.28.4.102) 323.034 ms 323.934 ms 322.254 ms
10 p5-0.core01.mci01.atlas.cogentco.com (66.28.4.30) 363.540 ms 361.978 ms 366.207 ms
11 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 366.247 ms 366.749 ms 365.633 ms
12 g50.ba02.b000268-0.ord01.atlas.cogentco.com (66.28.66.78) 367.247 ms 370.333 ms 356.055 ms
13 66.28.242.253 (66.28.242.253) 355.562 ms 361.491 ms 367.734 ms

my traceroute from vienna, austria, EU. that hop from mfnx > cogent-above.above.net is f'd up. that should be an easily fixed problem if one were to contact the right people

traceroute to 66.28.242.253 (66.28.242.253), 30 hops max, 40 byte packets
1 warp9.vienna.at.max4eu.net (80.64.128.1) [AS20751] 2.027 ms 1.961 ms 1.964 ms
2 max4eu.VIX-eth011-102.at.lambdanet.net (217.71.108.109) [AS13237] 1.976 ms 1.980 ms 2.147 ms
3 M-4-so023-0.de.lambdanet.net (217.71.105.5) [AS13237] 7.355 ms 7.495 ms 7.642 ms
4 S-3-atm010-732.de.lambdanet.net (217.71.105.121) [AS13237] 10.378 ms 10.540 ms 10.933 ms
5 F-2-pos030-0.de.lambdanet.net (217.71.105.117) [AS13237] 13.788 ms 13.950 ms 14.097 ms
6 PZU-2-pos130.fr.lambdanet.net (217.71.96.149) [AS13237] 25.294 ms 25.457 ms 25.603 ms
7 bcr1-so-0-0-3-0.Paris.cw.net (208.172.251.141) [(null)] 26.160 ms 26.322 ms 26.468 ms
8 dcr2-loopback.NewYork.cw.net (206.24.194.100) [(null)] 117.796 ms 118.113 ms 118.424 ms
9 agr4-so-2-0-0.NewYork.cw.net (206.24.207.190) [(null)] 117.447 ms 117.550 ms 117.906 ms
10 acr2-loopback.NewYork.cw.net (206.24.194.62) [(null)] 118.831 ms 119.146 ms 119.452 ms
11 cable-and-wireless-peering.NewYork.cw.net (206.24.193.234) [(null)] 118.124 ms 118.422 ms 118.602 ms
12 p5-0.br01.jfk01.atlas.psi.net (154.54.1.197) [(null)] 118.833 ms 119.199 ms 119.534 ms
13 p14-0.core01.jfk01.atlas.cogentco.com (154.54.1.21) [(null)] 120.266 ms 120.453 ms 120.625 ms
14 p13-0.core02.jfk02.atlas.cogentco.com (66.28.4.121) [AS16631] 120.731 ms 120.882 ms 121.027 ms
15 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) [AS16631] 144.129 ms 145.386 ms 145.699 ms
16 g50.ba02.b000268-0.ord01.atlas.cogentco.com (66.28.66.78) [AS16631] 145.502 ms 145.805 ms 145.997 ms
17 66.28.242.253 (66.28.242.253) [AS16631] 146.074 ms 147.512 ms 148.143 ms

what happened? cogent didn't pay their bill to metromedia??? lol

traceroute to 66.28.118.11 (66.28.118.11), 64 hops max, 40 byte packets
1 209.53.12.254 (209.53.12.254) 18.287 ms 22.903 ms 29.157 ms
2 209.53.75.198 (209.53.75.198) 30.745 ms 23.917 ms 13.637 ms
3 vancbc01br01.bb.telus.com (204.174.217.38) 23.577 ms 12.470 ms 22.139 ms
4 clgrab21br01.bb.telus.com (209.53.75.182) 37.801 ms 32.999 ms 30.122 ms
5 clgrab31br01.bb.telus.com (154.11.10.165) 28.963 ms 33.595 ms 38.178 ms
6 chcnil23br00.bb.telus.com (154.11.10.130) 64.378 ms 62.114 ms 62.291 ms
7 so-3-1-0.cr1.ord2.us.mfnx.net (216.200.254.30) 65.780 ms 87.261 ms 62.921 ms
8 pos5-0.mpr1.dfw2.us.mfnx.net (208.184.233.149) 83.230 ms 96.231 ms 98.221 ms
9 so-3-0-0.cr1.dfw2.us.mfnx.net (216.200.127.213) 84.487 ms 89.824 ms 89.998 ms
10 so-4-0-0.pr1.dfw3.us.mfnx.net (64.125.31.218) 150.106 ms 84.601 ms 84.052 ms
11 64.124.51.171.cogentco.com (64.124.51.171) 251.276 ms 246.538 ms 254.059 ms
12 g50.ba01.b000870-0.dfw01.atlas.cogentco.com (66.28.5.30) 251.578 ms 252.166 ms 259.741 ms
13 Xamo-Entertainment.demarc.cogentco.com (66.28.28.50) 253.192 ms 253.814 ms 250.086 ms
14 66.28.118.11 (66.28.118.11) 250.615 ms 249.923 ms 251.586 ms

Originally posted by Gernot
Rackmy, have you seen their last quarter's results? Because, according to them they really don't have problems getting customers...

Anyone can stand in a park and sell someone elses dollar bills for 35 cents apiece and have a line of potential customers a mile long looking for their 65 cents, there is no secret there. The problem is you don't make alot of money doing it, and eventually you run out of other peoples dollar bills.

-Brendan

netdude. i'm wondering at what point your obvious blatant bashing of cogent will stop and turn into you blatantly pushing your own products? are you just building up the momentum to your first advertising post (oops, that's been deleted), ok, your second advertising post? or do you just like using the same old tired argument over and over again for the fun of it?


it's obvious there is a problem at certain hops with cogent. i'm sure you feel there are many more. but i've seen problems like that on many many other past servers i've had on other non-cogent connections (on yipes, on verio, on savvis, on level3, on verio, on qwest, etc etc), and i didn't stop to bash any of those companies. hell, twice in the past i've had some re-occuring problems with some hops from europe to one of my servers in the US on cogent and i simply emailed support@cogent .com and was pleased to have a fairly fast response both times and they addressed the issues. i've done the same with level3 and the same with yipes' support and have gotten similar positive results.

it's just it's starting to become obvious that your cogent bashing is one-sided and with an ulterior motive (to push your future planned products, which actually looked like great offerings).

Backed by cisco........


hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahhahahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha



Originally posted by Gernot
Yipes wasn't backed by Cisco :)

skylab, yeah... i bash cogent a lot... but most of it is because of the frustration i am having with my current sites and not totally about my own new setup... u know why i even thought that one up a few months ago? because i was so bloody fed up with cogent bullsh*t... and i was fed up with not being able to find another host that is actually as affordable as fdc... (i am not really making anything off the sites i host, so i m not seeking to spend too much, mostly high bandwidth sites for friends)... and those traceroutes/hops... i posted only after seeing them like that for over 2 days without ANY improvement... i waited a whole two days before bringing it up... if it were fixed, i would have never mentioned it!

Originally posted by netdude
skylab, yeah... i bash cogent a lot... but most of it is because of the frustration i am having with my current sites and not totally about my own new setup... u know why i even thought that one up a few months ago? because i was so bloody fed up with cogent bullsh*t... and i was fed up with not being able to find another host that is actually as affordable as fdc... (i am not really making anything off the sites i host, so i m not seeking to spend too much, mostly high bandwidth sites for friends)... and those traceroutes/hops... i posted only after seeing them like that for over 2 days without ANY improvement... i waited a whole two days before bringing it up... if it were fixed, i would have never mentioned it!

I have a "feeling" that Cogent will reply to your bashin ghere soon and also talk to the WHT staff... can't wait for "netdude2" to sign up :rolleyes:

lol

cogent coming on here ... thats a funny one ... lol

if i had said any lies, then they'd have a right to take legal action/etc... but ya know what? i have not to date, pretty much everything i've said was backed up by undisputable evidence (traces/etc)... if not, it was actually backed up by someone else knowledgable on these forums...

so... for the record, nocsol: you're a comedian.
-------
btw, how i mentioned trouble with my own sites... i was implying my sites performance due to the pathetic cogent network.

now... back to the pathetic cogent network:

traceroute to 66.28.242.253 (66.28.242.253), 64 hops max, 40 byte packets
1 209.53.12.254 (209.53.12.254) 12.242 ms 12.185 ms 12.326 ms
2 209.53.75.198 (209.53.75.198) 12.536 ms 12.264 ms 12.294 ms
3 vancbc01br01.bb.telus.com (204.174.217.6) 12.487 ms 12.481 ms 12.567 ms
4 clgrab21br01.bb.telus.com (209.53.75.182) 29.041 ms 28.693 ms 28.876 ms
5 clgrab31br01.bb.telus.com (154.11.10.165) 29.054 ms 29.351 ms 28.881 ms
6 chcnil23br00.bb.telus.com (154.11.10.130) 62.205 ms 62.120 ms 62.276 ms
7 so-3-1-0.cr1.ord2.us.mfnx.net (216.200.254.30) 62.295 ms 62.490 ms 62.305 ms
8 pos5-0.mpr1.dfw2.us.mfnx.net (208.184.233.149) 83.025 ms 83.435 ms 82.857 ms
9 so-3-0-0.cr2.dfw2.us.mfnx.net (216.200.127.217) 83.174 ms 82.937 ms 83.777 ms
10 so-5-0-0.pr1.dfw3.us.mfnx.net (208.184.232.114) 83.520 ms 83.205 ms 83.470 ms
11 64.124.51.171.cogentco.com (64.124.51.171) 238.120 ms 237.646 ms 240.552 ms
12 p15-0.core01.mci01.atlas.cogentco.com (66.28.4.38) 281.230 ms 279.746 ms 281.158 ms
13 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 285.049 ms 282.323 ms 283.625 ms
14 g50.ba02.b000268-0.ord01.atlas.cogentco.com (66.28.66.78) 280.742 ms 280.229 ms 274.737 ms
15 66.28.242.253 (66.28.242.253) 279.093 ms 271.510 ms 273.053 ms

traceroute to salt.cogentco.com (66.28.0.10), 64 hops max, 40 byte packets
1 209.53.12.254 (209.53.12.254) 12.659 ms 12.532 ms 12.236 ms
2 209.53.75.198 (209.53.75.198) 12.402 ms 21.675 ms 12.571 ms
3 vancbc01br01.bb.telus.com (204.174.217.6) 12.992 ms 12.236 ms 12.272 ms
4 clgrab21br01.bb.telus.com (209.53.75.182) 28.738 ms 29.347 ms 28.822 ms
5 clgrab31br01.bb.telus.com (154.11.10.165) 29.247 ms 29.108 ms 29.005 ms
6 chcnil23br00.bb.telus.com (154.11.10.130) 62.328 ms 62.352 ms 62.310 ms
7 so-3-1-0.cr1.ord2.us.mfnx.net (216.200.254.30) 62.962 ms 62.545 ms 62.382 ms
8 pos5-0.mpr1.dfw2.us.mfnx.net (208.184.233.149) 85.421 ms 83.111 ms 83.527 ms
9 so-3-0-0.cr1.dfw2.us.mfnx.net (216.200.127.213) 83.008 ms 83.056 ms 82.984 ms
10 so-4-0-0.pr1.dfw3.us.mfnx.net (64.125.31.218) 82.944 ms 83.346 ms 83.163 ms
11 64.124.51.171.cogentco.com (64.124.51.171) 237.702 ms 247.658 ms 253.476 ms
12 p15-0.core01.dfw01.atlas.cogentco.com (66.28.4.25) 253.370 ms 248.429 ms 249.567 ms
13 p4-0.core01.dca01.atlas.cogentco.com (66.28.4.89) 294.015 ms 289.043 ms 289.839 ms
14 salt.cogentco.com (66.28.0.10) 287.819 ms 281.552 ms *

now this is ridiculous... ! over 500ms!?! thats just bloody pathetic!

traceroute to salt.cogentco.com (66.28.0.10), 64 hops max, 40 byte packets
1 209.53.12.254 (209.53.12.254) 12.256 ms 12.241 ms 12.077 ms
2 209.53.75.198 (209.53.75.198) 12.719 ms 12.195 ms 12.686 ms
3 vancbc01br01.bb.telus.com (204.174.217.6) 12.484 ms 12.476 ms 12.810 ms
4 clgrab21br01.bb.telus.com (209.53.75.182) 28.763 ms 29.398 ms 28.694 ms
5 clgrab31br01.bb.telus.com (154.11.10.165) 29.532 ms 29.355 ms 29.746 ms
6 chcnil23br00.bb.telus.com (154.11.10.130) 62.582 ms 62.401 ms 62.366 ms
7 so-3-1-0.cr1.ord2.us.mfnx.net (216.200.254.30) 62.598 ms 62.511 ms 62.126 ms
8 pos5-0.mpr1.dfw2.us.mfnx.net (208.184.233.149) 83.523 ms 83.071 ms 83.350 ms
9 so-3-0-0.cr1.dfw2.us.mfnx.net (216.200.127.213) 83.215 ms 83.084 ms 83.353 ms
10 so-4-0-0.pr1.dfw3.us.mfnx.net (64.125.31.218) 82.987 ms 83.074 ms 83.484 ms
11 64.124.51.171.cogentco.com (64.124.51.171) 461.657 ms 459.833 ms 453.589 ms
12 p15-0.core01.dfw01.atlas.cogentco.com (66.28.4.25) 456.943 ms 451.423 ms 450.038 ms
13 p4-0.core01.dca01.atlas.cogentco.com (66.28.4.89) 495.685 ms 511.686 ms 512.311 ms
14 salt.cogentco.com (66.28.0.10) 510.641 ms 503.312 ms 501.732 ms

Originally posted by johnallen
Walmart is profitable. It doesn't make it a great place to shop.

it's a great place to shop!

Is telus an isp out of the US? if so that can explain the 500 ms ping

notice where the ping time jumps... its not on the telus network, its on the cogent-above.net interconnection... :P now this isn't always signifcant... but... take note... above.net = cogent's primary transit provider...

telus = isp in canada... :P so there is no way to justify such high pings... :P

Originally posted by NocSol


I have a "feeling" that Cogent will reply to your bashin ghere soon and also talk to the WHT staff... can't wait for "netdude2" to sign up :rolleyes:


Only reason that you would have that "feeling" is because you would be the one bringing them here.

It would be really lame for you (NocSol) to beg/bribe/whatever WHT into banning netdude...then WHT would just be another communist forum censoring whatever isn't to their liking. But I don't think whatever you're trying to do NocSol is going to work. Why? I don't see any RackShack haters being banned even though they own these forums...WHT isn't lame; they believe in free speech and this is what the internet is about (unless you're in China.)

edited for spelling error

Originally posted by edude
Backed by cisco........


hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahhahahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha

hahahahahahahahahahahhahahahahhahahahhahahahahahahhahahahahha





Glad you're so happy. Care to elaborate or is this just for insiders?

Originally posted by netdude

notice where the ping time jumps... its not on the telus network, its on the cogent-above.net interconnection... :P now this isn't always signifcant... but... take note... above.net = cogent's primary transit provider...

telus = isp in canada... :P so there is no way to justify such high pings... :P


There is no problem between above.net and Cogent, as the followign traceroute back to you shows:

traceroute to 209.53.12.254 (209.53.12.254), 30 hops max, 38 byte packets
1 f13.ba01.b003070-1.sfo01.atlas.cogentco.com (66.250.4.165) 0.676 ms 0.438 ms 0.389 ms
2 g0-2.core01.sfo01.atlas.cogentco.com (66.28.5.177) 0.786 ms 0.595 ms 0.654 ms
3 p15-0.core02.sfo01.atlas.cogentco.com (66.28.4.70) 0.685 ms 0.797 ms 0.626 ms
4 p6-0.br01.sfo01.atlas.psi.net (154.54.1.42) 0.435 ms 0.512 ms 0.396 ms
5 p6-0.br01.lax10.atlas.psi.net (154.54.1.30) 12.928 ms 12.812 ms 13.365 ms
6 p4-0.sw.peering2.tier1.psi.net (154.54.1.34) 12.896 ms 13.038 ms 12.896 ms
7 nc.peering.tier1.us.psi.net (154.13.2.67) 352.914 ms 347.893 ms 349.293 ms
8 154.13.70.26 (154.13.70.26) 350.472 ms 350.277 ms 354.236 ms
9 chcnil23br00.bb.telus.com (154.11.11.93) 361.779 ms 366.819 ms 359.350 ms
10 clgrab31br01.bb.telus.com (154.11.10.129) 391.621 ms 387.597 ms 381.335 ms
11 clgrab21br01.bb.telus.com (154.11.10.166) 384.545 ms 390.119 ms 393.602 ms
12 vancbc01br01.bb.telus.com (209.53.75.181) 405.357 ms 411.940 ms 404.833 ms
13 bc-regional-gw1.bctel.net (204.174.217.13) 415.577 ms 412.540 ms 402.917 ms
14 209.53.75.197 (209.53.75.197) 401.242 ms 401.682 ms *

There is, however, a problem at hop 7 which is still in Cogent's network and I'm sure they are aware of it and fixing it and that this problem will disappear soon. I have, of course, also sent a copy of this trace to Cogent's support desk.

Originally posted by NocSol


I have a "feeling" that Cogent will reply to your bashin ghere soon and also talk to the WHT staff... can't wait for "netdude2" to sign up :rolleyes:

Sorry, lol but this is ridiculous. Nuff' said lol

Originally posted by Gernot


Sorry, lol but this is ridiculous. Nuff' said lol

Nocsol's just making an ass out of himself (again.) Next thing he'll do is leave the WHT forums for the third time in a row because none of us takes him seroiusly. Not our fault, it's hard to when you have such a bad reputation and keep on making it worse with foolish comments such as this.

Mushrew, your behavior is the one of a 12 year old.

Originally posted by NocSol
Mushrew, your behavior is the one of a 12 year old.

BAHAHA

You're not the one to be saying that!!!

I see, so COME ON.. BASH me .. that's all you can do! :angry:

lol... right, they're going to take care of it fast... yup... just like my problems i posted about... ya know what? the problems i posted about are still evident... so thats what 3 or 4 days, no resolution... yup, fast to fix networks... right... ya know how many million visitors my problem is probably affecting? lots... and yet its still not fixed... i mean, if this were level3 (which is like 3rd worst on internetpulse) or verio (which has the worst rating)... or any other big-name carrier that cogent lovers claim it to be... it would have been fixed in nothing more than a few minutes/hours... !
(internetpulse.com values don't really mean much, but they do give a relative rating from network-to-network... heh... and... they're impartial... and... they are done by the same guys that do boardwatch...)

as for mushrew? why is he being childish? because he laughs at the prospect of the FBI breaking down my door for badmouthing (with the truth) cogent?

Originally posted by Gernot

...
There is, however, a problem at hop 7 which is still in Cogent's network and I'm sure they are aware of it and fixing it and that this problem will disappear soon. I have, of course, also sent a copy of this trace to Cogent's support desk.

come on dude... this just makes u seem childish... atleast have a little dignity...

Originally posted by NocSol
I see, so COME ON.. BASH me .. that's all you can do! :angry:
------------------------------------------------------------------------------
now we're off topic... i guess best if we limit ourselves to a cogent-only discussion, eh?
------------------------------------------------------------------------------
trapnoc, i don't figure its dignified to bother making a new post to reply to your bullsh*t... i mean, if thats what you think, fine... ya know what? your opinion don't mean squat to me... make a thread about it in the lounge... this is a cogent thread... k? sorry i couldn't support your beloved cogent... heh

I'm new here, but, "netdude" you DO sound like a retarded 12 year old. You also write like one.

Do you have anything better to do with your time?

When I start reading what I think will be an intelligent thread and I see you post to it I know right there it ends being an intelligent thread.

TrapNOC

Sorry to see you have these kind of problems with Cogent. Maybe these guys a overselling their Cogent link and it's really maxed out.


Originally posted by netdude
now this is ridiculous... ! over 500ms!?! thats just bloody pathetic!

traceroute to salt.cogentco.com (66.28.0.10), 64 hops max, 40 byte packets
1 209.53.12.254 (209.53.12.254) 12.256 ms 12.241 ms 12.077 ms
2 209.53.75.198 (209.53.75.198) 12.719 ms 12.195 ms 12.686 ms
3 vancbc01br01.bb.telus.com (204.174.217.6) 12.484 ms 12.476 ms 12.810 ms
4 clgrab21br01.bb.telus.com (209.53.75.182) 28.763 ms 29.398 ms 28.694 ms
5 clgrab31br01.bb.telus.com (154.11.10.165) 29.532 ms 29.355 ms 29.746 ms
6 chcnil23br00.bb.telus.com (154.11.10.130) 62.582 ms 62.401 ms 62.366 ms
7 so-3-1-0.cr1.ord2.us.mfnx.net (216.200.254.30) 62.598 ms 62.511 ms 62.126 ms
8 pos5-0.mpr1.dfw2.us.mfnx.net (208.184.233.149) 83.523 ms 83.071 ms 83.350 ms
9 so-3-0-0.cr1.dfw2.us.mfnx.net (216.200.127.213) 83.215 ms 83.084 ms 83.353 ms
10 so-4-0-0.pr1.dfw3.us.mfnx.net (64.125.31.218) 82.987 ms 83.074 ms 83.484 ms
11 64.124.51.171.cogentco.com (64.124.51.171) 461.657 ms 459.833 ms 453.589 ms
12 p15-0.core01.dfw01.atlas.cogentco.com (66.28.4.25) 456.943 ms 451.423 ms 450.038 ms
13 p4-0.core01.dca01.atlas.cogentco.com (66.28.4.89) 495.685 ms 511.686 ms 512.311 ms
14 salt.cogentco.com (66.28.0.10) 510.641 ms 503.312 ms 501.732 ms

"Sorry to see you have these kind of problems with Cogent. Maybe these guys a overselling their Cogent link and it's really maxed out. "

I doubt it's a result of overselling since the ping jumps occur on Cogent's routers, not at the provider.

just so i'm not totally 1 sided... it seems cogent is now back to normal... after 4 days of being f*cked... heh... but still getting 170ms ping times to chicago (but thats normal), when it shouldn't be more than 60ms... i mean... i get 80ms to atlanta... heh

actually that problem couldnt be a provider overselling, as the problem starts at cogents core router for that area, if it was a matter of overselling the problem would begin at the customers premise router.

cluster,
suron:~# ns cogentco.com
Server: localhost
Address: 127.0.0.1

Non-authoritative answer:
Name: cogentco.com
Address: 66.28.0.10

suron:~# ns 66.28.0.10
Server: localhost
Address: 127.0.0.1

Name: salt.cogentco.com
Address: 66.28.0.10

so they arent overselling i dont think?