Identifying and Avoiding Dishonest Hosting Providers?

An anonymous reader asks: "Recently I have had the (dis)pleasure of dealing with the buyout and resulting problems problems of Managed.com by WebHostPlus, Alphared (aka Orangefiber) being dishonest about backup facilities (no power backups and not multi-homed), and CalPop overselling bandwidth. What can we do to protect us from these companies, they all seem to be have web sites and be real companies, but we seem to get scammed by them. The dishonest ones look a lot like the honest ones. We can't afford the attorney's fees or to build a data-center, and that is why we pay the monthly fee to host a server, but the companies do not have what they claim to, nor do they care about the customers. We contacted two attorneys in the United States and they said that the companies didn't have any assets worth going after. What does Slashdot think of these problems and what can we do to avoid them?"

Comments

Web hosting Talk

[Telvin_3d]

Swing by http://www.webhostingtalk.com/ and check them out before putting money down. A really solid community, where SOMEONE will have experiance with any given provider. And many of the members are more on the profesional side of thigns, not what another comment here refered to as "the clueless PHB set".

Homework. Eyeballs. RTFC.

[Sierran]

Step one: Know what you need. 'Reliable' doesn't mean anything. *How* reliable? To what level? What is an acceptable risk level for the facility your data will be in, or must your data be multihomed? If the latter, failover or clustered? Etc. Make sure that the company can tell you how it will meet all these requirements, in writing, to you and your lawyer's satisfaction before signing a contract.

Step two: Referrals. Who else do they host? Check uptimes. Talk to their other customers. If they won't give you references, or if they can't give you companies you've either heard of or can verify have existed and are independent, walk.

Step three: Read the contract. Better yet, have your lawyers read the contract. Anything fuzzy? Push them on it. If they waffle at all, or look like they're trying to get you to sign terms they might give way on if you push (not the price, the *terms*) DANGER. Established hosting companies should have their risks well set out and know what it will cost them to assume whatever level of risk - at worst, they should simply change pricing if you try to reassign risk, or simply tell you they don't offer that service level.

Step four: GO LOOK AT THE FACILITY. No excuse for that. If your business is going to depend on this facility, you need to see it. No trusting web photos. This is your place of business and your physical plant. If your business depends on it being available, or worse yet on it being something that you describe to *your* customers, it's your responsibility to eyeball it. If you don't know what you're looking for (and if you're a business type, there's no shame in that) then find a technical person to eyeball it with you and pay them for their time.

Step five: If you're concerned about their available bandwidth, ask to see bandwidth reports. Ask for peers who can verify their connectivity. When you visit a facility, ask to see the external switching facilities and rough-count circuits if you have to. If you're still concerned, then tell them you want legal guarantees (with penalties) in the contract for available bandwidth - they shouldn't bat an eye at that, since the more bandwidth you (verifiably) use, the more they should be able to bill you, probably. If they balk at potential penalties for short bandwidth, there's likely a problem. Typically, they themselves will offer tight bandwidth monitoring just so they can bill you for those bits.

Step six, and final for me: HAVE A BACKUP PLAN. Things can and will go wrong. The best hosting provider out there might suffer incredibly bad luck and multilevel catastrophe. EVERY admin will have horror stories of 'the two things that would never go wrong together' going wrong. My favorite is a switching center in downtown Boston having *both* of its redundant data pipes being taken out by construction on the same day by the Big Dig, on opposite sides of the building. This might mean having a small backup system in another center on the smae provider. It might mean having a staging system in a home office that can be brought live on limited bandwidth. I don't know, that's *your* problem. It might just mean having a really good PR checklist. But HAVE A PLAN.

Sure, if you're not dependent on an uptime number, these steps may not be necessary. But if, as the question seems to imply, your success or failure will be tightly coupled to the reliability of your hosting provider, then there's no substitution for Doing The Work.