GreenGeeks vs. Rackspace Managed Hosting

If you are looking for a shared hosting service, Green Geeks pricing is comparable to most vendors. T2 tech support is generally knowledgeable, T1 is responsive via chat, but often is not able to resolve issues (other than KB questions). Load balancing on a shared server is difficult for all vendors, since individual website usage is hard to predict. Vendors have different ways of dealing with this - some simply do not guarantee resource limits (e.g. available memory, PHP threads, etc). Green Geeks does provide resource limits as part of their contracts, but they frequently downgrade those limits, presumably to address overloaded servers. BUT BE AWARE - I believe GreenGeeks uses unethical practices when a customer wants to cancel. It is my personal experience that they make it extremely difficult / impossible to cancel a contract. I feel the process is not transparent and they will ignore emails directing them to cancel. In my experience, they will then proceed to charge customers for a renewed contract. I believe multiple customers have reported this problem.

I would choose zero, but it's not an option. In my opinion, STAY away from this company. Problems can occur, but responsiveness should occur when problems do. In my experience, I've been on hold for more than 9 hours, waiting for promised callbacks for more than 30 hours, and don't have any hope for a near-term resolution.

• T1 support generally responds w/i 15-30 minutes

• Fanatical Support - I can't stress how great their team is. Not only are they knowledgeable, whenever I call in (during the day or in the middle of the night), I never have to wait more than a minute to speak to someone.
• Webmail, Hosted Exchange, and Office365 Support - As an IT team of one, Rackspace's cloud solution and migration team has really helped me over the years to minimize issues for users, but also provide a reliable and flexible email platform.

Incentivized

• In my personal experience, the billing department uses unethical practices when customers cancel subs.

• Pricing is competitive, but other providers do beat them out with some of their pricing "features".
• The Cloud Files offering is relatively slow and wasn't usable for us.
• The automated backup feature that is offered for the Cloud Servers is pretty limited and wasn't usable for us.
• There are 2-3 different web management panels, with different logins. It's hard to keep track of which one is which, and can be frustrating/confusing when trying to log in to your panel and choosing the wrong one.

Incentivized

If I wake tomorrow completely incapable of managing a client cloud operation, our dedicated Rackspace Cloud Engineering Team is deployable as literal extension of our business, immediately addressing all needs and requirements without cause of business disruption for our consultancy, and more importantly for the mission-critical ones of our clients. For this reason alone, Rackspace is our choice of choices!

Incentivized

The company does not put as much focus on usability as other cloud competitors and it is kind of clear. It would be good to take a quarter and gather intense feedback, and then another quarter and focus purely on UI enhancements and backend interoperability

Incentivized

In my experience, their support team is massively overworked — taking FOUR DAYS to look at tickets, and a MONTH to fix problems!

Incentivized

From a technical perspective, all shared server vendors are comparable. Bluehost has terrible customer support. A2 is more expensive, but has more personalized support.

Rackspace is a premier IaaS company with vast resources and an excellent reputation for reliability and support. We have used AWS and Rackspace extensively over the last 10 years, while trying other providers for smaller, less mission critical, requirements. Rackspace has been solid throughout that time, experiencing very little unplanned downtime. During their planned maintenance windows, they were incredibly responsive and helpful in coming up with solutions to deal with the scheduled downtime so as to minimize, or eliminate, the downtime experienced by our customers. We originally started working with Rackspace due to a major outage in the AWS platform, which opened our eyes to needing to diversify where our servers are located so as to reduce the risk on a single point of failure with any single provider. Compared to Linode and Digital Ocean, specifically, Rackspace's offering is much more robust. While those other companies do have a good offering, they did not provide cloud servers with enough resources for our needs (MySQL databases with fast solid state disks, and large amounts of memory available). We did host many machines with Joyent for a time, however, they were very focused on the SuSe operating system, which we wanted to move away from due to it's waning community support and relatively esoteric package management system. Ultimately, Amazon and Rackspace were our two providers for hosting our infrastructure, consisting of several (4-10) application servers, database servers (typically 1 MySQL master with multiple slaves for reporting, backups, and failover), and micro-service host machines.

Incentivized

• Throttling servers impacted website availability.

• We've found it helpful to host our own web sites on their cloud servers, which is a positive.
• We've also hosted our Nagios instance on a low-end cloud server, which is also a positive.
• A negative impact is that they've now decided to start charging for their support.

Incentivized