The 'shared server' hosting environment is the hosting solution for our web hosting and reseller hosting plans. A server's resources, such as RAM (memory) and CPU (processor), amongst other things, are shared amongst all accounts on the server. We ensure that the server has plenty of capacity to meet the day-to-day needs of the vast majority of web sites, ensuring also that the demands for resources are met even at peak times. Given that resources are shared amongst all users, this also makes it possible for web sites to use too many resources to the detriment of other customers hosted on the same server. This can happen for many reasons, but the most common causes are due to poor coding, compromised accounts or a very abnormal huge influx of visitors to the site. Allowing sites to utilise more than their fair share of resources could lead to a poor quality of service for the remaining clients on the server.
We have drafted this policy to outline what we consider to be excessive usage of server resources, and to also exclude certain types of content and eliminate bad practices which almost always cause resource over-utilisation. This policy stands in addition to our terms of service. The vast majority of sites won't even come close to these limits, and those that do will almost certainly be adversely affecting the service other clients on the server are receiving.
We have developed a number of automated systems which enforce the bulk our resource usage policy. These systems trigger alerts when accounts hit a "soft" limit - these are mild violations of the resource usage policy that, whilst excessive, have not yet caused any significant reduction in server performance. Typically we will then notify you of the problem, and you'll have a period of time to fix the problem - typically between 2 and 10 days depending on the severity. This might be by rewriting parts of your site to be coded more efficiently, or if that's not possible we can talk about alternative hosting solutions where you can have dedicated resources - such as on our cloud hosting platform or on a dedicated server. If a site hits our "hard" limit, the server will automatically kill the process causing the problem to prevent the server being brought to a griding halt, and may also suspend the web site in line with our terms of service. This action will only be taken in extreme cases where the violation could have caused service failure or a severe degradation of service - where possibe we will work with you to resolve any issues without interrupting your service.
These policies are in place to protect 99.9% of our customers from the tiny fraction of sites that cause performance issues. We want you to enjoy the best possible hosting experience for your site - that is to say fast, and with the maximum possible uptime. The only way to do this fairly is to ensure that all users abide by the same set of principles, so no individuals can become a 'resource hog' to the detriment of others.
Unsolicited email / SPAM carries not only a financial burden, but can also severly damage our reputation as a spam-free network. This damage can prevent legitimate email from being delivered via our network or servers. We therefore maintain a zero-tolerance anti-spamming policy. We prohibit the sending of SPAM or any unsolicited commercial email, being sent either over our network OR over any network if the email advertises or mentions in any way a site hosted on our network.
We do not permit email to be sent from 'bought' lists, you may only send email to lists that you yourself have collected. We are made aware of bought lists as they almost always contain spam trap email accounts, which are monitored by spam prevention groups.
In addition to the sending of bulk email, we prohibit account holders from cross-posting messages on a large number of newsgroups, websites or forums, and/or posting obscene or threatening messages whilst using or referring to an email address or website URL hosted on our network.
If you violate this policy then your account will be subject to a thorough investigation, and may be terminated without notice. Any damages will be prosecuted to the full extent of the law.
We do not permit pornography, including adult oriented pictures, videos, links to adult sites or sites containing content of a sexually explicit nature, including in written text, or which retail sex-related merchandising.
Backups, Storage Archives & FTP Storage Space
Hosting accounts are to be used for the purposes of hosting web sites - they are not to be used to back up content from remote computers, as a general purpose file storage system or as an FTP upload repository. We permit the storage of a single backup of your account to be stored within your space, however these must not be stored for more than 45 days. We do not permit the storing of audio music, videos, photos, or other downloadable media unless these files are being used specifically on your publicly accessible web site.
We do not permit real time chat software to be hosted from within your hosting account. Third party chat solutions that integrate with your website but are remotely hosted are permitted.
All third party web applications that you install must be kept up-to-date. Failure to keep third party applications up-to-date leaves them open to vulnerabilities, which can lead to the server being exploited. It is your responsibility to regularly check for updates to applications - we would suggest doing this once per month. Any applications which are being actively exploited will be automatically quarrantined and we will contact you to advise you of the situation. If you decide to take no action, quarantined files will be automatically deleted after 14 days.
The following are strictly prohibited:
Files & Folders
Any processes attributed to or initiated by your user account, must not:
CPU Usage - Websites
The total usage of all websites running within an account may not exceed these limits:
No individual cron job within an account may exceed these limits:
The total usage of all cron jobs running within an account may not exceed these limits:
An account may not: