We will NEVER put more than 200 shared hosting accounts on any single server under any circumstances. In fact, if there are more customers who purchased  higher resource packages on the server, then there will be even less number of hosting accounts on the server. 

Here's an example: Since we have 800 GB of disk space on each server to distribute to our customers, we may either host 200 customers who need 4 GB disk space OR 50 customers who need 16 GB disk space. There may be various mix-n-match until the entire 800 GB of disk space is fully distributed. However, we will NEVER put 200 customer accounts with 16 GB disk quota per account because that will trigger an oversold condition, which is strictly against our Zero Overselling Policy.

At GigaPros, each server is equipped with 1000 GB of hard disk. Every hard disk is fault tolerant thru RAID mirrors. Out of the total 1000 GB of disk space, we reserve 200 GB for the operating system, server software, swap space etc. The remaining 800 GB of disk space is distributed among a maximum of 200 customers. So, each customer gets a guaranteed minimum disk space of 4 GB. However, you can always buy / upgrade to higher package if you need more disk space.

* Storage limit does not apply to Unlimited Plan.

At GigaPros, each server has a total bandwidth (traffic) limit of 6000 GB per month. Out of the total 6000 GB of bandwidth, we reserve 1000 GB for administrative purposes such as downloading updates for operating system, updates for server software, daily backups, server monitoring etc. The remaining bandwidth of 5000 GB is distributed among a maximum of 200 customers. So, each customer gets a guaranteed minimum bandwidth of 25 GB per month. However, you can always buy / upgrade to a higher package if you need more bandwidth.

* Bandwidth limit does not apply to Unlimited Plan.

Unless your site is very script intensive, you will not hit this CPU usage limit. And if you do, then it's time to upgrade your shared account to a Semi-Dedicated account or a VPS or a Dedicated Server. To calculate your CPU usage, we record the CPU used by all your processes every 1 minute. Then we take the 5-minute average of that sampling, which must be within 5% limit. If it crosses 5% consistently, then we'll be contacting you to let this know and you will have an option to upgrade.

Under normal circumstances, a shared hosting account generally uses 1-5 processes simultaneously. However, if your account creates more than 25 processes & keeps them running simultaneously, it indicates that either you are running a very poorly coded script that can’t handle the processes efficiently or you are intentionally abusing the server. In such case, all those 25 processes will be automatically killed immediately to maintain the stability of the server. By "killing", we just mean to remove those processes from the RAM (& NOT to delete any of your files or settings). If this condition keeps occurring consistently, we'll notify you about this situation, so that you may fix the offending scripts.

NOTE: This parameter has NOTHING to do with how many users can browse your site simultaneously. To understand the significance & usage of this parameter, you should either be a programmer or must have understanding about how an operating system (like Linux) manages it’s processes. The above limit is good enough for your account unless you are running a very poorly coded script or intentionally abusing the server.

Under normal circumstances, when a script in a shared hosting account creates a new process, it generally runs for a few seconds. And once the script completes it's task, the process is automatically disposed off and flushed out from the RAM. However, if the same process keeps running for more than 1800 seconds, we consider it to be stuck in an endless loop and the process will be automatically killed. By "killing", we just mean to remove the offending process from the RAM (& NOT to delete any of your files or settings). If this condition keeps occurring consistently, we'll notify you about this situation, so that you may fix your offending scripts.

NOTE: The above limit is good enough for your account unless you are running a very poorly coded script or intentionally abusing the server.

Under normal circumstances, a shared hosting account typically uses about 1-20 MB of RAM while serving web pages, reading SQL databases, writing files etc. This is good enough even for a fairly busy website.

However, to handle any occasional RAM spikes that your account may cause, we have set the highest spike of RAM usage limit to 100 MB. This is maximum amount of RAM that will be available to your account. However, if you account keeps hitting the max RAM limit very frequently, we'll notify you about this situation and discuss about the possible reasons & resolutions.

You can upload any file as big as 200MB. You can upload any number of such files as long as you stay within your allocated disk-space quota. The larger file-size enables you to run your video streaming sites effortlessly.

An inode is a data structure used to keep information about a file on your hosting account. This indicates the number disk entries needed to store everything on your account like emails, files, folders, anything you store on the server.

Cronjobs are used to run a script repeatedly after a fixed interval of time. You must choose an interval of MORE THAN 5 minutes to run any of your cronjobs. We DO NOT allow any cronjob to be scheduled at less than 5 minutes interval.

Each of your MySQL databases must be less than 2 GB in size. If any of your database exceeds this limit, we'll notify about this issue so that you may resolve this issue. You may either delete the unnecessary records from your database or you may split the bigger database into multiple smaller databases.

Each db_username can establish a maximum of 20 simultaneous connections with any of your databases. For an explanation of db_username, see the notes below. 

If you reach the above limit, any further new connections will be denied with a database error code# of 1203. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can initiate a maximum of 5,000 new connections with any of your databases. For an explanation of db_username, see the notes below.

If you reach the above limit, any further new connections will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can execute a maximum of 50,000 database READ queries. A database READ query consists of a database command that can read database records or schema. An example is "SELECT" command. For an explanation of db_username, see the notes below.

If you reach the above limit, any further database queries will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can execute a maximum of 10,000 database MODIFY queries. A database MODIFY query consists of a database command that can modify database records or schema. Some examples are: INSERT, UPDATE, DELETE, CREATE, ALTER etc. For an explanation of db_username, see the notes below.

If you reach the above limit, any further database queries will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

Each unique external IP address can establish a maximum of 50 concurrent connections to your website (thru Apache web server). As soon as this limit is exceeded, the offending external IP will be blocked from accessing your website for the next 1 hour.

NOTE: The above scenario is a potential indication of HTTP Denial-of-Service attack towards your website. Blocking the offending external IP may save your website from becoming inaccessible to your legitimate site-visitors due to unnecessary flooding of connections.

During a period of 1 hour, your account can send a maximum of 1000 outgoing e-mails.

Each e-mail can have a total attachments of 10 MB maximum.

If you are using a POP3 complaint external e-mail clients (like Microsoft Outlook), you may connect to your mailbox periodically to check / retrieve your e-mails. In 1 hour period, you can connect a maximum of 120 times to your mailbox.

We will NEVER put more than 15 hosting accounts on any single server under any circumstances. In fact, if there are more customers who purchased  higher resource packages on the server, then there will be even less number of hosting accounts on the server.

At GigaPros, each server is equipped with 1000 GB of hard disk. Every hard disk is fault tolerant thru RAID mirrors. Out of the total 1000 GB of disk space, we reserve 200 GB for the operating system, server software, swap space etc. The remaining 800 GB of disk space is distributed among a maximum of 200 customers. So, each customer gets a guaranteed minimum disk space of 50 GB. However, you can always buy / upgrade to higher package if you need more disk space.

At GigaPros, each server has a total bandwidth (traffic) limit of 8000 GB per month, which is distributed among a maximum of 15 customers. So, each customer gets a guaranteed minimum bandwidth of 500 GB per month. However, you can always buy / upgrade to a higher package if you need more bandwidth.

Unless your site is very script intensive, you will not hit this CPU usage limit. And if you do, then it's time to upgrade your semi-dedicated account to a VPS or a Dedicated Server. To calculate your CPU usage, we record the CPU used by all your processes every 1 minute. Then we take the 5-minute average of that sampling, which must be within 10% limit. If it crosses 10% consistently, then we'll be contacting you to let this know and you will have an option to upgrade.

Under normal circumstances, a semi-dedicated hosting account generally uses 10-15 processes simultaneously. However, if your account creates more than 50 processes & keeps them running simultaneously, it indicates that either you are running a very poorly coded script that can’t handle the processes efficiently or you are intentionally abusing the server. In such case, all those 50 processes will be automatically killed immediately to maintain the stability of the server. By "killing", we just mean to remove those processes from the RAM (& NOT to delete any of your files or settings). If this condition keeps occurring consistently, we'll notify you about this situation, so that you may fix the offending scripts.

NOTE: This parameter has NOTHING to do with how many users can browse your site simultaneously. To understand the significance & usage of this parameter, you should either be a programmer or must have understanding about how an operating system (like Linux) manages it’s processes. The above limit is good enough for your account unless you are running a very poorly coded script or intentionally abusing the server.

Under normal circumstances, when a script in a semi-dedicated hosting account creates a new process, it generally runs for a few seconds. And once the script completes it's task, the process is automatically disposed off and flushed out from the RAM. However, if the same process keeps running for more than 3600 seconds, we consider it to be stuck in an endless loop and the process will be automatically killed. By "killing", we just mean to remove the offending process from the RAM (& NOT to delete any of your files or settings). If this condition keeps occurring consistently, we'll notify you about this situation, so that you may fix your offending scripts.

NOTE: The above limit is good enough for your account unless you are running a very poorly coded script or intentionally abusing the server.

Under normal circumstances, a semi-dedicated hosting account typically uses about 20-50 MB of RAM while serving web pages, reading SQL databases, writing files etc. This is good enough even for a fairly busy website.

However, to handle any occasional RAM spikes that your account may cause, we have set the highest spike of RAM usage limit to 250 MB. This is maximum amount of RAM that will be available to your account. However, if you account keeps hitting the max RAM limit very frequently, we'll notify you about this situation and discuss about the possible reasons & resolutions.

You can upload any file as big as 500MB. You can upload any number of such files as long as you stay within your allocated disk-space quota. The larger file-size enables you to run your video streaming sites effortlessly.

An inode is a data structure used to keep information about a file on your hosting account. This indicates the number of disk entries needed to store everything on your account like emails, files, folders, anything you store on the server.

Cronjobs are used to run a script repeatedly after a fixed interval of time. You must choose an interval of MORE THAN 5 minutes to run any of your cronjobs. We DO NOT allow any cronjob to be scheduled at less than 5 minutes interval.

Each of your MySQL databases must be less than 2 GB in size. If any of your database exceeds this limit, we'll notify about this issue so that you may resolve this issue. You may either delete the unnecessary records from your database or you may split the bigger database into multiple smaller databases.

Each db_username can establish a maximum of 60 simultaneous connections with any of your databases. For an explanation of db_username, see the notes below. 

If you reach the above limit, any further new connections will be denied with a database error code# of 1203. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can initiate a maximum of 10,000 new connections with any of your databases. For an explanation of db_username, see the notes below.

If you reach the above limit, any further new connections will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can execute a maximum of 100,000 database READ queries. A database READ query consists of a database command that can read database records or schema. An example is "SELECT" command. For an explanation of db_username, see the notes below.

If you reach the above limit, any further database queries will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can execute a maximum of 20,000 database MODIFY queries. A database MODIFY query consists of a database command that can modify database records or schema. Some examples are: INSERT, UPDATE, DELETE, CREATE, ALTER etc. For an explanation of db_username, see the notes below.

If you reach the above limit, any further database queries will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

Each unique external IP address can establish a maximum of 100 concurrent connections to your website (thru Apache web server). As soon as this limit is exceeded, the offending external IP will be blocked from accessing your website for the next 1 hour.

NOTE: The above scenario is a potential indication of HTTP Denial-of-Service attack towards your website. Blocking the offending external IP may save your website from becoming inaccessible to your legitimate site-visitors due to unnecessary flooding of connections.

During a period of 1 hour, your account can send a maximum of 2000 outgoing e-mails.

Each e-mail can have a total attachments of 30 MB maximum.

If you are using a POP3 complaint external e-mail clients (like Microsoft Outlook), you may connect to your mailbox periodically to check / retrieve your e-mails. In 1 hour period, you can connect a maximum of 120 times to your mailbox.

We will NEVER put more than 30 reseller hosting accounts on any single server under any circumstances. In fact, if there are more customers who purchased  higher resource packages on the server, then there will be even less number of reseller hosting accounts on the server. 

Please note that each of the reseller hosting accounts have the capability of creating any number of CPanel accounts within itself, as long as the reseller account remains within the limit of total disk space and bandwidth allocated to it.

At GigaPros, each server is equipped with 1000 GB of hard disk. Every hard disk is fault tolerant thru RAID mirrors. Out of the total 1000 GB of disk space, we reserve 200 GB for the operating system, server software, swap space etc. The remaining 800 GB of disk space is distributed among a maximum of 30 reseller accounts.

At GigaPros, each server has a total bandwidth (traffic) limit of 6000 GB per month. Out of the total 6000 GB of bandwidth, we reserve 1000 GB for administrative purposes such as downloading updates for operating system, updates for server software, daily backups, server monitoring etc. The remaining bandwidth of 5000 GB is distributed among a maximum of 30 reseller accounts.

Unless your site is very script intensive, you will not hit this CPU usage limit. And if you do, then it's time to upgrade your reseller account to a VPS or a Dedicated Server account. To calculate your CPU usage, we record the CPU used by each of your resold users every 1 minute. Then we take the 5-minute average of that sampling, which must be within 5% limit. If it crosses 5% consistently, then we'll be contacting you to let this know and you will have an option to upgrade.

Under normal circumstances, a Cpanel hosting account generally uses 1-5 processes simultaneously. However, if any of your CPanel account creates more than 25 processes & keeps them running simultaneously, it indicates that either you are running a very poorly coded script that can’t handle the processes efficiently or you are intentionally abusing the server. In such case, all those 25 processes will be automatically killed immediately to maintain the stability of the server. By "killing", we just mean to remove those processes from the RAM (& NOT to delete any of your files or settings). If this condition keeps occurring consistently, we'll notify you about this situation, so that you may fix the offending scripts.

NOTE: This parameter has NOTHING to do with how many users can browse your site simultaneously. To understand the significance & usage of this parameter, you should either be a programmer or must have understanding about how an operating system (like Linux) manages it’s processes. The above limit is good enough for your CPanel account unless you are running a very poorly coded script or intentionally abusing the server.

Under normal circumstances, when a script in a CPanel hosting account creates a new process, it generally runs for a few seconds. And once the script completes it's task, the process is automatically disposed off and flushed out from the RAM. However, if the same process keeps running for more than 1000 seconds, we consider it to be stuck in an endless loop and the process will be automatically killed. By "killing", we just mean to remove the offending process from the RAM (& NOT to delete any of your files or settings). If this condition keeps occurring consistently, we'll notify you about this situation, so that you may fix your offending scripts.

NOTE: The above limit is good enough for any CPanel account unless you are running a very poorly coded script or intentionally abusing the server.

Under normal circumstances, a CPanel hosting account typically uses about 1-20 MB of RAM while serving web pages, reading SQL databases, writing files etc. This is good enough even for a fairly busy website.

However, to handle any occasional RAM spikes that your account may cause, we have set the highest spike of RAM usage limit to 100 MB. This is maximum amount of RAM that will be available to your account. However, if you account keeps hitting the max RAM limit very frequently, we'll notify you about this situation and discuss about the possible reasons & resolutions.

You can upload any file as big as 200MB. You can upload any number of such files as long as you stay within your allocated disk-space quota. The larger file-size enables you to run your video streaming sites effortlessly.

An inode is a data structure used to keep information about a file on your hosting account. This indicates the number of disk entries needed to store everything on your account like emails, files, folders, anything you store on the server.

Cronjobs are used to run a script repeatedly after a fixed interval of time. You must choose an interval of MORE THAN 5 minutes to run any of your cronjobs. We DO NOT allow any cronjob to be scheduled at less than 5 minutes interval.

Each of your MySQL databases must be less than 2 GB in size. If any of your database exceeds this limit, we'll notify about this issue so that you may resolve this issue. You may either delete the unnecessary records from your database or you may split the bigger database into multiple smaller databases.

Each db_username can establish a maximum of 20 simultaneous connections with any of your databases. For an explanation of db_username, see the notes below. 

If you reach the above limit, any further new connections will be denied with a database error code# of 1203. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can initiate a maximum of 5,000 new connections with any of your databases. For an explanation of db_username, see the notes below.

If you reach the above limit, any further new connections will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can execute a maximum of 50,000 database READ queries. A database READ query consists of a database command that can read database records or schema. An example is "SELECT" command. For an explanation of db_username, see the notes below.

If you reach the above limit, any further database queries will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

In 1 hour period, each db_username can execute a maximum of 10,000 database MODIFY queries. A database MODIFY query consists of a database command that can modify database records or schema. Some examples are: INSERT, UPDATE, DELETE, CREATE, ALTER etc. For an explanation of db_username, see the notes below.

If you reach the above limit, any further database queries will be denied with a database error code# of 1226. You can use this error code in your script's error handling routines.

NOTE: A db_username is used to access your MySQL databases. You can create a db_username in your CPanel's "Manage MySQL Databases" screen. This is NOT your Cpanel's username.

Each unique external IP address can establish a maximum of 50 concurrent connections to your website (thru Apache web server). As soon as this limit is exceeded, the offending external IP will be blocked from accessing your website for the next 1 hour.

NOTE: The above scenario is a potential indication of HTTP Denial-of-Service attack towards your website. Blocking the offending external IP may save your website from becoming inaccessible to your legitimate site-visitors due to unnecessary flooding of connections.

During a period of 1 hour, your account can send a maximum of 1000 outgoing e-mails.

Each e-mail can have a total attachments of 10 MB maximum.

If you are using a POP3 complaint external e-mail clients (like Microsoft Outlook), you may connect to your mailbox periodically to check / retrieve your e-mails. In 1 hour period, you can connect a maximum of 120 times to your mailbox.