The second largest aspect of the billing and pricing of collocation services is what they typically refer to as bandwidth charges. This is somewhat misleading of a name because bandwidth typically refers just to the amount of possible data per second that the connection can handle but what the providers are referring to is the amount of data transferred to and from the server for the given billing cycle.
Most providers will include a base amount of data transfers with the basic package and will be referred to by the number of gigabytes (GB) allowed. This can be as small as 2GB per month or as high as several hundred. The providers will also have a fee that will be charged to the customer for data transfers that exceed the amount of allotted bandwidth. Charges can range as low as pennies per GB to several dollars per GB. Be sure of what the rate is before signing any agreements.
Actual billing of the bandwidth charges can be calculated one of two ways by the collocation provider. The most common method is called 95th percentile while the other is the straight data transfer rates. Small servers with low bandwidth usage will typically use the straight data rates while larger servers tend to use the 95th percentile. Let's examine them in more detail.
Colocation America maintains one of the largest and most secure carrier-neutral data centers in the industry, and can now offer you all the bandwidth you'll ever need.
With 12 different carriers delivering 24Gbps of bandwidth into a fully meshed and redundant network data center, Colocation America is able to provide the bandwidth you require to manage your business, at a very competitive rate.
What is the 95th percentile, and why is it useful in measuring bandwidth?
The 95th percentile is the smallest number that is greater than 95% of the numbers in a given set. The reason this statistic is so useful in measuring data throughput is that is gives a very accurate picture of the cost of the bandwidth. Here's an example. Suppose an ISP sells you a T1 line, but you're only using it to access the web. Even though you might frequently download very large files (filling the pipe) your cost to the ISP is negligible, because your usage is intermittent. A single T3 connection to the backbone could easily support hundreds of such downstream customers, and never become saturated. As another example, suppose you are hosting a very busy web site that half-way fills your T1 for several hours every day. This type of bandwidth is more expensive, because your ISP can't oversell their connection to the backbone as effectively. The important thing to realize is that it doesn't cost your ISP anything to sell you a pipe of any particular size - it is the sustained rate of data transfer that costs them money. The sum of the 95th percentile usage of all of an ISP's customers predicts the peak amount of backbone traffic that the ISP will incur (in a given direction).
Here are some examples, ISPs must charge for bandwidth by one of three means:
The 95th percentile calculation is a hard formula to try and explain. The easiest way to explain it is to give an example of how the calculation might be computed after a bit of explanation.
In order to determine the amount of data transferred to a server, the provider will monitor the network port that a server is attached to. Every 3 to 5 minutes, they will get a reading for the data transfer rate recorded over that time period. These are then stored in a database. At the end of the billing cycle, the database is queried for the entry that is the 95th percentile in overall size. This number is ten put into the formula such as this: (95th Percentile rate) x (billing cycle length) = Bandwidth usage.
Now, this in general will benefit most individuals since most network connections are idle for the majority of the time they are idle. However, if a site has a high sustained data transfer rate that is used for more than 5% of the time the link is up, it can be very expensive. Let's look at two examples using a shorter time span of 1 day to make it simple.
Over a 30 day period, a Web server gets about 30GB of traffic. For 28 of these days, the traffic consists of only .5GB/day. The last two days has 8GB/day of traffic. In this case of bursting traffic, the 95th percentile would be around .5GB/day. Using the 95th percentile calculation, the bandwidth charge would be: (.5GB/day) * (30days) = 15GB
Over a 30 day period, a Web server gets about 30GB of total traffic. For 20 of these 30 days, there is only a small amount of traffic that doesn't add up at a single GB. The remaining 10 days sees traffic of 3GB/day. The 95ht percentile in this case would be 3GB. Using the 95th percentile calculation, the bandwidth charge would be: (2GB/day) * (30days) = 90GB
As you can see, the consistent traffic with several days of busting traffic in the first example actually is more beneficial to the customer compared to the second example with its traffic that bursted for more than 5% of the time. Thankfully, the majority of servers on the Internet are going to be similar to example #1 and not example #2.