By using ExiaHost's services ("ExiaHost", "our", "us", or "we"), you ("Customer", "you", or "your") agree to follow and comply with our policies stated below.
If you have any questions regarding the Resource Abuse Policy, please email us at email@example.com or by opening up a ticket through your user panel located here.
1. Overall Resource Usage
Shared hosting accounts share resources with other users on the same server. Websites that utilize a high amount of server resources (including CPU, memory, and network resources) will be at risk for suspension. Accounts must follow the resource limits set below.
Memory usage may not exceed 10% per domain/file/application
CPU usage may not exceed 20% per domain/file/application
Apache connections may not exceed 20 connections
MySQL connections may not exceed 10 user connections
150 emails per hour, per domain
There are special exceptions (i.e. account compromise) to these rules to be determined at the time we discover abuse. We reserve the right to suspend any account that is causing the server to be unstable in order to keep the server functioning normally.
If your account has been suspended for resource abuse and we are unable to mitigate the cause and you do not wish to upgrade your services, the account will remain suspended and a backup of your files will be provided to you. This is to prevent the server from remaining unstable.
An inode is defined as any file or folder on the account. This includes each email as well as your webpage content (images, php files, html files, videos, etc). Shared accounts found to be in excess of 75,000 inodes may be removed from our backup system, as these accounts may cause the server to overload during the backup process. Shared accounts in excess of 200,000 inodes are at risk of suspension. Before suspension, warning messages will be sent to your email on file; if no action is taken, the account may be suspended.
Customers are allowed to configure cron jobs to perform repeated functions on our shared servers. Cron jobs that take more than half the time to complete before the next scheduled run or jobs that run more frequently than 15 minutes will be considered abusive. Any cron that is found to be in violation of this policy or affecting the performance of the server may be disabled.
Back to top of page