Updates on Bluehost server status

Two months ago I posted my problem with Bluehost server – that their server was being overloaded. I contacted their staffs and was told that they were fixing the issues.

Good news is, I’m seeing significant improvement since early Feb.

Things are improving slowly and I’m getting back the usual response speed for my website. For your reference, I made a quick print screen this morning and here’s how the server status looks like at this moment.

Bluehost server status overview

Bluehost server status (6/3/09)

Compare Bluehost server performance on January and March

On a closer view, you’ll see the server load’s controlled within 8 CPUs (which is the limit of one cycle); storage and memory usage had been reduced – things are looking good again.

Bluehost server status (March 6, 2009)

Screen captured right before this blogpost was published.

Bluehost server status (6/3/09)

Bluehost server status (Jan 9, 2009)

Sreen captured on January – I was shock to see the CPU load at that time.

Bluehost server status (8/1/09)

Is Bluehost still recommended?

There was some worries with the overselling process but everything is alright by now. Despite the poor performance for the past one month (Jan 2009), I actually see good things from this incident. Bluehost, as a company hosting hundreds of thousands websites, was able to address and fix their server problem in a short time frame. This shows that the company has strong technical support on the machine blocks and they care a lot about their customers.

With such being said, – Yes, Bluehost is still recommended. In fact, I think they are still among the bests and I remain my ‘A’ rating on the company.

Visit Bluehost online: http://www.bluehost.com
Read detail Bluehost customer reviews.




Popular Web Hosting Reviews

In case you're here looking for some honest hosting reviews, here're some of my popular hosting reviews.

Hostgator Hosting iPage Hosting BlueHost Hosting Fatcow Hosting JustHost Hosting Review
Hostgator Review iPage Review BlueHost Review Fatcow Review JustHost Review



3 Comments for "Updates on Bluehost server status"

  1. avatar SimpleTechGuy Says:

    I’m having problems with bluehost now. Just woke up this morning and everything is down. This is my first bad experience with bluehost, and I don’t like it. I do have access to my cpanel, but I can’t get into anything else, not even the help desk. I hope they can get everything back up soon! Are your websites down? Would you send me a mail and let me know? Thanks

  2. avatar FatCow vs BlueHost: Who’s better? Says:

    [...] loaded (sign of unmanaged overselling!) and my database server is on and off broken. Nevertheless, the problem is solved by [...]

  3. avatar Frank Says:

    Hi, my website have the sample problem again, and when i talk with support, they said, they can do nothing. :( that is really bad. Here is the suggestion , but in fact we can do nothing to our database….

    What are CPU Quota/Suspension Errors?

    CPU Quota/Suspensions Errors are used as a maintenance tool to help avoid server lockups by preventing customers from running inefficient scripts that monopolize unnecessary CPU time and slow your server down.

    Why do I get CPU Quota/Suspension Errors?

    CPU Quota/Suspension Errors are currently triggered by a single process taking more than 30 CPU seconds to run or if your total processes take more than 40 CPU seconds in any 60 second window. They are set up like this to avoid server lockups. Your site will generally come back up after 5-10 minutes of suspension. In some cases the following issues may trigger CPU Quota/Suspension Errors:

    • Over sized and unnecessary database queries can lead to performance issues. Optimize your applications to use less CPU by adding appropriate indeces (index) to your MySQL tables. Click here to learn more about Optimizing MySQL: Queries and Indexes
    • Poorly coded .php scripts may lead to extended processing times. Try using static .html documents instead of .php scripts; doing so will practically eliminate CPU Quota Suspension/Errors

    How can I prevent more CPU Quota/Suspension Errors?

    If you receive several CPU Quota/Suspension Errors a day or notice this to be a repetitive issue, we encourage you to consult your personal designer, programmer or webmaster. As these issues are the account holders responsibility to resolve, BlueHost Technical Support is not authorized to troubleshoot your scripting or database programming issues on your behalf. Please have your designer, programmer or webmaster review your detailed log files by doing the following:

    1. Log into your BlueHost Control Panel.

    2. Locate the Files menu.

    3. Locate and click on the File Manager icon.

    4. When the Directory Selection menu loads select the Home Directory option.

    5. This will take you to the Root ( / ) directory of your File Manager.

    6. Locate and double click on the tmp folder.

    7. Inside this folder there are two folders that may have information pertaining to this issue; the cpu_exceeded_logs and mysql_slow_queries.

    8. The cpu_exceeded_logs folder will contain individual log files listed in order by date. If you wish to view the details of these log files right click on the file you would like to open and select View from the drop down list.

    Important: The cpu_exceeded_logs contain important information about which processes you were running and their lengths that coincide with your cpu exceeded errors.

    Example:
    Fri Jul 7 17:07:36 2006: used 716.27 seconds of cpu time for HTTP Request: yourdomain.com: GET /img_yourproducts/shop_images_026.jpg HTTP/1.1
    Fri Jul 7 17:07:37 2006: used 0.18 seconds of cpu time for HTTP Request: yourdomain.com: GET /img_yourproducts/shop_images_027.jpg HTTP/1.1

    9. The mysql_slow_queries folder will contain individual log files listed in order by date. If you wish to view the details of these log files right click on the file you would like to open and select View from the drop down list.

    Important: The mysql_slow_queries contain important information about which queries you were running and their lengths that coincide with your mysql_slow_queries errors. These will appear much like the above logs. only providing details on your particular mysql queries.

    Example:

    Tue Aug 28 11:54:54 2007:
    Query_time: 4 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
    use yourdoma_yourdoma;
    update SS_categories set viewed_times=viewed_times+1 where categoryID=’665′

    Tue Aug 28 11:54:56 2007
    Query_time: 2 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
    update SS_products set viewed_times=viewed_times+1 where productID=’21925′

    Once again if you are unable to resolve this issue yourself we recommend that you consult your personal designer, programmer or webmaster. If you have already done so and feel your situation warrants review by our Technical Support department please fill out our online CPU Exceeded Error Form.Let our World Class U.S. based Support Team help answer your questions. Please allow (24-48 hours) for a response.

    Thank you,
    Scott
    Technical Support Engineer
    BlueHost.com
    888.401.4678

    Does anyone can help me ?

    Thanks

Have your say! Leave a comment.

Please also share the article if you like it. Comments are moderated and rel="nofollow" is in use. Please no link dropping unless it's necessary, do not spam, and do not advertise.