Does Cogent Suck?
 

I'm trying to help a friend get a new server set up. And one of the places he wants to go is to a datacenter that is on a Cogent line. Since I do my fair share of drinking, I can't really remember whether Cogent is any good or not. What are you guys and gal's opinions?

Nope. They're a good backup for Level3
.

how does one go about finding who gets their bandwidth from cognet and who doesnt?

I'm not sure it really matters anymore. Depending on the route it seems all providers can have equal amounts of latency from time to time. There are times where Cogent is faster than other providers that you would expect to be top quality.

Are they a Teir 1 provider?

Cogent is worth noting if you ask me.. have very bad experince, hit me up if you want to know why I think so

its not like rocket sciene you can post it there as well

Well the truth is that they used to suck alot. We used to use them in the past.
Nowdays they are very very good. We created a second network ,working with them for 8 months and i can say they are PERFECT.

Cheap and good

Yeah, tell us! I promise we won't tell anyone else :thumbsup

Does Cogent Suck?

WARNING: Most Hosting Companies Do Not Want You To Read This!

Well Cogent is defiantly the lowest-priced bandwidth a hosting provider can provide, but a lot hosting companies will use them in their bandwidth mix because of the cost savings and many will defend them to no end. So in rather giving you my opinion I would like to show you how to use some tools to test any hosting company?s network and let you form your own opinion.

Lets check a hosting company who should we use? Hmmm...
Let?s pick on a big guy www.ev1.net (because I know they use Cogent)

Here are the steps

1.) As www.isprime.com (a very good hosting company) has pointed out? let?s check who they are peered with (note fixdorbit.com is not 100% accurate but is close enough for what we are doing) first.

http://www.fixedorbit.com/search.htm

Enter the IP or host name to find AS for
IP/Domain ev1.net

Giver use a return of

Peers Neighbors
ASN Name
174 COGENT-PSI-1
2828 XO-AS15
2914 VERIO
3561 SAVVIS
4323 TWTC
6461 ABOVENET
7911 WCG

So we have confirmed they are using Cogent in there mix (and more likely for most of there bandwidth).

2.) So now let?s test the ev1.net network from around the world and see how well it performs. To do this you should actually compare two networks at the same time. Since I am posting this I?ll volunteer www.e5hosting.com (we are on NTT/Verio?s network).

-------------------------------------------------------------------------------------------------------------------------------
Here is the definition of traceroute - http://www.webopedia.com/TERM/t/traceroute.html
-------------------------------------------------------------------------------------------------------------------------------

So it?s going to be: www.ev1.net vs www.e5hosting.com

But we can not just do a trace route from you local computer we need to test the network from around the world. So we are going to use www.traceroute.org (this has a site that list traceroutes from around the world) and are the easiest way for the average person to check someone?s network performance.

We will be looking for two things? one the fastest times and? two the shortest amount of hops to the destination. I?m? only going to run a few traceroutes from a few different countries using, but feel free to test your own.



Here is the first test from Argentina ? http://daemon.servit.com.ar/cgi-bin/trace

-------------------------------------------------------------------------------------------------------------------------------
www.ev1.net returned the following from Argentina http://daemon.servit.com.ar/cgi-bin/trace
-------------------------------------------------------------------------------------------------------------------------------
traceroute to ev1.net (207.218.192.46), 30 hops max, 40 byte packets
1 lineaAO86.velocom.com.ar (200.59.46.86) 0.829 ms 0.378 ms 0.64 ms
2 lineaAT246.velocom.com.ar (200.59.50.246) 0.34 ms 0.558 ms 0.282 ms
3 200-47-54-238.comsat.net.ar (200.47.54.238) 0.6 ms 0.633 ms 0.816 ms
4 200.47.201.101 (200.47.201.101) 169.398 ms 169.402 ms 170.029 ms
5 200.47.201.1 (200.47.201.1) 132.66 ms 132.133 ms 132.485 ms
6 216.6.2.6 (216.6.2.6) 132.334 ms 132.145 ms 132.284 ms
7 216.6.2.5 (216.6.2.5) 169.916 ms 178.55 ms 169.538 ms
8 if-1-3.core2.NJY-Newark.teleglobe.net (64.86.138.145) 168.996 ms 164.585 ms 164.552 ms
9 if-3-1.mcore4.NJY-Newark.teleglobe.net (216.6.63.5) 258.542 ms 209.902 ms 167.494 ms
10 if-4-0.core1.NTO-NewYork.teleglobe.net (216.6.82.5) 165.072 ms 164.467 ms 164.892 ms
11 p4-1-3-0.r04.nycmny01.us.bb.verio.net (129.250.8.101) 165.082 ms 165.647 ms 169.867 ms
12 p16-1-1-0.r21.nycmny01.us.bb.verio.net (129.250.3.48) 165.272 ms 170.867 ms 164.815 ms
13 * * *
14 xe-0-2-0.r20.asbnva01.us.bb.verio.net (129.250.4.118) 164.798 ms 164.75 ms 165.451 ms
15 p16-0-1-1.r21.dllstx09.us.bb.verio.net (129.250.5.34) 196.557 ms 197.207 ms 197.141 ms
16 p16-6-0-0.r02.hstntx01.us.bb.verio.net (129.250.5.101) 234.656 ms 203.986 ms 204.012 ms
17 ge-0.ev1.hstntx01.us.bb.verio.net (129.250.10.66) 183.345 ms 185.829 ms 183.197 ms
18 ivhou-207-218-223-85.ev1.net (207.218.223.85) 183.713 ms 183.781 ms 184.092 ms
19 ivhou-207-218-223-85.ev1.net (207.218.223.85) 184.199 ms 183.89 ms 183.453 ms
20 ivhou-207-218-223-85.ev1.net (207.218.223.85) 184.411 ms 187.475 ms 183.64 ms
21 ivhou-207-218-223-85.ev1.net (207.218.223.85) 185.24 ms 183.432 ms 183.374 ms
22 ivhou-207-218-223-85.ev1.net (207.218.223.85) 183.505 ms 183.428 ms 183.719 ms
23 ivhou-207-218-223-85.ev1.net (207.218.223.85) 184.437 ms 183.529 ms 184.362 ms
24 ivhou-207-218-223-85.ev1.net (207.218.223.85) 191.431 ms 183.573 ms 183.653 ms
25 ivhou-207-218-223-85.ev1.net (207.218.223.85) 183.624 ms 193.5 ms 185.233 ms
26 ivhou-207-218-223-85.ev1.net (207.218.223.85) 184.487 ms 184.521 ms 183.315 ms
27 ivhou-207-218-223-85.ev1.net (207.218.223.85) 183.398 ms 183.627 ms 189.642 ms
28 ivhou-207-218-223-85.ev1.net (207.218.223.85) 183.479 ms 183.718 ms 184.277 ms
29 ivhou-207-218-223-85.ev1.net (207.218.223.85) 183.77 ms 184.2 ms 183.727 ms
30 ivhou-207-218-223-85.ev1.net (207.218.223.85) 184.506 ms 183.59 ms 184.382 ms
-------------------------------------------------------------------------------------------------------------------------------
www.e5hosting.com returned the following from Argentina http://daemon.servit.com.ar/cgi-bin/trace
-------------------------------------------------------------------------------------------------------------------------------
traceroute to e5hosting.com (198.65.137.252), 30 hops max, 40 byte packets
1 lineaAO86.velocom.com.ar (200.59.46.86) 0.844 ms 1.164 ms 0.358 ms
2 lineaAT246.velocom.com.ar (200.59.50.246) 0.329 ms 0.295 ms 0.487 ms
3 * 200-47-54-238.comsat.net.ar (200.47.54.238) 1.014 ms 0.621 ms
4 200.47.201.101 (200.47.201.101) 169.368 ms 169.857 ms 170.183 ms
5 200.47.201.1 (200.47.201.1) 132.569 ms 132.481 ms 132.845 ms
6 ComsatInternational.so-1-1-2.ar2.MIA1.gblx.net (64.214.174.146) 132.249 ms 132.086 ms 132.356 ms
7 so-1-1-2.ar2.MIA1.gblx.net (64.214.174.145) 132.635 ms 131.952 ms 135.393 ms
8 so2-1-0-2488M.ar1.DCA3.gblx.net (67.17.67.57) 166.52 ms 185.252 ms so7-2-0-2488M.ar1.DCA3.gblx.net (67.17.64.69) 161.891 ms
9 verio.ar1.DCA3.gblx.net (208.51.6.34) 161.282 ms 161.859 ms 164.352 ms
10 xe-0-2-0.r20.asbnva01.us.bb.verio.net (129.250.4.118) 162.838 ms 164.002 ms 161.299 ms
11 mg-1.c00.stngva01.us.da.verio.net (129.250.28.202) 162.257 ms 162.178 ms 162.044 ms
12 161.58.156.189 (161.58.156.189) 162.276 ms 169.68 ms 161.401 ms
13 198.65.137.252 (198.65.137.252) 161.319 ms 161.551 ms 161.237 ms
-------------------------------------------------------------------------------------------------------------------------------

And here are the results? :)

www.ev1.net hopes = 30 and time= 184.382 ms (milliseconds)

www.e5hosting.com hopes = 13 and time= 161.237 ms (milliseconds)

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

Continues on next thread --->

-

Here is the second test from Canada? http://probe.pcconsultation.net

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

www.ev1.net returned the following from Canada http://probe.pcconsultation.net (select traceroute from the box)

traceroute to www.ev1.net (216.88.76.7) from 192.168.0.105, 30 hops max, 38 byte packets
1 fwabsolut (192.168.0.1) 0.247 ms 0.139 ms 0.134 ms
2 ppp01-254.dsl.citenet.net (206.123.47.254) 9.123 ms 9.173 ms 10.840 ms
3 undefined-node-27.citenet.net (205.237.242.27) 60.487 ms 9.072 ms 13.195 ms
4 g80-37.citenet.net (209.41.128.37) 9.097 ms 19.462 ms 11.979 ms
5 g80-131.citenet.net (209.41.128.131) 12.032 ms 10.414 ms 13.922 ms
6 Cite-Net-mtl-gw.peer1.net (66.199.164.253) 9.605 ms 10.449 ms 9.990 ms
7 GIG1-0.mtl-core-b.peer1.net (216.187.90.41) 12.055 ms 11.380 ms 10.724 ms
8 OC48POS4-0.mtl-core-a.peer1.net (216.187.90.45) 12.308 ms 11.649 ms 59.025 ms
9 OC48-POS2-0.nyc-telx-dis-a.peer1.net (216.187.115.130) 19.426 ms 17.984 ms 55.091 ms
10 OC48-POS3-0.nyc-teleh-dis-2.peer1.net (216.187.115.166) 18.210 ms 18.577 ms 18.356 ms
11 fast0-0.iix-igr01.nycl.twtelecom.net (198.32.160.35) 18.434 ms 28.662 ms 18.816 ms
12 core-01-so-1-0-0-0.nycl.twtelecom.net (66.192.240.197) 36.682 ms 21.552 ms 18.424 ms
13 core-02-so-0-0-0-0.atln.twtelecom.net (66.192.255.23) 44.266 ms 88.446 ms 40.793 ms
14 dist-01-so-0-0-0-0.hsto.twtelecom.net (66.192.246.1) 63.393 ms 61.804 ms 60.993 ms
15 hagg-02-ge-3-3-0-505.hsto.twtelecom.net (66.192.246.123) 62.755 ms 60.528 ms 60.134 ms
16 216-54-253-2.gen.twtelecom.net (216.54.253.2) 74.609 ms 62.712 ms 61.995 ms
17 ivhou-207-218-223-66.ev1.net (207.218.223.66) 64.394 ms !X 61.350 ms !X 61.956 ms !X

---------------------------------------------------------------------------------------------------------------------------
www.e5hosting.com returned the following from Canada http://probe.pcconsultation.net (select traceroute from the box)

traceroute to www.e5hosting.com (198.65.137.252) from 192.168.0.105, 30 hops max, 38 byte packets
1 fwabsolut (192.168.0.1) 0.214 ms 0.138 ms 0.153 ms
2 ppp01-254.dsl.citenet.net (206.123.47.254) 170.504 ms 33.814 ms 9.240 ms
3 undefined-node-27.citenet.net (205.237.242.27) 8.530 ms 9.202 ms 8.503 ms
4 g80-37.citenet.net (209.41.128.37) 9.331 ms 9.741 ms 9.248 ms
5 g80-131.citenet.net (209.41.128.131) 9.801 ms 36.364 ms 11.401 ms
6 Cite-Net-mtl-gw.peer1.net (66.199.164.253) 13.864 ms 10.756 ms 10.406 ms
7 GIG1-0.mtl-core-b.peer1.net (216.187.90.41) 12.457 ms 10.691 ms 9.501 ms
8 OC48POS2-0.tor-core-b.peer1.net (216.187.68.94) 19.877 ms 18.831 ms 17.144 ms
9 OC48POS1-0.tor-core-1.peer1.net (216.187.114.133) 21.094 ms 20.518 ms 17.683 ms
10 OC48POS0-0.chi-dis-1.peer1.net (216.187.114.141) 31.694 ms 29.440 ms 30.921 ms
11 ge-4-3-0.r00.chcgil06.us.bb.verio.net (206.223.119.12) 31.196 ms 29.958 ms 29.955 ms
12 p16-0-3-0.r21.asbnva01.us.bb.verio.net (129.250.5.103) 49.456 ms 39.411 ms 39.307 ms
13 xe-0-2-0.r20.asbnva01.us.bb.verio.net (129.250.4.118) 42.470 ms 42.110 ms 39.080 ms
14 mg-1.c00.stngva01.us.da.verio.net (129.250.28.202) 41.071 ms 39.688 ms 40.247 ms
15 161.58.156.189 (161.58.156.189) 41.087 ms 39.484 ms 38.602 ms
16 198.65.137.252 (198.65.137.252) 41.875 ms 39.094 ms 39.492 ms

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

And here are the results? :)

www.ev1.net hopes = 17 and time= 61.956 ms (milliseconds)

www.e5hosting.com hopes = 16 and time= 39.492 ms (milliseconds)

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

Here is the third test from Germany? http://www.helios.de/cgi-bin/nph-trace.cgi

---------------------------------------------------------------------------------------------------------------------------
www.ev1.net returned the following from Germany? http://www.helios.de/cgi-bin/nph-trace.cgi

trying to get source for www.ev1.net
source should be 193.141.98.37
traceroute to www.ev1.net (216.88.76.7) from 193.141.98.37 (193.141.98.37), 30 hops max
outgoing MTU = 1500
1 cishelios2.helios.de (193.141.98.1) 11 ms 5 ms 4 ms
2 pop9.pop-hannover.de (193.98.1.212) 14 ms 14 ms 31 ms
3 popcore.pop-hannover.de (193.98.1.213) 14 ms 14 ms 21 ms
4 eurocore.pop-hannover.net (62.48.64.236) 15 ms 15 ms 16 ms
5 ffmcore2.pop-hannover.net (62.48.66.98) 21 ms 21 ms 21 ms
6 ffmcore.pop-hannover.net (62.48.66.106) 22 ms 28 ms 22 ms
7 de-cix.fra.above.net (80.81.192.226) 32 ms 23 ms 22 ms
8 pos11-0.cr2.cdg2.fr.above.net (64.125.31.137) 135 ms 154 ms 134 ms
9 pos3-0.cr1.cdg2.fr.above.net (64.125.31.125) 136 ms 134 ms 134 ms
10 so-5-1-0.cr1.lhr3.uk.above.net (64.125.31.129) 40 ms 40 ms 40 ms
11 so-7-0-0.cr1.dca2.us.above.net (64.125.31.186) 111 ms 112 ms 128 ms
12 so-5-1-0.mpr2.atl6.us.above.net (64.125.29.37) 140 ms 171 ms 122 ms
13 so-0-0-0.mpr1.atl6.us.above.net (64.125.27.49) 122 ms 123 ms 123 ms
14 so-3-3-0.mpr2.iah1.us.above.net (64.125.29.66) 152 ms 153 ms 148 ms
15 216.200.251.61.ev1.net (216.200.251.61) 135 ms 134 ms 135 ms
16 ivhou-207-218-223-66.ev1.net (207.218.223.66) 150 ms 150 ms 150 ms
17 ivhou-207-218-223-66.ev1.net (207.218.223.66) 150 ms 150 ms 151 ms
18 ivhou-207-218-223-66.ev1.net (207.218.223.66) 150 ms 150 ms 150 ms
19 ivhou-207-218-223-66.ev1.net (207.218.223.66) 154 ms 150 ms 150 ms
20 ivhou-207-218-223-66.ev1.net (207.218.223.66) 151 ms 150 ms 149 ms
21 ivhou-207-218-223-66.ev1.net (207.218.223.66) 150 ms 150 ms 151 ms
22 ivhou-207-218-223-66.ev1.net (207.218.223.66) 154 ms 149 ms 150 ms
23 ivhou-207-218-223-66.ev1.net (207.218.223.66) 152 ms 162 ms 151 ms
24 ivhou-207-218-223-66.ev1.net (207.218.223.66) 150 ms 150 ms 150 ms
25 ivhou-207-218-223-66.ev1.net (207.218.223.66) 163 ms 151 ms 150 ms
26 ivhou-207-218-223-66.ev1.net (207.218.223.66) 150 ms 157 ms 149 ms
27 ivhou-207-218-223-66.ev1.net (207.218.223.66) 162 ms 149 ms 149 ms
28 ivhou-207-218-223-66.ev1.net (207.218.223.66) 149 ms 150 ms 154 ms
29 ivhou-207-218-223-66.ev1.net (207.218.223.66) 153 ms 150 ms 150 ms
30 ivhou-207-218-223-66.ev1.net (207.218.223.66) 150 ms 157 ms 152 ms

---------------------------------------------------------------------------------------------------------------------------
www.e5hosting.com returned the following from Germany? http://www.helios.de/cgi-bin/nph-trace.cgi

trying to get source for www.e5hosting.com
source should be 193.141.98.37
traceroute to www.e5hosting.com (198.65.137.252) from 193.141.98.37 (193.141.98.37), 30 hops max
outgoing MTU = 1500
1 cishelios2.helios.de (193.141.98.1) 5 ms 4 ms 4 ms
2 pop9.pop-hannover.de (193.98.1.212) 14 ms 14 ms 14 ms
3 popcore.pop-hannover.de (193.98.1.213) 13 ms 14 ms 13 ms
4 eurocore.pop-hannover.net (62.48.64.236) 15 ms 14 ms 14 ms
5 hnvr-s1-rou-1071.DE.eurorings.net (134.222.111.241) 15 ms 15 ms 15 ms
6 hmb-s2-rou-1001.DE.eurorings.net (134.222.227.117) 20 ms 20 ms 20 ms
7 dssd-s2-rou-1001.DE.eurorings.net (134.222.230.33) 26 ms 27 ms 55 ms
8 ledn-rou-1001.NL.eurorings.net (134.222.230.17) 30 ms 31 ms 31 ms
9 ewr-brdr-02.inet.qwest.net (134.222.254.2) 110 ms 110 ms 108 ms
10 ewr-core-01.inet.qwest.net (205.171.17.125) 109 ms 109 ms 110 ms
11 jfk-core-02.inet.qwest.net (205.171.8.246) 107 ms 108 ms 107 ms
12 jfk-brdr-02.inet.qwest.net (205.171.230.21) 109 ms 110 ms 109 ms
13 129.250.9.209 (129.250.9.209) 109 ms 110 ms 109 ms
14 p16-1-1-0.r20.nycmny01.us.bb.verio.net (129.250.2.36) 108 ms 108 ms 109 ms
15 p16-7-0-0.r02.stngva01.us.bb.verio.net (129.250.2.167) 114 ms 115 ms 115 ms
16 mg-2.c00.stngva01.us.da.verio.net (129.250.26.202) 116 ms 115 ms 115 ms
17 161.58.156.189 (161.58.156.189) 112 ms 113 ms 113 ms
18 198.65.137.252 (198.65.137.252) 116 ms 117 ms 117 ms

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

And here are the results? :)

www.ev1.net hopes = 30 and time= 152 ms (milliseconds)

www.e5hosting.com hopes = 18 and time= 117 ms (milliseconds)

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

So there you have it? now you can draw your own conclusion if Cogent sucks.

Just remember that is only bandwidth you still have to considered the hosting companies network equipment, the server/hardware and they way the your hosting company configures and tweaks your server to gain maximum performance. When you test the hosting companies home page odds are they have that site on one of there top of the line server tweaked to best of their abilities. So buy test that server one can draw some good conclusions about the network they are on.

Regards,

Anthony

Anthony, thank you very much! I have really learned something here.

Jay

Jay,

Glad I could be of help? and I completely under stand the confusing position your friend is in. I was him years ago.

Best of luck.

Anthony

the funny thing is that im that friend who might have to move from current server bc of need for higher amounts of predicted bw, yet i drink as much as jay does and dont even remember the conversation we had about cogent last night lol

but now, i get it!

thanks fellows.

i just close my eyes and see 20 low level techs drawing these graphs

http://ev1servers.net/english/aboutus/networks.asp

personaly I find it sucking.. the bad way that is :1orglaugh

It reminds me of going into the local Chinese Restaurant and seeing the beautiful photos (in the light boxes on the wall) of the menu that compels me to place an order, but then when my order arrives on a Styrofoam plate something just does not seem to be the same. :(


Anthony

You're an idiot mr e5hosting.

EV1 does NOT have 30 hops but i like how you try and fuck with them. Real classy.

EV1
15 216.200.251.61.ev1.net (216.200.251.61) 135 ms 134 ms 135 ms
16 ivhou-207-218-223-66.ev1.net (207.218.223.66) 150 ms 150 ms 150 ms

You (e5hosting)
17 161.58.156.189 (161.58.156.189) 112 ms 113 ms 113 ms
18 198.65.137.252 (198.65.137.252) 116 ms 117 ms 117 ms

You're an extra hop away but have lower latency.

Is where it hits the EV1 network, how could you count the loop as an additional 14 hops? Ov

12 hstntx1wcx3-pos1-0-oc192.wcg.net (64.200.210.66) 83.823 ms 83.461 ms 82.473 ms
13 hstntx1wcx1-pos9-0-oc48.wcg.net (65.77.93.213) 81.974 ms 82.802 ms 83.488 ms
14 hstntx1wce2-everyonesinternet-gige.wcg.net (65.77.93.54) 87.838 ms 88.488 ms 87.306 ms
15 ivhou-207-218-223-66.ev1.net (207.218.223.66) 88.819 ms !X 88.961 ms !X 88.665 ms !X

11 mg-2.c00.stngva01.us.da.verio.net (129.250.26.202) 90.834 ms 72.040 ms 71.938 ms
12 161.58.156.189 (161.58.156.189) 71.779 ms 71.715 ms 71.282 ms
13 198.65.137.252 (198.65.137.252) 72.948 ms 72.752 ms 72.288 ms

Very close in latency/hops, HOWEVER, ev1 isnt here taking a traceroute and twisting its results so that one ISP looks bad and they look good.

esp. when they have clearly stated they have 4 cogent lines in their mix. pretty big chunk in fact.

ev1 and e5hosting are not in the same type of hosting business, there is no benefit to me proving that NTT/Verio better then Cogent. I used ev1 specialty because they are not in the high bandwidth server solution market and on of the larger users of Cogent.

Regards,

Anthony

Still doesnt change anything about you not knowing how to read traceroutes and reporting back that ev1 had 30 hops when they only had 16. If you cant grasp something as simple as traceroute i'd be very worried hosting with you.

Why didnt you set no timeout values, then they would have had 100 hops or 1000 hops. idiot.

Why dont you point out where your traceroutes hit the cogent network? Ohhh right, they didnt. So how can you say "Cogent is bad, look at EV1" when your traceroutes didnt even hit the cogent link?

Dram,

Your right and it was my mistake 100% and I did not mean to mislead anyone at all.

Regards,

Anthony

Thank you.

Quite honestly it makes no difference to me as i know no one from either company but when you take a shot at another company you better make sure that your facts and data is correct.

Have a great day! :)

the reason cogent is no good sometimes is they have limited peering, and are peered in fewer spots so instead of exiting at a close peering point you have to travel way out. The best example is that when you you are in LA and trying to get to another peer thats also in LA often times you have to go to san jose to get to the peering point which then goes back to LA through the other network. This is what makes latency. 15 milliseconds to go up to san jose plus 15 ms back when you could have peered right to a peering point in LA. If you stay in cogents network they are really fast. When you choose a host, find how many peers they have, ask for ip's in all their networks and trace from multiple sources to all the ip's. If you have any more questions please feel free to icq or email me.

Cazually,

That was explained very well? and anyone looking for a rock solid host should consider www.oc3networks.com in their selection. :thumbsup

Regards,

Anthony

I would just like to apologize to GFY, I?m sorry that I brought an intelligent thread to the table!

Thanks to all.

PS. Anyone want to hit me up, I?m looking for a server to host videos on, I use about 200 Gb a day.

It's not just the peering - it's the routing at Cogent that sucks. We have had all kinds of experiences with them and they really do suck.

Jay - off the subject :) Can you hit me up, ICQ is screwy-dewy today, can't find ya on my list although it insists you're there :)

I don't think the traceroutes from Germany and Argentina have any bearing on whether or not a provider is good for our business.

The vast majority of our signups come from the US and Canada, with EU countries being a distant 3rd and places like Argentina don't matter at all.
Who cares if you have good connectivity to a country where the average person makes $1 a day? Are they going to spend a whole month's salary on a porn membership?


Best thing to do is test out the network for a short period of time and see if your sales go up or down, and then look at the cost/benefit of one provider over another.

:2 cents:

Bingo!

Talk to a Cogent rep, they will tell you the same thing. "Throw us (Cogent) in the mix to lower your overall costs, but don't rely on us (Cogent) as your main provider. As long as your traffic is heading for a major US destination, we (Cogent) are usually quite fast and reliable." Is basically what they said to me.

hey jay. guy from leenks just bought a server from highvelocity.

3ghz p4, 512mb, 2x80gb hardware raid1, 50mbit bw - $530/month

got all that

but they have smaller packages

plus you get an ipod with it, or if you dont want the ipod they will take off the setup fee

P4 3.0 Ghz
512 Ram
80 GB hard drive
6 ips
10 Mbps Unmetered Bandwidth
$115/month, $99/setup

that would be your basic server

20 Mbps Unmetered Bandwidth- add $119
50 Mbps Unmetered Bandwidth- add $399
100 Mbps Unmetered Bandwidth- add $899

512 Ram- add $15/month

120 GB hard drive- add $5/month
200 GB hard drive- add $10/month
250 GB hard drive- add $20/month

DirectAdmin- $9/month
HostingController- $9/month
Cpanel- $35/month
Hsphere- $99 one time setup, $4 per license
Helm- $39/month

Additional Drives
80 GB - $10/month, $30/setup
120 GB- $15/month, $40/setup
200 GB- $15/month, $50 setup
250 GB- $20/month, $50/setup

let me know i will send you the thread, dont wanna post a thread to another board on here.

Thanks guys, virtu mike you are right in a way, what they won't do is change their routes for you, if they have a clogged peering point, they will not adjust it for you. If you are in hosting you know people call and ask, hey we are slow to this network, can you reroute us? we do it all the time. when you are an isp thats what your engineers should do. We host hosting companies, some pretty big ones actually and as the isp we have to watch those peering points. Hey anthony, thanks for the vote of confidence, am waiting to meet you at a show one of these days. For free hosted galleries and things, I think cogent and btn and the other cheap isps are great, hey its free to those mfer's out there, wait little buddy, if you want the real stuff pay for a membership. We have cogent and btn in the mix and they are great when you are in their network, but its a horrible thing to only have em. remember one last thing, hosting is more than good peering, its a relationship, like the guys you do business with, because you are gonna have to talk to them all the time. you can't choose your family, but you can choose your business partners. We all have different strengths. honestly I have talked to virtu mike about maybe gettin some space in ther data center in amsterdam, I like mike, he gave me a kick ass robe in miami. I got the data center in the US with the most peering, hands down by a huge margin, but I might not be your kinda guy and you people would have to talk to me a lot. lol, its all true. Some hosting companies are server guys, they know nothing about peering, but they are kickass with unix or linux. wel all have strengthsand weaknesses, don't just follow someones sig cuz its says hosting, talk to your rep ask questions, you will never regret that.

fris, have him send me an email here jay [at] whtech.net that's not too bad of a deal.

thanks meing!

e5hosting - you didn't analised those traceroutes in a unbiased way to be honest...