Going, Going, Gone

PFunk · #1 07-18-2006, 10:31 AM

I am leaving HG and figured that I should leave a review on my way out. Why, you ask? Because HG is still a great hosting solution, but it's not the solution for me. I used a database intensive gallery and messageboard and with the limitations imposed by HG, it made it an unpleasant experience. I will say that 25 concurrent connections is a bit low.

Many of you will say I should upgrade to a 'larger' plan, but I only had a personal website. I was using 3GB of Bandwidth a month on average. That's not close to the 100GB I was allotted. Why should I upgrade when I was only using 3% of my BW.

It was good while it lasted, but I had to move to a provider that doesn't impose the tight limitations that HG did.

***GatorBrent*** · #2 07-22-2006, 11:13 PM

Did this limitation affect you? If you did it was a problem with your coding. Forums with 100's of users online at a time don't hit the 25 simul connections.

PFunk · #3 07-26-2006, 03:04 PM

I expected nothing less than for you to blame my 'coding' skills, Brent, even though I used a fantastico installed gallery and messageboard.

***GatorBrent*** · #4 07-26-2006, 03:43 PM

What is your ticket number on the issue so that I can review it?

PFunk · #5 07-27-2006, 04:38 PM

I'm not sure of the ticket numbers because it was before the change to the new ticket system or they have been deleted/archived. Plus, I'm only seeing low/medium tickets on the Kayako list. Not sure where the critical ones went. Guess that is another one of my coding errors.

What would that accomplish? It won't bring me back. Also, I can't give you a list of 'ticket numbers' for all the times I contacted live support because something was going on.

Examples:
Server Load over 30.00
/var was full so my stats were not updating. I gave up on webalizer because I was tired of filling out tickets to have it updated.
imapd was stopped
httpd was stopped

When I did do 'tickets', I usually just heard that everything was working. Submitted a critical ticket that httpd was stopped and 30 minutes later, I was informed that everything was working fine like I was a complete idiot for even submitting it. I would hope that a critical error would be resolved by the time 30 minutes has passed. Especially when httpd was not running. No explaination given about WHY it was down.

I repeatedly(5 or more times) asked live support and email support to put something in the Knowledgebase about the concurrent mysql connection limit. This never happened. It still hasn't. Email limits are there, but why publish something about mySQL that might impact a site as much as email limits.

Everything IS a coding error regardless of HG responsibility in the matter or the lack thereof.

HG used to be well ahead of the pack when it came to hosting. It's not that other hosting providers are catching up, it's that HG is failing in it's dedication it once had to it's customers. You might say $15 a month isn't a big deal. What happens when that is multiplied and word of mouth is that HG might not be the best option out there. It's not the positive things that a hosting company does. That is expected. It's the negative and you know this. That's why this forum (Customer Reviews) can only be replied to by the person that started the thread or a staff member. Wouldn't want a long thread of how poorly HG is doing. Limit the negativity to just one person so it sounds isolated when in reality, it's probably not.

As owner of HG, you should hold yourself to higher standards then your other staff, but you are just a quick to pull the 'customer coding' trigger as anyone else. I've very disappointing to see you blame your customer's first, seek answers second.

I happy where I am now. I've had no reason to contact support since their services seem to stay running. Regardless, I won't be back here.

***GatorBrent*** · #6 07-31-2006, 01:45 PM

I'm being a 100% honest with you. If the limits affected all scripts as your saying we would be flooded with complaints, and are phones would be going off the hook.

Without a ticket number it's hard to comment directly, bus there's 100's if not thousands of people using the very scripts your talking about without any issues on our servers. We migrated to the new ticket system about 6 months ago so maybe the issues you're talking about did exist at the time on your server, but there's definitely nothing going on as you experienced now. We are not the same company we were 6 months ago thanks to the help of a few new top gun admins.