I have read a good deal of posts that have had positive information about Site5 and Wizards Hosting. I found this other site...Next Generation Web Hosting, (www.nghosting.com) on my own and I was wondering if anyone has used them. Or, could give me positive or negative things they have heard about them.

I have been given the responsibility of finding a new hosting company for my office, and I am looking to create a list of pros and cons to give to my boss, along with my recommendation.

Thanks in advance for the help.

I think Jay from NG has popped in and out of here in the past.

Quick link:
(From HostSearch reviews)
http://www.hostsearch.com/showcomment.asp?Companycode=2328

I personally have had nothing but bad luck with the connection to my site at site5.com . The handoff at Site5 and their major access NAC.NET is disgusting to say the least. We have been complaining now for over 5-months about it to Site5, even NAC.NET, they all blame it on roadrunner. I don't know how true this is or what the solution is but nothing has been resolved. Believe me, this is a huge audience AT&T Roadrunner cable users, they all will have a problem connecting to your site through this handoff. Today it running as usual at a 90% packet loss at the NYIIX.PEER.NAC.NET, this is everyday!


Here is todays ping results .. Last column is number of packets loss - right now 97 sent 88 loss!

Node High Low Avg Total Loss

3 67 7 17 38 0
4 28 8 11 38 0
5 55 15 19 38 0
6 38 16 18 38 0
7 83 16 20 38 0
8 108 81 90 38 0
9 141 81 83 38 0
10 83 19 21 72 64
11 307 84 88 37 0
12 141 84 90 37 0
13 144 84 89 37 0


Starting at node3 here is the trace

3 2 1 24.31.61.45 33.967N 118.242W pos5-0-0.frsnca2-rtr1.we.mediaone.net

4 3 1 24.130.0.5 33.967N 118.242W pos4-0-0.frsnca1-rtr1.we.mediaone.net

5 3 1 24.130.0.49 33.967N 118.242W hss4-1-0.cypsca1-rtr1.we.mediaone.net

6 4 1 24.165.128.69 33.967N 118.242W srp4-0.lsanca1-gsr2.we.mediaone.net

7 5 2 24.218.189.188 - labrt03-labrt01.rr.com

8 5 - 24.218.190.202 -

9 5 - 24.218.188.54 -

10 6 3 198.32.160.20 - nyiix.peer.nac.net

11 7 3 209.123.11.181 - a1-1-0-2020.core1.oct.nac.net

12 8 3 207.99.21.35 - vlan1.msfc1.oct.nac.net

13 9 4 64.21.152.4 41.052N 74.741W www.site5.com


Yes, I have another open ticket with Site5 from yesterday morning that has yet to be answered..

:angry:

I try to contact the sales departament for 4 days, and they never answer.

Wow!

No, they usually respond pretty quickly but it's been getting worse lately. I'm suprised they are not jumping on a sales question..

I've noticed that sometimes when I go out to site5.com to look at their plans I cannot load their home page. I've left the browser window open and carried on in another window and 10-15 minutes later their page still hadn't loaded. I don't get this every time but it happens a lot.

jericho

they all blame it on roadrunner. I don't know how true this is or what the solution is but nothing has been resolved. Believe me, this is a huge audience AT&T Roadrunner cable users, they all will have a problem connecting to your site through this handoff. Today it running as usual at a 90% packet loss at the NYIIX.PEER.NAC.NET, this is everyday!

And Brad - they are probably right. I myself am on @Home's cable network and although it takes me 19 hops to site5.com its only a ~45ms roundtrip. Believe me, we used to be hosted on site5 [we run our own hosting company now] and we _rarely_ had a connection problem with them.
You need to understand that cable modem providers have a habit of routing all their traffic around through the same central routers. For example - I live 3 miles away from Purdue University - anytime I connect to Purdue (through @Home) I get routed to indy to cleveland to chicago to indy and back to Purdue. It usually takes ~12 hops just to get back to them. Pretty sick, huh?

Just for reference I have posted my traceroute to site5.com:
archimedes:~# traceroute site5.com
traceroute to site5.com (64.21.152.4), 30 hops max, 38 byte packets
1 192.168.0.10 (192.168.0.10) 0.960 ms 0.966 ms 0.754 ms
2 10.71.1.1 (10.71.1.1) 12.905 ms 14.888 ms 37.261 ms
3 bb1-fe1-0.lafayt1.in.home.net (24.4.160.1) 10.509 ms 12.354 ms 9.971 ms
4 c1-se6-2.iplsin1.home.net (24.7.74.125) 13.107 ms 12.307 ms 13.582 ms
5 c1-pos9-0.clevoh1.home.net (24.7.65.246) 20.222 ms 44.962 ms 22.323 ms
6 c1-pos2-0.chcgil1.home.net (24.7.64.173) 49.335 ms 33.421 ms 28.927 ms
7 ATM3-0.BR2.CHI2.ALTER.NET (204.255.168.1) 30.740 ms 32.359 ms 32.658 ms
8 0.so-5-1-0.XL2.CHI2.ALTER.NET (152.63.67.246) 33.531 ms 42.643 ms 36.232
ms
9 0.so-7-0-0.XR2.CHI2.ALTER.NET (152.63.67.134) 39.986 ms 45.959 ms 30.960
ms
10 0.so-3-0-0.TR2.CHI2.ALTER.NET (152.63.15.134) 29.518 ms 30.004 ms 59.558
ms
11 126.at-5-1-0.TR2.NYC9.ALTER.NET (152.63.1.138) 49.234 ms 58.645 ms 42.601
ms
12 286.ATM6-0.XR2.NYC4.ALTER.NET (152.63.21.141) 44.899 ms 42.749 ms 43.518
ms
13 188.ATM7-0.GW7.NYC4.ALTER.NET (152.63.25.109) 42.182 ms 44.167 ms 48.304
ms
14 internap-gw.customer.alter.net (157.130.50.86) 85.111 ms 46.984 ms 42.197
ms
15 border11.ge3-0-bbnet2.nyc.pnap.net (209.191.128.145) 47.664 ms 45.730 ms
43.879 ms
16 nac-1.border11.nyc.pnap.net (209.191.130.94) 57.808 ms 50.231 ms 49.588 m
s
17 a1-1-0-2020.core1.oct.nac.net (209.123.11.181) 65.978 ms 55.731 ms 65.510
ms
18 vlan1.msfc1.oct.nac.net (207.99.21.35) 45.606 ms 46.348 ms 50.147 ms
19 64.21.152.4 (64.21.152.4) 66.310 ms 47.366 ms 45.778 ms

Originally posted by Brad
I personally have had nothing but bad luck with the connection to my site at site5.com . The handoff at Site5 and their major access NAC.NET is disgusting to say the least. We have been complaining now for over 5-months about it to Site5, even NAC.NET, they all blame it on roadrunner. I don't know how true this is or what the solution is but nothing has been resolved. Believe me, this is a huge audience AT&T Roadrunner cable users, they all will have a problem connecting to your site through this handoff. Today it running as usual at a 90% packet loss at the NYIIX.PEER.NAC.NET, this is everyday!


Yes, I have another open ticket with Site5 from yesterday morning that has yet to be answered..

:angry:
Hi All,

There is actually another series of posts about this same issue from Brad available at the following URL:
http://webhostingtalk.com/showthread.php?threadid=10938&highlight=NAC.net

Essentially, this problem is out of our hands at this point. The NAC network admins have attempted to contact the administrators of the other problematic networks, to little avail.

Brad, we are aware that you have opened a new ticket on this issue (which you have submitted multiple tickets on in the past), however at this juncture we have no resolution for you, as it depends on a response from a great many other people - and a major network change like this doesn't just happen overnight (or even over a period of 5 months).

Once again, we are aware of this problem, and have done (and are still doing) everything in our power to see that is resolved - unfortunately not all parties involved consider it to be as high of a priority as we do. There is little that we can do about this.

We do, however, appreciate your determination and perseverance in sticking with us even though you are experiencing this problem. ;)

Best Regards,
Matt Lightner
mlightner@site5.com

No, they usually respond pretty quickly but it's been getting worse lately. I'm suprised they are not jumping on a sales question.

As I'm shopping around for a dedicated server I contacted Site5 a few days ago with a presales question. It was answered within a few hours.

Site5 is on my shortlist.

Jan Derk

Matt,

I understand your situation but not talking about it does nothing at all, I've been pretty dam persistant about it because I like your hosting service, you provide a quality setup and I'm willing to pay more for it. I'd love nothing more than to see this resolved and not have to talk about it anymore, it's a pain in the rear. But I've never heard anything at all about a major network change being needed on this, only that were aware of the problem, we've Identified it's location and we're not getting any support. I know it's out of your hands at this point, it's just frustrating.

I'd love to have a dedicated server with you right now, you'd be my first choice but this problem keeps stopping me from selecting you. I need one right now for another site of ours and will be purchasing tomorrow from somebody.

Let me know if you can help in any way ..

Brad

Brad, have you contacted RR at all? Based on my own research, tracing to NAC is still one of the best connections, from both a latency and loss standpoint. Unfortunately, RR do not have a publicly-available trace function to poll against their POPS around the country. Perhaps if you can find a contact for their network weenies, they'd be able to do some testing that might show why those one or two modes are consistently failing to properly hand off. Matt's right - there isn't a lot they can do about this one. I don't know if I would term it a major network change, unless RR was willing to swap out an entire router, which I doubt. However, a check of the routing tables and a probe on the router(s) would be in order.