If you noticed that this blog was inaccessible in the past 24 hours, its because I’ve migrated it to my new web host. DNS propagation usually takes about 24 hours to take effect, depending on your location. Just wanted to update you guys about that so you know what happened and I’m also sharing with you my recent experience with web hosting issues.

This month of October has been the worst month for me and my blog in terms of web hosting. Would you believe that I’ve migrated my blog at least 6 times just this month? In my effort to find a new webhost, I opened an account with 2 other web hosts but for some certain reasons, it didn’t work out so I had to migrate back to my previous host. Anyways, what prompted me to go and find a different web host was the “issues” I had with my previous hosting provider.

Most of you guys know that my blog’s hosting account got suspended several times due to “high cpu usage”. I tried installing WP Super Cache and other plugins that will help minimize the load on my server, decreased the search engine crawl rate on my blog and tweaked my robots.txt file all in the effort of avoiding using up my server’s cpu resources. Unfortunately all of those efforts were in vain because I still got my account suspended not once, twice but three times! When I asked my web host for the reason why they suspended my account, they gave the same answer – “high cpu usage“. This time, I asked them what could be causing the high cpu usage and the Level 2 Tech Support people gave me these lame answers/excuses.

This is because the site is open for anyone to search for whatever they want, and this can cause malicious users to abuse this, which in this case it appears they have. The easiest fix for this is to make a log in and for anyone to search, perform a GET search, they must be logged in.

It looks like you have your website setup with a forum script or members site that is publicly accessable. youll need to adjust your website so that only members who are logged in can view pages / posts / profiles / images. This should resolve the issue. I am unsuspending the account. Please make the changes.

A blog is a forum, its a specific form of forum, however it is based on the same software. One page, that holds several posts. i do not know if the site has profiles or not. I got the information because i work at a hosting company and do this work every day all day and happen to know that when ever a site is suspended and in the abuse report it contains several hundred apache get requests to random files and directories, such as 3fb5c0424e085100d6b88904b308d6b0.css?t=1027215365 the problem is that the site / profiles/ forum/ blog/ community/ what ever it is, is configured to be openly accessible to the internet and because of this someone or some group of people are access the site in an abusive way, often times looking for exploits. These requests overload the server. The fix is to disable the site so it is not open accessible to anyone who is not logged in with a correct username and password.

Btw, my blog was hosted on a reseller account and because of these “high cpu usage” issues, they were trying to get me to upgrade to a VPS account. With that and these lame answers, I knew that they were just trying to make money and get me to upgrade my account. It was at this time that I decided to move out and find a new web host.

After checking out my options, I finally decided to go with ServInt who I found via BloggingTips.com and purchased a VPS account. My blog has only been with them for a day but I’ve opened my account about 2 days ago and since then I’ve been dealing with their customer support. Based on my experience with their support, all I can say that their customer support and service is AWESOME! They have 24/7 support and free phone support. Not only did they help me with the setup and answered my questions but support was replying to my tickets even at 1 AM! Their sales and tech support aren’t only friendly and helpful but also very knowledgeable.

I tried migrating the other day but had some issues because of an old version of MySQL so I had to wait until support upgraded it before I was able to restore my WordPress database backup. Now that I’ve successfully migrated my blog to its new home on the web, I can now get back to blogging and focus on more important stuff like my upcoming blog contest.

I’m keeping my fingers crossed and hoping that I won’t have any major web hosting issues again and that everything would work out with my new web host – ServInt.

NOTE: Just to be clear, my previous web host/hosting provider was NOT TechHive. TechHive was just using a reseller account from another hosting company. All of the problems/issues I had was with the other hosting company, not TechHive.