Monthly Archives: July 2013

What Is A Bonded T1?

Understanding what a bonded T1 is, and what it brings to the table, is not as more information complicated as some people make it out to be. For T1 bandwidth specifically, your choices are fractional T1, T1, and bonded T1. In other words ? part of a T1, a full T1 line, or X number of T1s connected to deliver whatever bandwidth capacity you need met.

The benefit of a bonded T1 service is that it eliminates overtaxing of a single T1. If your required bandwidth is more than what a full T1 delivers ? but less than a DS3 line ? then a bonded T1 is a smart choice.
Bonded T1’s are basically 2 or more T1’s that are connected to make a fatter pipe. This does confuse a lot of people so let me try and explain with a few examples.

Lets assume you have 2 T1’s bonded together ?.

If you have to download a file from the web that is 300Mbits in size then it would take 100 seconds to down load that file (300Mbit file/3Mbits per second bandwidth). This is because the bonded T1’s appear to be one large pipe.

Taking the same example but now you have 2 unbonded T1’s.

You still have a total of 3Mbits per second bandwidth, however if you have to download one file that’s 300Mbits in size it will take 200 seconds. This is because you only have 1.5Mbits per second bandwidth available as the file cannot be split and sent down both T1’s at the same time. The other T1 is not used for this transfer but is available for other traffic.

If you had two 300Mbit files to download then it would take 200 seconds to download in either scenario.

Bonded T1’s only help if you transfer large data files and time is critical. If time is not an issue and the data transfer is not large then bonded T1’s won’t help much. In that case stick with a full T1 line or look at the availability of Business Ethernet. Please note tt some point you鎶 reach a point of diminishing return with a bonded T1 share this site solution. For both capacity and cost. If that is a concern than fractional or full DS3 bandwidth is a better option.

The key is to understand first what your typical use load will be. Also consider what your peak load parameters would look like. Then design your solution around those two analyzed scenarios.