See available themesUKTNET
UKTNET - Resource Usage Policy
A shared hosting environment means that the server's resources, such as RAM (memory) and CPU (processor), are shared with every other account on the server. We always try to ensure that a shared server has sufficient resource capacity to meet the day-to-day needs, and has adequate resources to meet demand at peak times for the vast majority of web sites. Because the server's resources are shared amongst all users on a server, it is always possible for any individual website to use too many resources to the detriment of other customers hosted on the same server. Excessive resource usage can happen for many reasons, but the most common causes are due to poor coding, compromised (hacked) accounts, targeted dDos attacks, or a very abnormal amount of visitors to the site.
The vast majority of sites hardly ever breach resource usage limits, but those that do will inevitably have a detrimental effect on the service provided to other clients on the same server receive, so we have drafted this guide to outline what constitutes excessive usage of server resources, and what actions might be taken.
We want you to enjoy the best possible hosting experience for your website - that is to say fast, and with the maximum possible uptime, and 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.
Overuse controls are in place to protect 99.9% of our customers from the very small proportion of sites that cause performance issues.
What controls are in place?
Our servers have a number of automated systems to help us control excessive resource usage. One of those controls is an automatic alert is sent to us when an account hits a pre-detemined "soft" limit - soft-limits are mild violations of the resource usage policy that, whilst excessive, have not yet caused any significant reduction in server performance, but would if they were continuous. If the problem is continuous and severe, we will notify you of the problem, and you will be given a period of time to address it - typically between 2 and 10 days depending on the severity. Fixes you might need to make might entail re-coding parts of your website so that they are more efficient and less demanding on server resource usage for example. If re-coding is not possible then depending on circumstances, we will discuss alternative hosting solutions with you such as as moving your site onto a more powerful, and less populated server, or offer you a dedicated server option. Both of these options will inevitably incur administrative costs, and an increase in the cost of your annual hosting.
Where a web site hits our "hard" limit, the server will automatically kill all of the processes causing the problem to prevent the server being brought to a grinding halt, and could also result in automated account suspension. This action will only be taken in extreme cases where the violation could have caused service failure or a severe degradation of service - where possible we will work with you to resolve any issues without interrupting your service.
What are the policies?
Unsolicited Email / SPAM
Unsolicited email / SPAM is not only annoying to recipients, it can severely damage our reputation as a spam-free hosting network. Sites causing a server to get blacklisted cause quite a lot of work to get them de-listed, and can prevent legitimate email from other sites on the server from being delivered via our network or servers. We therefore maintain a zero-tolerance anti-spamming policy, and we prohibit the sending of SPAM or any unsolicited commercial email from 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.
Whilst your hosting account will allow you to send an hourly limited amount of 'bulk' email to your own customer base, we do not permit email to be sent from 'bought' in email lists, because most bought in lists will contain spam trap email accounts which are constantly monitored by spam prevention groups, and blacklist operators, and could cause a server or ISP to become permanently blacklisted for allowing it to happen.
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 incurred by us as a result of a blatant violation will be prosecuted in court to the fullest 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 do not permit the storing of audio music or videos, unless these music and video files are being used specifically on your 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 quarantined 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:
- Banner rotation services & link exchanges.
- Bit torrent or other peer-to-peer applications, trackers and clients.
- Offering of free or paid image, file, document or data storage.
- Offering free hosting or email services.
- Online RPGs, hate sites, sites that promote hacking, SPAM, warez content or other illegal activities.
- Material that infringes any rights (including Intellectual Property Rights) of any third party.
- Operating a public download mirror.
- Running a gaming server.
- Running a proxy server or anonymizer, either publicly accessible or password protected.
- Web spiders and indexers.
- IRC Egg Drops & Related Programs.
- UltimateBBS, Ikonboard, YaBB, YabbSE.
- Shell, SSH, Telnet Scripts and all alternatiives.
- formmail.pl, formmail.php, formmail.cgi OR alternative names for the same script, except the secure version available for install from the Control Panel.
- Any script using a large flat file database.
Resource Usage Restrictions
- No more than 40 simultaneous Apache connections are permitted from any one source.
- No defined cron job should execute more frequently than once every 10 minutes.
- All cron jobs must be 'niced' to 15 or greater (add nice -n 15 to the cron job).
- Accounts are restricted to 15 concurrent MySQL connections.
- Databases cannot exceed 2GB in size.
- Database queries cannot exceed 8,000 per hour.
- Database changes (insert/update/delete) should not exceed 2,000 queries per hour.
- Accounts should not exceed an average of 1 second of CPU time per query for MySQL queries performed in any given hour.
- Databases may not be accessed by externally hosted sites, except for the purposes of administering the database.
- Attachments larger than 25MB in size should not be sent by email.
- IMAP/POP Email Boxes must be no larger than 4GB each. Old mail can archived or deleted to remain below this limit.
- No more than 60 POP connections are permitted per hour.
- No more than 500 SMTP connections are permitted per hour.
- No more than 1200 emails may be sent per hour.
- Outbound emails should not be sent to more than 50 recipients at any one time.
- If you need to send mail to more than 50 recipients, mailing list software should be used. Any such software should be capable of throttling email sending to a maximum of 1 email every 5 seconds. Mailing software without this functionality is not permitted.
- Mailing lists can have a maximum of 2,000 recipients. Users requiring mailing lists larger than 2,000 subscribers will require a dedicated server, or may need to use use a third party email marketing platform.
- Any mailing list over 1,000 recipients can only be sent between 3AM and 7AM GMT weekdays, or any time at the weekend.
- Any emails sent to a mailing list must contain an unsubscribe link to an automated email removal system. This system must not be behind password protection.
Files & Folders
- Accounts may not exceed more than 150,000 inodes. Every file or folder in your hosting account uses up one inode.
- Accounts exceeding more 75,000 inodes may be removed from our backup system. Databases will continue to be backed up.
- A folder cannot contain more than 5,000 immediate child files or folders, excluding files within child folders.
Any processes attributed to or initiated by your user account, must not:
- Consume more than 128MB RAM.
- Consume more than 30 seconds of CPU time.
- Create core dumps.
- Execute a script or binary that forks in a way to create a fork bomb, or spawn subprocesses.
- Run in the background.
- Listen to a network port.
- Open more than 30 files.
- Run more than 40 simultaneous processes.
CPU Usage - Websites
The total usage of all websites running within an account may not exceed these limits:
- Perform more than 1,300 dynamic page executions (PHP/CGI) in one hour.
- Perform more than 13,000 dynamic page executions (PHP/CGI) in one day.
- Consume more than 1,000 seconds of CPU time in one hour (realtime).
- Consume more than 10,000 seconds of CPU time in one day (realtime).
CPU Usage - Cron Jobs
The total usage of all cron jobs running within an account may not exceed these limits:
- Perform more than 60 executions in one hour.
- Perform more than 1500 executions in one day.
- Consume more than 500 seconds of CPU time in one hour (realtime).
- Consume more than 5,000 seconds of CPU time in one day (realtime).
- Consume more than 30 seconds of CPU time per execution (realtime).
An account may not:
- Consume more than 128MB RAM per second of CPU time consumed
- Shell access is not normally allowed in order to protect the privacy of other sites on the same server.
In cases where Shell access has been allowed...
- You are not permitted to log into any other server or network from our servers.
- You may not use the "find" command recursively on folders more than 5 levels deep.
Revised 22nd June 2011