The worst asp.net host

[David K]

Whatever you do, don't try aspwebhosting.com . One day recently I got
an email from them saying that my account had been suspended for using
too much cpu time. There was no further explanation. Those bastards
took my site offline, removed my email account, blocked my ftp access
and even refused to let me get a backup of sql-server data. I sent
them an email (using a yahoo account since they had shut down my own
server) to ask what I could do to get my data. Rather than answer my
email they simply put me their BLOCK list. All of my emails are now
automatically bounced. I only sent them one email and it was very
polite. My website is gone. My data is gone. All of my files are
gone. The loss of time and effort combined with damage to my business
is unforgivable

[Trevor Best]

On 12 Sep 2003 23:19:19 -0700 in comp.databases.ms-sqlserver,
st**********@yahoo.com (David K) wrote:

Whatever you do, don't try aspwebhosting.com . One day recently I got
an email from them saying that my account had been suspended for using
too much cpu time. There was no further explanation. Those bastards
took my site offline, removed my email account, blocked my ftp access
and even refused to let me get a backup of sql-server data. I sent
them an email (using a yahoo account since they had shut down my own
server) to ask what I could do to get my data. Rather than answer my
email they simply put me their BLOCK list. All of my emails are now
automatically bounced. I only sent them one email and it was very
polite. My website is gone. My data is gone. All of my files are
gone. The loss of time and effort combined with damage to my business
is unforgivable

IANAL but I think it would be illegal for them to deny you access to
your data.

--
A)bort, R)etry, I)nfluence with large hammer.

(replace sithlord with trevor for email)

[Support]

Indeed we did take the customers site off-line. This new customer
chose a shared ASP.NET hosting plan, a starter plan to be exact,
however, his site was using 80% to 90% of the processing time on a
multi-processor SQL Server machine that typically supports 200+
customers using an average of 18% of the servers CPU time.

What the customer is failing to tell you is the following:

A) Customer recently signed up for service, from Japan and provided an
international telephone number

B) We called this customer in Japan and left a message on the
answering machine describing the problem and asking him to call us
ASAP

C) The customer provided a phony US 800 number as the technical
contact and calling that 800 number results in a message that says
"Not in Service".

D) We emailed the customer and notified him of the issue, yet he took
no action

E) The customer claimed we blocked him, however, he may be sending
email from a MAPS blacklisted IP block

F) The customer could have sent email using the online email interface
we provided. It is NOT blacklisted. He did not.

G) The customer could have opened a ticket using our online technical
support system. He did not.

H) The customer could have called our support number which is answered
24 hours. He did not.

We are not in the business of disrupting customers web sites, however,
we will not allow one customers application to consume all of the
servers resources at the expense of other customers sharing those
resources. In some cases, drastic situations require drastic action.
In this particular case, the customers application was crippling the
server and I believe the customer was most likely aware that his
application could not be supported on a shared SQL Server.

You may be surprised by the number of people that move poorly written
applications from one host to another always complaining that it is
the hosts fault. They never tell anyone about their misgivings, only
about how terrible the host is for taking some action to protect their
customers and systems.

We are an excellent hosting company. We provide excellent services,
guaranteed performance and maximum uptime. Just ask any one of the
other customers that were sharing that particular SQL Server. I would
bet everyone of them were pleased that we did not allow this customers
application to continue to cause their applications to fail due to
timeouts and connectivity problems.

ASPwebhosting.com

[Support]

Indeed we did take the customers site off-line. This new customer
chose a shared ASP.NET hosting plan, a starter plan to be exact,
however, his site was using 80% to 90% of the processing time on a
multi-processor SQL Server machine that typically supports 200+
customers using an average of 18% of the servers CPU time.

What the customer is failing to tell you is the following:

A) Customer recently signed up for service, from Japan and provided an
international telephone number

B) We called this customer in Japan and left a message on the
answering machine describing the problem and asking him to call us
ASAP

C) The customer provided a phony US 800 number as the technical
contact and calling that 800 number results in a message that says
"Not in Service".

D) We emailed the customer and notified him of the issue, yet he took
no action

E) The customer claimed we blocked him, however, he may be sending
email from a MAPS blacklisted IP block

F) The customer could have sent email using the online email interface
we provided. It is NOT blacklisted. He did not.

G) The customer could have opened a ticket using our online technical
support system. He did not.

H) The customer could have called our support number which is answered
24 hours. He did not.

I) We did not disable the FTP service

J) We did not shut down his POP3 or SMTP email services

K) We have not denied the customer access to his files or data, which still
reside on our servers.
We are not in the business of disrupting customers web sites, however,
we will not allow one customers application to consume all of the
servers resources at the expense of other customers sharing those
resources. In some cases, drastic situations require drastic action.
In this particular case, the customers application was crippling the
server and I believe the customer was most likely aware that his
application could not be supported on a shared SQL Server.

You may be surprised by the number of people that move poorly written
applications from one host to another always complaining that it is
the hosts fault. They never tell anyone about their misgivings, only
about how terrible the host is for taking some action to protect their
customers and systems.

We are an excellent hosting company. We provide excellent services,
guaranteed performance and maximum uptime. Just ask any one of the
other customers that were sharing that particular SQL Server. I would
bet everyone of them were pleased that we did not allow this customers
application to continue to cause their applications to fail due to
timeouts and connectivity problems.

ASPwebhosting.com

[David K]

in fact aspwebhosting did shut me out of my mail service. My login no
longer works. I am also shut out of their online help system. I
went there to file a new ticket but I recieved a "You are not
authorized" message. All the numbers which I provided are in fact
correct. I never provided any 800 number as a technical contact. I
have no idea where that statement came from. When I tried to contact
them via email I used my yahoo account. Have they have blocked all
incoming mail from yahoo servers? If anyone out their needs a hosting
service please consider another provider. If their is a change of
heart on their part and I am treated fairly I will gladly post that
information here. All I want is access to my database and to my
files. I need to download them so that I can move to another
provider.

[David K]

aspwebhosting has in fact cut me of from my email service (which is
paid for until the end of this month). They have disabled my login to
the help desk system. I tried to file a tick their but my login did
not work. When I try to email them for information via my yahoo mail
account my emails are bounced back (they have the entire yahoo mail
system filtered). All of the phone numbers that I have provided them
are correct. I have been a paying customer for about 5 months. I
understand that pulling my website from their server may have been
neccesary due to sql-server performance issues but the treatment I
have recieved since then is disgraceful. Before I was booted from
their system I did file one help desk ticket stating that I had found
the roblem code and opptomized it. I filed that ticket and then
checked back a few hours later to see what the reply was. The reply
was that I was locked out of their system completely.

[Support]

Indeed we did take the customers site off-line, however, we did not
disable email, FTP or any other services as the customer describes.

The customer chose a shared ASP.NET hosting plan, a starter plan to be
exact, however, his site was using 80% to 90% of the processing time
on a multi-processor SQL Server machine that typically supports 200+
customers using an average of 18% of the servers CPU time.

What the customer is failing to tell you is the following:

A) Customer recently signed up for service, from Japan and provided a
Japanese telephone number

B) We called this customer in Japan and left a message on the
answering machine describing the problem and requesting him to call us
ASAP

C) The customer provided a US 800 number as the technical contact and
calling the number results in a message that says "Not in Service"

D) We emailed the customer and notified him of the issue, yet he took
no action

E) The customer claimed we blocked him, however, he may be sending
email from a MAPS blacklisted IP block

F) The customer could have sent email using the online email interface
we provided. It is NOT blacklisted. He did not.

G) The customer could have opened a ticket using our online technical
support system. He did not.

H) The customer could have called our support number which is answered
24 hours. He did not.

We are not in the business of disrupting customers web sites, however,
we will not allow one customers application to consume all of the
servers resources at the expense of other customers sharing those
resources. In some cases, drastic situations require drastic action.
In this case, the customers application was crippling the server and,
in my opinion, the customer was fully aware that his application could
not be supported on a shared SQL Server.

You may be surprised at the number of people that move poorly written
applications from one host to another always complaining that it is
the hosts fault. They never tell anyone about their perforemnce
issues, only about how terrible the host is for taking some action to
protect their customers and systems.

We are an excellent hosting company. We provide excellent services,
guaranteed performance and maximum uptime. Just ask any one of the
other customers that were sharing that particular SQL Server. I would
bet every one of them were pleased that we did not allow this
customers application to continue to cause their applications to fail
due to timeouts and connection failures.

ASPwebhosting.com