ASPnix Reviews

Average rating: 3.2 of 5 (based on 6 reviews)

>> Host's web site

February 8, 2008	Reviewed by Carol
	ASPNix is "always down" host with overloaded servers. Avoid it.

December 22, 2007	Reviewed by Fabian Marsiglione
	I´m an ASPnix client since few years ago and I’m really comfortable with the services. The servers have a very good uptime and the support is great. They always help me and response time is amazing. I would recommend ASPnix Windows Hosting to everyone.

December 22, 2007

Reviewed by Fabianus

Since more than 2 years our company is satisfied in every way with the services and prizing of ASPnix. Support, hardware, software and consulting – all these areas are covered by their enthusiastic and friendly team and they keep on improving with every demand we could address. Their “open communication” policy is revolutionary and now imitated by others: open and honest forums keep record of all inquiries and testifies their seriousness and dedication. ASPnix accompanied our company starting with a small presentation website and now having a fully featured VPS with several active websites, .NET applications, mail-server etc. The best word describing our relation to ASPnix is “confidence”, and that’s what counts most.

August 20, 2007

Reviewed by ASPNix Customer 2

I have had numerous HTTP, FTP, SQL and Email issues lasting many hours at a time over the last month.

ASPNix disabled the customer forums on 7/17/07 so I started tracking when I sent in tickets for outages. Since that time I have sent in tickets on 7/20, 7/25, 7/27, 7/28, 7/29, 8/3, 8/4, 8/8, 8/11, 8/13, 8/15. (This is just in the last month since I started tracking it - prior months are similar or worse)

Average outages (HTTP, FTP or SQL) lasted about 10 hours each with the longest HTTP outage I'm aware of was about 30 hours. Their response to tickets submitted was a minimum of 6 hours, average was about 12 hours with no response to 4 of the 11 tickets I sent in. So within about the last month my customers were unable to reach my support site for a minimum of 100 hours. To date there has been no credit given for the downtime.

All responses received were one of 2 canned replies - Either "We don't see any problems here..." or "your issue has been resolved, check your site(s) again"

The company line is give us a chance we are making improvements all the time. (Like I should have to wait 3 days for server replacment parts to fix my email?) I suggest you wait UNTIL the improvements are done before even considering ASPNix or any reseller that uses them.

July 30, 2007

Reviewed by ASPNix Customer

There hasn't been a week in the last year where there hasn't been an Email, SQL, HTTP or FTP outage that lasted for an extended period of time - several hours to sometimes days at a time.

They boast 99.9% uptime but read their TOS carefully. The guarantee network connectivity not website availability. Who cares if the network is running if you can't get to your web site and eMail.

Don't bother requesting credit for the website downtime either - They will just direct you to the Terms of Service stating network uptime, not website uptime.

They have recently started spamming host review sites with positive comments so be careful what you read.

Save your money and host with someone else.

November 24, 2006

Reviewed by Jim

I have had some good experiences with this host, and it took me a long time to decide to leave them.

The biggest problem is lots of down time. One server with an important application has been down about twice a day for 10-15 days. About 5 days ago, they said they would replace it, but the problems continued for 4-5 more days. I think it's fixed now, but I've already started moving to a new provider. They seldom notice it’s down unless I tell them. When I submit a ticket, it's usually back up within 30-60 minutes, but if I'm asleep and don't notice, it usually stays down all night.

Today, I'm trying to get a database backup, so I can move to another provider. I did not tell them why I want it, but my ticket has been sitting there (while my site is down) for about 16 hours. About 15 hours ago, I got a response asking for more information, which I answered within 5 minutes, but have heard nothing since, until a couple of minutes ago while I was writing this review. He promises to have it in a few minutes, and threw in that they are never closed. They sure looked closed to me.

They seem to have only two people, Rick during the day and Roma the rest of the time. I think Rick took vacation, and Roma had to sleep sometime. To be fair, I should note that today is the Friday after thanksgiving. Roma was there at about 10 pm last night (Thanksgiving), and apparently woke up around 2 pm. I chose this time for my maintenance because I thought it would minimize disruption for my users.

Next, one of my customers is dissatisfied with the response time. It's not awful, but he's afraid that prospects attracted by a search engine will go elsewhere rather than wait. I have identified two other providers that seem to have better response times. ASPnix ignored my request to move this application to another server. (Once they gave a non-responsive answer, and the second time they literally did not respond at all.)

They often do not address the question and seldom give you all the information you need, but that’s the norm in ticket-based support. They can be quite careless about following instructions, which can be critical to maintaining the integrity of a database. You are dependent on them to backup and restore SQL database, and if they do it wrong you can lose data. My users have never told me I actually lost data, so probably nobody was on during the time interval for which the data was lost, but the potential was there because ASPnix didn't follow instructions. Rick is rather impulsive, and you can usually only communicate by submitting a ticket.

Also, they once withdrew a feature (SQL full-text searching) without notice, causing my site to stop working until I discovered it.

Finally, the Helm system is a bit awkward in that everything is domain oriented. If you have several domains, you must have a separate FTP account and SQL server account for each.

In summary, they are probably OK if you need ASP.NET (especially 2.0) or SQL Server (especially 2005), and can tolerate some support problems and down time. Otherwise, I would not go with them.

Home: Web Hosting Reviews | Contact | Privacy Policy | Disclaimer