This is another security feature that we employ to ensure that all your scripts are running within the limits of the shared accounts. For example, our rules state that you cannot use more than 25% of CPU time and Memory for more than 60 seconds.

These limits are not enforced to be mean. Although we offer generous bandwidth and storage on all our plans, a shared server has to deliver great service for a number of users. If one person uses too many resources, it hurts everyone else's ability to have their sites display with top performance.

Whenever your site exceeds our resource limits, your site will be automatically suspended. You will see the Account Notice page, because your site was caught abusing our servers and the server is putting your site on hold until your account falls within the parameters that you agreed to when you signed. Then it will be released.

Below are some reasons why your site might be suspended:

1. Poorly written scripts. Scripts that are poorly written use excessive of CPU / Memory and MySQL time. If you got these scripts from a software developer, then you'll need to work with them directly to find a solution, or don't use the scripts. Common script problems are generated by mods or plugins for content management systems or online forums. As a temporary solution, you may wish to disable your less-essential mods and see if that improves your situation.

2. Your site has become too large for a shared server. It is possible that your account has outgrown your shared hosting account and that you may need to upgrade to a VPS or dedicated server, which are able to accommodate larger sites.

3. Optimizing your MySQL. Another great way to try to resolve this issue is by repairing and optimizing your databases that your applications use on a daily basis. You can find how to do that on the following link: http://answers.hostican.com/questions/34

Further detailed information about this matter can be found by accessing your site via FTP and going to /cpulogs/ folder and looking at the respective date that you see this page. For example, if you are seeing this page on 01/02/08 it would be: /cpulogs/Apache-2008-Jan-02.log. You will need to download this file and in there it will contain more details about what is going wrong.

The above information covers only a few of the issues that could explain why you are seeing the page. Please don't hesitate to let us know if you have any further questions.

How can I avoid seeing this page in the future?

There are a couple of ways to avoid seeing this page. One of them is by optimizing your code, thus ensuring you use less CPU and Memory on your account. Another way is by replacing .php files with .html files whoever you can to lower the memory needed to run your site.

Or, you can upgrade to a VPS hosting account such as the VPS-Rage or VPS-Extreme. This is an ideal solution for a growing site, and you can find more information on http://www.hostican.com/hosting/cpanel-vps.php