First Problem with BlueHost

Posted on May 14, 2008
Filed Under Blogging Information, System Information |

Well the honeymoon is over, sort of. I tried to log into my blogs and the blogs did not come right up! I was nervous of course, since I am just starting out with this blogging network. I do not want all three up and running blogs to be down at all let alone for an extended period of time. I quickly went to http://bluehost.com and tried to log in to see if it was something I did. The website brought me directly to a System Alerts screen and told me what was going on. See below to see what I saw: (click on it to see the full sized image)

This was nice, I have to say, to be able to keep track of their progress. Although it wasn’t optimal, I could at least see what was going on. And luckily for me, and for BlueHost, my blogs were quickly restored to working order. I just wonder how long my blogs have been down for. I know they are not super popular right now, but the whole idea of building a blogging network is that it needs to be built. I cannot afford downtime.

This brings up an interesting point. Did I shot myself in the foot putting all three of my blogs on one server? Should I diversify when I expand my blogging network? Also, anyone else host on BlueHost and had the same problem?

Comments

One Response to “First Problem with BlueHost”

  1. Nick on May 15th, 2008 2:23 am

    Very interesting. I’m on box 403, and there has been server overload for the last four days. I’ve even had my account deactivated and later reactivated as they pounce on anyone suspected of causing the problem. It turns out I had nothing to do with the server overload, which still persists as I write this.

    In my case, by deactivating my account, I had 12 websites go offline. Not much fun when those sites are your livelihood. I also regret having all my sites under one account, but spreading them out can be quite costly.

    Thanks for writing this post. It’s some comfort to know that I’m not the only one experiencing the problem, and it’s not just on my server box, either.

Leave a Reply