You know I hate these sort of posts when people bash providers but well DN has earned this I think. Not to long ago I was praising them recommending them say they had a nice network good servers, great support and all that jazz. I used to get praises from customers saying how great pings were and the game servers for the price they were paying. Customers recommending everyone to us but now we're the big horror story because of DedicatedNOW's packet loss and crappy pings. Over the course of a month the bad pings and packet loss got worse and worse. DedicatedNOW had many what seemed to be lies changing routers to fix problems which never happened I beleive unless they switched it when they had bgp issues. Now how about friday when Nac was finally suppose to have another oc-12 up and running to stop the packet loss or so that was what DN was saying. It never happened not a big surprise to me considering how well DN has been doing lately.

It seems DN wants everyone to beleive the network is fine or giving execuses like the one exchange point was getting attacked and this was the reason for the packet loss. Now I said fine since I assumed the oc-12 was lit by nac on that friday. Wake up the next morning and look still the same packet loss so I'm not idiot and well it was pretty apparent there was no attack since this packet loss lined up to what it has been for weeks I really doubt nyiix would be attacked for weeks. So I said fine I'm going to send DN a nice huge email with all kinds of traces all showing the packet loss so I do so.

I got all the traces using visual traceroute and I was simply told essentially nac can't find any issues use a better trace tool. I reply asking about a good tool to use but never got a reply not a big surprise there. Now it's funny I've tried sending DN many traces with all kinds of utilities and all are ignored or I get a reply from their outsourced support saying it's my problem essentially.

Now when you got many DN customers posting in their network forums of problems still and everytime they ask about oc-12, routers it's basically ignored. I just don't think DN has got their act together right now and won't recommend them until I see an improvement :(

Sorry DedicatedNOW you guys earned this one considering your speeds are slower than unitedcolo right now :(


I would take this as a grain of salt if you don't care about packet loss basically if it wasn't for that DN would be top notch.

Enjoy the post, don't bash me I gave DN plenty of time. Enjoy the review!

Oh, and VeZoZ forgot to mention how they claimed they were going to get Juniper routers, and never did.

He forgot to include how you are basically forced into 2 months of subscription due to a line in their ToS. You them 30 days in advance before canceling a server, thus after the first day you have the server, you will not to be able to stop the charges until the end of the 2nd month. Get this, they charged me for a month of service when the server was taken down 4 days before and told me I couldn't get a refund for a month I CAN NOT USE .

He forgot to include that their support leaves tickets unanswered, gives wrong answers, or says it’s your problem.

He forgot to include that the Remote Reboot Ports that dedicated now were supposed to supply never came out.

He forgot to include that DedicatedNOW wants you to log into ubersmith and their DMS when they won’t give you your log in info. Right after they email bomb you with your password and not your username... lol

He forgot to include that DedicatedNOW only supports 10MBPS Half Duplex even after they agree to give you 100MB Full.

Can you paste a traceroute just for arguments sake?

===================================================
=== VisualRoute report on 25-May-03 11:17:33 AM ===
===================================================

Report for vezoz.sonichosting.net [216.67.237.157]

Analysis: 'vezoz.sonichosting.net' was found in 10 hops (TTL=52). But, problems starting at hop 1 in network "(private use)" are causing IP packets to be dropped.

----------------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
----------------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 24.141.96.145 | xaser.hato1.on.cogeco.ca | * | | | | Cogeco Cable Solutions CGOC-HATO1-1 |
| 1 | | 10.66.32.1 | - | ... | | 11 | x-- | (private use) |
| 2 | | 24.226.0.201 | cgowave-0-201.cgocable.net | ?(Canada) | -05:00 | 13 | x-- | Cogeco Cable Solutions CGOC-RESERVED1 |
| 3 | | 24.226.0.197 | cgowave-0-197.cgocable.net | ?(Canada) | -05:00 | 13 | x-- | Cogeco Cable Solutions CGOC-RESERVED1 |
| 4 | | 66.244.223.225 | ra1sh-pos7-1.mt.bigpipeinc.com | ?(Canada) | -05:00 | 35 | -x-------- | Big Pipe Inc. BIGPIPE-2 |
| 5 | | 66.163.66.9 | rc1sh-ge10-0.mt.shawcable.net | ?(Canada) | -05:00 | 15 | x-- | Shaw Cablesystems SHAW-COMM-BLK |
| 6 | | 66.163.76.158 | rc1hu-pos7-0.ny.shawcable.net | ?(Canada) | -05:00 | 24 | x-- | Shaw Cablesystems SHAW-COMM-BLK |
| 7 | 3 | 198.32.160.20 | nyiix.ge-2-2-0.gbr1.nyc.nac.net | New York, NY, USA | -05:00 | 33 | x--- | Exchange Point Blocks NET-EP-1 |
| 8 | 3 | 209.123.11.150 | 1187.at-0-1-0.gbr1.oct.nac.net | - | | 32 | x- | Net Access Corporation NAC-NETBLK02 |
| 9 | 2 | 209.123.182.243 | - | ... | | 39 | x-- | Net Access Corporation NAC-NETBLK02 |
| 10 | 2 | 216.67.237.157 | vezoz.sonichosting.net | ... | | 45 | x-- | Pegasus Web Technologies PEGASUSHOST |
----------------------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to vezoz.sonichosting.net, average = 45ms, min = 37ms, max = 97ms -- 25-May-03 11:17:33 AM===================================================


===================================================
=== VisualRoute report on 25-May-03 11:49:12 AM ===
===================================================

Report for vezoz.sonichosting.net [216.67.237.157]

Analysis: 'vezoz.sonichosting.net' was found in 5 hops (TTL=59).

-----------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
-----------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 64.21.106.162 | a2800 | ... | | | | Net Access Corporation NAC-NETBLK03 |
| 1 | | 209.123.12.26 | bigtime-loopback.nac.net | - | | 361 | -----x---- | Net Access Corporation NAC-NETBLK02 |
| 2 | | 64.21.100.115 | 1.fa0-0-0.core2.sne.nac.net | - | | 297 | ----x--- | Net Access Corporation NAC-NETBLK03 |
| 3 | | 209.123.11.185 | 1206.at-0-1-0.gbr1.oct.nac.net | - | | 210 | ---x-- | Net Access Corporation NAC-NETBLK02 |
| 4 | 4 | 209.123.182.243 | - | ... | | 117 | -x--- | Net Access Corporation NAC-NETBLK02 |
| 5 | | 216.67.237.157 | vezoz.sonichosting.net | ... | | 30 | x-------- | Pegasus Web Technologies PEGASUSHOST |
-----------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to vezoz.sonichosting.net, average = 30ms, min = 29ms, max = 543ms -- 25-May-03 11:49:12 AM



===================================================
=== VisualRoute report on 25-May-03 11:52:37 AM ===
===================================================

Report for vezoz.sonichosting.net [216.67.237.157]

Analysis: 'vezoz.sonichosting.net' was found in 12 hops (TTL=52).

--------------------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
--------------------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 152.163.0.0 | DEXTER | ... | | | | America Online AOL-BNET |
| 1 | | 10.120.0.1 | - | ... | | 8 | x- | (private use) |
| 2 | | 24.29.32.97 | pos3-1.albynybet-rtr01.nyroc.rr.com | Rochester, NY, USA | -05:00 | 7 | x- | Road Runner ROAD-RUNNER-1 |
| 3 | | 24.29.32.181 | pos1-1.albynywav-rtr01.nyroc.rr.com | Rochester, NY, USA | -05:00 | 7 | x- | Road Runner ROAD-RUNNER-1 |
| 4 | | 66.185.148.137 | pop2-alb-P3-0.atdn.net | ... | | 9 | x- | AOL Transit Data Network ATDN |
| 5 | | 66.185.148.130 | bb2-alb-P0-1.atdn.net | ... | | 9 | x------- | AOL Transit Data Network ATDN |
| 6 | | 66.185.152.195 | bb2-new-P6-0.atdn.net | ... | | 16 | x--------- | AOL Transit Data Network ATDN |
| 7 | | 66.185.152.196 | bb1-nye-P4-0.atdn.net | ... | | 15 | x------- | AOL Transit Data Network ATDN |
| 8 | | 66.185.151.65 | pop2-nye-P0-0.atdn.net | ... | | 16 | x-------- | AOL Transit Data Network ATDN |
| 9 | | 66.185.151.70 | NAC.atdn.net | ... | | 14 | x- | AOL Transit Data Network ATDN |
| 10 | | 209.123.11.150 | 1187.at-0-1-0.gbr1.oct.nac.net | - | | 18 | x- | Net Access Corporation NAC-NETBLK02 |
| 11 | 1 | 209.123.182.243 | - | ... | | 16 | x- | Net Access Corporation NAC-NETBLK02 |
| 12 | | 216.67.237.157 | vezoz.sonichosting.net | ... | | 21 | x- | Pegasus Web Technologies PEGASUSHOST |
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to vezoz.sonichosting.net, average = 21ms, min = 18ms, max = 48ms -- 25-May-03 11:52:37 AM










http://tlcwe.com/trace_1.jpg
This PL has been going on for months and getting increasingly worse.

I don't see any packet loss.

Post your traceroutes as well then :P

PL appears randomly.... right now its not bad.. but at times its up to 15%. DN pretty much is denying it now, even though quite a few customers are complaining about it in their forums.

We wouldn't have lost nearly half of our clients if their wasnt a packet loss problem.

I've been with DN for months now and I'm not going to let a little mishap make me pissed off at their service. How could you have lost half your client base from a little issue like this? I've only had 2 customers actually email me about the issue and both of them were quite understanding. I'm sure if you send out an email explaining the issue, they will understand.

Just a quick note before matt comes on to discuss the other pending issues we never lied in reference to the new route refer to the post in OUR forums
http://forums.dedicatednow.com/viewtopic.php?t=1036

Which clearly outlines the time of the router swap over.

The additional oc12 was supposed to be live last week which was obviously delayed due to the carrier involved in running the loop.

And yes at that time at NYIIX there was an attack causing PL, for customers, whose traffic came of NYIIX peers. I can even show you the NAC trouble ticket to prove it. We never implied that was the cause of the ongoing PL.

Also all people who purchased or who were given RRP ports should have all the info if not email sales@dedicatednow.com.

And the best tool for showing traceroutes is straight unix traceroute command easy to read, striaght forward doesn't get messed up in email.


Originally posted by VeZoZ
You know I hate these sort of posts when people bash providers but well DN has earned this I think. Not to long ago I was praising them recommending them say they had a nice network good servers, great support and all that jazz. I used to get praises from customers saying how great pings were and the game servers for the price they were paying. Customers recommending everyone to us but now we're the big horror story because of DedicatedNOW's packet loss and crappy pings. Over the course of a month the bad pings and packet loss got worse and worse. DedicatedNOW had many what seemed to be lies changing routers to fix problems which never happened I beleive unless they switched it when they had bgp issues. Now how about friday when Nac was finally suppose to have another oc-12 up and running to stop the packet loss or so that was what DN was saying. It never happened not a big surprise to me considering how well DN has been doing lately.

It seems DN wants everyone to beleive the network is fine or giving execuses like the one exchange point was getting attacked and this was the reason for the packet loss. Now I said fine since I assumed the oc-12 was lit by nac on that friday. Wake up the next morning and look still the same packet loss so I'm not idiot and well it was pretty apparent there was no attack since this packet loss lined up to what it has been for weeks I really doubt nyiix would be attacked for weeks. So I said fine I'm going to send DN a nice huge email with all kinds of traces all showing the packet loss so I do so.

I got all the traces using visual traceroute and I was simply told essentially nac can't find any issues use a better trace tool. I reply asking about a good tool to use but never got a reply not a big surprise there. Now it's funny I've tried sending DN many traces with all kinds of utilities and all are ignored or I get a reply from their outsourced support saying it's my problem essentially.

Now when you got many DN customers posting in their network forums of problems still and everytime they ask about oc-12, routers it's basically ignored. I just don't think DN has got their act together right now and won't recommend them until I see an improvement :(

Sorry DedicatedNOW you guys earned this one considering your speeds are slower than unitedcolo right now :(


I would take this as a grain of salt if you don't care about packet loss basically if it wasn't for that DN would be top notch.

Enjoy the post, don't bash me I gave DN plenty of time. Enjoy the review!

I don't know how it is un the US, but dedicatednow's network is the fastest one for us europeans. I have been with them since november, and besides a couple of glitches, the experiencie has been wonderfull.

Cheers :)

I don't think DN deserves a bashing. I wasn't going to reply to this, but my weekly Alertra report came in and thought it was funny in a sick sort of way. One server is DN and one is Nocster :D

Report from 05/19/2003 - 05/25/2003

DedicatedNOW Server
Device PING
Protocol PING
URL ping://216.xx.xxx.xx
Frequency Every 10 Minutes
Status UP Since 05/15/2003 05:32:39

Date Outages Downtime Uptime Avg Time
05-19-2003 Mon 0 0 hrs, 0 mins, 0 secs 100.000% 5.100 secs
05-20-2003 Tue 0 0 hrs, 0 mins, 0 secs 100.000% 6.521 secs
05-21-2003 Wed 0 0 hrs, 0 mins, 0 secs 100.000% 5.724 secs
05-22-2003 Thu 0 0 hrs, 0 mins, 0 secs 100.000% 1.716 secs
05-23-2003 Fri 0 0 hrs, 0 mins, 0 secs 100.000% 4.468 secs
05-24-2003 Sat 0 0 hrs, 0 mins, 0 secs 100.000% 5.052 secs
05-25-2003 Sun 0 0 hrs, 0 mins, 0 secs 100.000% 5.653 secs
Week Summary 0 0 hrs, 0 mins, 0 secs 100.000% 4.957 secs

Uptime Report | Alert Log | Check Log | Device Setup

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

Nocster Server
Device PING
Protocol PING
URL ping://64.xxx.xx.xx
Frequency Every 10 Minutes
Status UP Since 05/23/2003 20:54:15

Date Outages Downtime Uptime Avg Time
05-19-2003 Mon 0 0 hrs, 0 mins, 0 secs 100.000% 6.353 secs
05-20-2003 Tue 2 1 hrs, 38 mins, 54 secs 93.132% 9.388 secs
05-21-2003 Wed 1 0 hrs, 19 mins, 18 secs 98.660% 6.489 secs
05-22-2003 Thu 0 0 hrs, 0 mins, 0 secs 100.000% 0.848 secs
05-23-2003 Fri 1 4 hrs, 19 mins, 22 secs 81.988% 8.683 secs
05-24-2003 Sat 0 0 hrs, 0 mins, 0 secs 100.000% 5.147 secs
05-25-2003 Sun 0 0 hrs, 0 mins, 0 secs 100.000% 5.175 secs
Week Summary 4 6 hrs, 17 mins, 34 secs 96.254% 6.153 secs


Since I am a new DN customer, this being my first month with them, I have had the network and support response times under the microscope and I haven't seen any type of problems that would warrant a "I hate to bash but they deserve it" thread.

I have access to my reboot port, I haven't had any support tickets unanswered, I didn't get mailbombed with DMS login info, I did get my billing login and had no trouble, and everything that DN promised when the delivery of the server was delayed has been supplied. I'm happy so far.

Comparing DN to Nocster probably isn' t a good indication given the massive IP blocks and record service level of Burst.

The DN service employs a heavy quota of Cogent (as opposed to the Pegasus network which is all goodness) from our experience. While we've rarely had issues with the ping and traceroutes, their IP allocation does contain a number of 'serial spammers'. After complaints of NAC the prime candidate of these SPEWS listing seems to be gone now, but the fact it took a whole /24 to get their attention rather than killing the spammer outright at the first IP is a worry.

NAC, and therefore Pegasus and their 'mate's rates' provider DN, need to do a little house cleaning in my opinion to clean the IP allocations they provide.

It's all fine and good to hammer spammers within your own servers but when the 'guy next door' lets these clowns pump out junk, and create a wider IP block then it's cause for concern.

I have had a server with DedicatedNow, since there first batch in November I believe.

There was some initial growing pains with support, but I have been very happy recently with there support and network. There have been some occaional network issues, but they are making it clear to the customers what they are doing to resolve it.

I have and will continue to recomend them.

Originally posted by VeZoZ

It seems DN wants everyone to beleive the network is fine or giving execuses like the one exchange point was getting attacked and this was the reason for the packet loss. Now I said fine since I assumed the oc-12 was lit by nac on that friday. Wake up the next morning and look still the same packet loss so I'm not idiot and well it was pretty apparent there was no attack since this packet loss lined up to what it has been for weeks I really doubt nyiix would be attacked for weeks. So I said fine I'm going to send DN a nice huge email with all kinds of traces all showing the packet loss so I do so.


An exchange point was getting attacked? I’ve never heard of “an exchange point getting attacked”. How do you attack an exchange point? Perhaps an attack was traversing THROUGH the exchange point, but I highly doubt there was an attack launched at the exchange point itself.

Also, I haven’t seen any valid reports of packet loss in the past month due to a problem with the NAC part of the network. The latest network event that I recall of was problems with WilTel. NAC has an OC-12 into WilTel’s New Jersey ATM cloud, which gets backhauled to their routers in New York City. The packet loss was due to saturation on behalf of WilTel’s network. You also need to keep in mind that NAC utilizes proactive filters on every ingress/egress point on their network, which filters rate-limit ICMP and other protocols.

Originally posted by VeZoZ

I got all the traces using visual traceroute and I was simply told essentially nac can't find any issues use a better trace tool. I reply asking about a good tool to use but never got a reply not a big surprise there. Now it's funny I've tried sending DN many traces with all kinds of utilities and all are ignored or I get a reply from their outsourced support saying it's my problem essentially.


Traceroutes are a horrible tool to use for checking network metrics. It’s great at showing you the path, but nothing really more than that. Also, some of the hops traversing over the trace might be higher than normal, this could be due to the fact that most router vendors prioritize ICMP/UDP echo lowest. An example of this would be tracerouting through AT&T’s network. If you pass through a *.tbr*.att.net router, which is an Avici, you may see extremely high latency or even perhaps “packet loss”. The packet loss isn’t really loss; it’s just your traceroute program’s TTL. Sometimes the Avici reports latency >5000ms, which might show up as a timeout to you, when it’s just merely cosmetic.

Also, you need always remember that routes may not be symmetrical. I.E. The route from your house to your server might not be the same as from your server back to your house. This can be especially true with “DCJN” customers.

[QUOTE]Originally posted by 2uantuM
Oh, and VeZoZ forgot to mention how they claimed they were going to get Juniper routers, and never did.
.
[QUOTE]

Where are you going with this? What’s your point? I believe DedicatedNow had some issues with their Cisco router, which appears to have been resolved. The problem was due to a software bug in Cisco’s IOS code. DedicatedNow worked with Cisco in finding a stable release and I think everything has been find since then.

We are still getting packet loss no matter how much you wanna flame vezoz.

thats what you get for being a cheap ass CS host

Greetings folks,

If you been wondering about this. Then digest this. We have a number of servers over at DN as well, and then last week, we have a server that been subjected to massive DoS attack on port 22.

So..I sent a ticket to support to get them to look into blocking it at the router. Instead, they go and change the port of SSH on our server and said that is pretty much it for now. I got little upset and complained about it. The night crew said they are working on it so I figures that is good and well. Then..next day, I get the email from tech support by the name of Jay Silver, who apparently is the CEO of DN. His crappy response is this: "What do you want us to do about it?"

Now...that is not the right answer we are expected to get from tech support. I got really upset and started complaining that I will get his ass canned due to his sub-standard tech support responses. Well....during all that exchanges, he never made clear that he, Jay Silver, is the CEO of the company and working as tech support. I expected him to give much better response than this lame "What do you want us to do about it?". According to their policy, it is their responsbility to deal with the problem. But they haven't done much til I did my homework and fixed it myself. But did they do anything on this problem? No. That problem, the DoS attack lasted nearly 3 days while they sat on it. That shows so much about their tech support and Jay's non-stellar tech support.

Well, sounds like you got silver rated support from Mr. Silver, maybe we should find a company with their CEO's last name of Platinum, and you'll get good support.... :rolleyes: sorry, just trying to bring some humor to the situation.

ahhhh, where to begin......?

2uantuM Nobody is held to a contractual period with us. It is at my discression for cancellations, but to date, NOBODY has ever been held to the 30 day terms, however, I do request that people give enough notice to remove all areas from their billing. If memory serves me correct, you tried to cancel a few days before you billing cycle was due. it got charged, you alerted me to the issue, and I was looking into the matter for you. Every person who signs up on the site clicks a link denoting that they've read and understood the terms and conditions of our service. You clicking that box meant that you had done so. Logins to DMS and Ubersmith were mentioned in our forums, as well as RRP's, deliver of, and what to do if you needed your logins. If you were "mailbombed" then you would have also received the apology letter sent out 15 minutes after it happened, and the follow up post about resolutions to the situation and how to request your information.

Elik,

The point at which Jason took over, was after your comments became rude and you began berating our staff. I was requested to intervene because of your attitude, and not fully understanding of our situation and what you were requesting us to do. Our techs tried to assist you as they could, but what you were asking for was impossible to do. As noted by your e-mail last Friday to me, it's amazing how you change your position publicly vs. privately.

Our forums, open to customers, have been well explained each step of the way, what issues we were facing, and what was being done to correct them. No customer has been lied to, or kept out of knowledge of what steps we are and have taken. At each stage where we corrected an issue, we alerted clients, and asked them to contact us with any remaining issues. We are awaiting final completion of the OC12, which to my meeting with one of the owners of NAC was being done last Friday.

Anyway, enough out of me, I need to get back to work now.

Originally posted by Mrdredd
thats what you get for being a cheap ass CS host

well that was mature of you to say.

We're cheap? Atleast we can keep our site up and don't go use cogent :P

It had to be done :)

Oh and traceroutes may be bad but packet loss doesn't lie when you are playing say counter-strike and seeing flucations of packet loss or your website is loading or your status pages are saying services are down because the packets didn't make it. DN I would still recommend for most I indeed did like their service until recently and most likely will approve of it some time soon. The bandwidth is really out of their control which sucks :( I just wish they would like push at nac a little more or something it's just been dragging on.

I'm at DN and I see some packet loss / latency :(

Originally posted by VeZoZ
We're cheap? Atleast we can keep our site up and don't go use cogent :P


OMG I see cogent, the world is over... i love all these children complaining about cogent. I didn’t ever see any real complains about NetRail or PSINet, but the second they s/psi/cogentco/, etc, boom, the whining comes pouring in. cogent has come a long way and I give them much credit.

Well he was talking about counter-strike servers and I really doubt cogent would qualify as a good bandwidth provider for gameservers.

Originally posted by sjs
OMG I see cogent, the world is over... i love all these children complaining about cogent. I didn’t ever see any real complains about NetRail or PSINet, but the second they s/psi/cogentco/, etc, boom, the whining comes pouring in. cogent has come a long way and I give them much credit.

Glad to see someone finally agrees with me on this one. I'm a big fan of Cogent and their awesome service.

Originally posted by VeZoZ
Well he was talking about counter-strike servers and I really doubt cogent would qualify as a good bandwidth provider for gameservers.

You'd be surprised, it suits it quite nicely.

We have many servers at DN and have seen no packet loss at all.
I think the service that Matt provides to us is well worth what we are paying for the servers.

I have to admit we have never needed to use their tech support, but the network has been very steady for serveral months.

No packet loss on any traces from here.

One server has been experiencing major packet loss today, so much so that it drops off the network for a while. They confirmed network issues are the root of the problem and they are working on solving it. At first I thought the server was in a reboot loop, I couldn't get the logs before I lost access...it came back, and again I couldn't grab the logs before I lost access... hopefully this gets resolved soon...

Originally posted by SolidJoe
Glad to see someone finally agrees with me on this one. I'm a big fan of Cogent and their awesome service.

How is their service awesome?

They get packet loss traveling across their OWN network. What does that mean?

You like them because they are cheap, because you'd be crazy to choose cogent over most any other provider.

Originally posted by ViAdcK
I don't know how it is in the US, but dedicatednow's network is the fastest one for us europeans.There are others that are as fast and that perform better (non-cogent)... you just haven't seen them yet. :D

Originally posted by clockwork
How is their service awesome?

They get packet loss traveling across their OWN network. What does that mean?

You like them because they are cheap, because you'd be crazy to choose cogent over most any other provider.

Don't think for me. I like them because with my home connection I get excellent responses with Cogent. I've also found that nationwide on my servers that use Cogent they have performed very well and been very stable. I don't recieve any packet loss across the United States, so I don't know where your figures come from. Please don't ever speak for me again.

No packetloss but high pings.


15 235 ms 250 ms 250 ms lax1-br1-p2-1.gnaps.net [199.232.44.5]
16 312 ms 328 ms 328 ms 199.232.44.29
17 328 ms 344 ms 328 ms ash1-br1-g1-1.gnaps.net [199.232.44.34]
18 297 ms 313 ms 297 ms 0504.ge-0-0-0.gbr1.ash.nac.net [209.123.24.173]

19 313 ms 312 ms 313 ms 0195.at-0-1-0.gbr1.oct.nac.net [209.123.11.138]

20 312 ms 313 ms 312 ms 209.123.182.243
21 1109 ms 578 ms 797 ms XXXXXX.XXXXXXX.XXX [66.246.54.XXX]

Trace complete.

C:\>

Reply from 66.246.54.XXX: bytes=32 time=1266ms TTL=39
Request timed out.
Request timed out.
Reply from 66.246.54.XXX: bytes=32 time=672ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=657ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=516ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=329ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=313ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=313ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=329ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=844ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=625ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=1157ms TTL=39
Request timed out.
Reply from 66.246.54.XXX: bytes=32 time=1282ms TTL=39
Request timed out.
Reply from 66.246.54.XXX: bytes=32 time=1469ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=360ms TTL=39
Reply from 66.246.54.XXX: bytes=32 time=875ms TTL=39

Keep in mind my normal pings are 300

Going over at&t, no packetloss and average ping times of 43ms.

I should mention then that my normal ping is 18 ms.