Last updated on November 26, 2023
We rely a lot on the reliability of various Internet service providers. We expect our broadband service to function at a reasonable speed every minute of every day. We expect any “essential” services for our businesses to be online and functioning.
When Amazon Web Services, Microsoft Azure, or any other major service experiences outages, a lot of people panic.
My wife and I rely on a hosting service that is part of a giant created by merger after merger. Maybe there’s a reason Amazon and Microsoft are so successful. They have incredible speed and up-time for their servers.
The last few weeks have been frustrating as our Web hosting provider, Bluehost, suspended our account with the claim that our blogs and sites consume too many resources. There’s no reason for a basic HTML site and one installation of WordPress with a handful of plugins to overload a shared hosting plan.
The site has less traffic than it did a two years ago, and a tenth of the traffic the site had ten years ago. The blogs are also not well-trafficked lately. If anything, the website and blogs should be consuming less processing power and memory.
One has to appreciate the Office Space and Kafkaesque response of Bluehost:
Me: Our site is down because it was using too many resources. How can we address this?
Support: Log in to the site and adjust the WordPress, PHP, and MySQL settings.
Me: We cannot access the site, not even via the cPanel interface.
Support: Yes. The account has been suspended….
After three phone calls, two emails, and a very long online chat, Bluehost promised to review the account.
As our server access was restored, the server went offline. Visitors were presented with a message directly from Bluehost that there were server problems after an upgrade.
So, what are the odds nothing was our fault? It seems likely we didn’t do anything to violate the terms of service. Instead, the hosting service somehow messed up the server upgrades. There are a lot of moving parts (metaphorically) and any one of them could cause problems with a website.
Anyway, I’ve lost a lot of time trying to keep this blog and our others online. I have three months of posts for 2019 and archives dating back to 2007 that I would like to have restored as soon as possible. But, that will take time I might not have until May.
I’ve lost a lot of sleep getting things back online. I know these things happen. That’s one reason I keep a lot of backups of all things digital. Technologies fail, for many reasons. When they do, you need a plan to restore all those backups and settings.
I do practice what I teach. That still doesn’t make crashes and suspended accounts any less frustrating.