Last updated: May 2011.
You may not use our network to engage in illegal, abusive, or irresponsible behaviour, including:
- Unauthorised access to or use of data, services, systems or networks, including any attempt to probe, scan or test the vulnerability of a system or network or to break security or authentication measures without express authorisation of the owner of the system or network;
- Monitoring data or traffic on any network or system without the authorisation of the owner of the system or network;
- Interference with service to any user, host or network including, without limitation, mail bombing, flooding, deliberate attempts to overload a system and broadcast attacks;
- Use of an Internet account or computer without the owner’s authorisation;
- Collecting information by deceit, including, but not limited to Internet scamming (tricking other people into releasing their passwords), password robbery, phishing, security hole scanning, and port scanning;
- Use of xneelo’s service to distribute software that covertly gathers information about a user or covertly transmits information about the user;
- Any activity or conduct that is likely to result in retaliation against our network;
- Any activity or conduct that is likely to be in breach of any applicable laws, codes or regulations including the Electronic Communications and Transactions Act 25 of 2002 (see ECT Act) which renders you liable to a fine or imprisonment;
- Introducing intentionally or knowingly into xneelo’s service any virus or other contaminating program or fail to use an up to date virus-scanning program on all material downloaded from the Web;
- Forging email or other messages is forbidden. Trafficking in pirated software is forbidden. Port scanning or the use of similar tools is forbidden.
- Use of xneelo services to publish or otherwise disseminate information about the availability of pirated software or other material that is being made available illegally, including the publication of a list of links to such material, regardless of disclaimers, is specifically forbidden. We do not condone any illegal material or behaviour.
Compliance with the acceptable use policies of any network or system with which you connect through our service is required. If inappropriate activity is detected, all accounts of the user in question will be deactivated until the investigation is complete. Prior notification to the user is not assured. In extreme cases, law enforcement will be contacted regarding the activity.
Back to top
Combining traffic quotas across multiple servers is not supported
Last updated: September 2014.
First, the general principle regarding quotas:
The generous quotas provided by hosting providers are based on an aggregated usage model. What this means is that each hosting product, at full quota use, runs at a loss.
In reality, 99% of customers use a fraction of their quotas while less than 1% are high or excessive users. As a result, the aggregate usage across the cumulative customer base remains within profitable margins. This makes it entirely feasible to offer quota levels that provides both peace of mind as well as the flexibility for occasional or permanent high usage without raising the cost.
Regarding combined dedicated server traffic quotas:
In the case of Dedicated servers (Managed and Self-Managed) that are combined to deliver a single service, the principle of an aggregated usage model can not be applied. When lumped together to service an ever growing need, it is as though a “super-computer” is being created and the traffic quotas that are allocated to its parts are not subject to an aggregated usage model. In other words, it’s a new product with different product characteristics.
Traffic routed between Colocation Racks and Self-Managed Servers:
Traffic generated from a Colocation network that is destined for the internet should not be routed via a Self-Managed server or network.
An example would be the hosting of a video processing system which requires a large number of servers to perform the required processing, including database, backup and redundancy servers. Combining the quotas of all the servers used for this purpose into a single large quota is simply not feasible due to the loss that this would incur for xneelo.
Other examples are:
Very popular Websites (eg. news24.com)
Large SaaS implementations
Servers used for mass download purposes or caching proxies
Mass mail services (eg. a free Webmail service)
Cloud hosting platforms
99% of customers with clustered servers remain well within the acceptable aggregated data usage pattern. A further 1% may be contacted to discuss a viable quota model. So why do we explain this policy so elaborately? Because we want you to understand the basis on which you are using the service and to give us the recourse to collaborate with you on options should we feel the need to do so.
Very simply, if you are not being contacted, it’s not a concern for us. If you are concerned or would like greater predictability, please contact email@example.com.