they do not respond to support and don't know what they are doing. i've
tried everything with them. i havn't heard anything from them in over a
week (they claim 48 hour response). i've even escalated to the
president, three times, and still heard nothing. their 'live support'
feature is a fraud. it is NEVER staffed.
stay away from webhosting.com
i'd love to hear from others with similar experience. they've cost me a
lot of time and money and i intend to get it back.
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
The only way I got a response from that company was to cc: my rant on the
usenet to Jesse Rasch [j...@webhosting.com]. He may be the president of the
company or some such thing. He quickly responded that he wanted to have a
"pro-active discussion", but I had already left them. Let him know you've
taken your gripes public and you may get a response.
My favorite dealing with them: After being informed that they required 30
days notification before cancelling service, and that the notification had
to be a hardcopy (not email), I sent their accounting dept. an email asking
"I did fax a hardcopy notice of my cancelation of service. Please let me
know if you did or did not receive that request." *Five* days later I got a
one word response: "Yes". It wasn't a yes/no question! Oh well, I cancelled
the credit card they were billing to and moved on.
Ed Callahan
li...@envstat.com
<kcmck...@hotmail.com> wrote in message
news:7rnp6r$35k$1...@nnrp1.deja.com...
webhosting.com got me so frustrated with their lame support, that I
went and bought a $3000 rack mount server and pay $500/mo for dedicated
access with above.net. I think webhosting.com should take a lesson
from above.net, they are top notch all the way.
In article <7rnp6r$35k$1...@nnrp1.deja.com>,
kcmck...@hotmail.com wrote:
> i made a big mistake hosting with webhosting.com
>
> they do not respond to support and don't know what they are doing.
i've
> tried everything with them. i havn't heard anything from them in over
a
> week (they claim 48 hour response). i've even escalated to the
> president, three times, and still heard nothing. their 'live support'
> feature is a fraud. it is NEVER staffed.
>
> stay away from webhosting.com
>
> i'd love to hear from others with similar experience. they've cost me
a
> lot of time and money and i intend to get it back.
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
Sent via Deja.com http://www.deja.com/
Before you buy.
No answers to support, etc etc..
The worst was when I wanted my money back - they delayed the entire
process so I wasn't "eligible" anymore for the money back guarantee.
God thing my bank saw my point of view, and I promptly got a partial
refund.
Yes partial ... It took me another month to get the remaining amount
of my money back.
Webhosting.com - terrible company with a very good domain name.
Anyway, now I'm with vservers.com - low cost, great service, and get
this:
average response time of tech support: 15 minutes (even at 2AM).
I'm sticking with them until I have to colo
Just a week after signing up with them I too have
also concluded webhosting.com is awful, if not
unethical. They sent us an introductory letter
with a user name/password a week ago and it still
doesn't work. After being put on hold for a total
of 4 hours or so we got through to a human
twice. They can't do anything - they can't even
set an account password. After asking for your
email address they then ask you to FAX !! your
problem on your letterhead to some number.
There are a couple of sites ranking web sites -
like tophosts.com which represents itself as
independent - that put webhosting.com at the top
of their list. Are they part of a scam to get
customers for webhosting.com? And is
webhosting.com located in Canada so that it can
more easily rip off US customers?
I plan to cancel ASAP.
Webhosting is horrible. I tried them once for about ten minutes
literally. As soon as my account was active, I noticed that i could not
CHMOD files in my virtual FTP directory. The tech support told me it was
because my FTP client did not support it. When I told them that I was
using command line FTP to issue the CHMOD command, they still didn't get
it. So I offered to email them a log of the session where the server
responded with the "Not Allowed". They responded to the mail with, "your
FTP client doesn't support CHMOD". Arrrrrgggghhhhhh!!!