OUR NETWORK
By connecting to multiple backbones, Swiftway's data can be distributed through many sources. This architectural design also means that we are not dependent upon any single Internet backbone. Thus when problems occur, we are able to reroute traffic automatically, thereby ensuring the integrity of our network and continued access for our high-speed dedicated server clients. We have taken the term "multi-homing" to a whole new level.
Furthermore, by routing traffic mainly across large Internet backbones and sending data through meet points (commonly referred to as Internet Exchanges), the data traffic from our network avoids centers of high congestion.
Swiftway does not have congestion problems because it pays for usage. Thus, if one connection starts experiencing packet loss, we are responsible for upgrading the circuit. This point also reinforces the advantage of our network architecture. Because we have connections to multiple backbone providers, we utilize their backbones, where there is less data congestion. In addition, though these large backbones may have good networks, they may not provide high-speed hosting solutions because they might have poor connectivity to other large backbones.
Presently bandwidth utilization is below 60% during peak traffic times. Therefore, our network is very flexible. If one of the backbones we connect to experiences problems, we can simply choose to re-route that traffic over other paths, thereby ensuring that users receive fast access times to sites hosted on our network.
In addition, Swiftway runs Border Gate Protocol (BGP4). BGP is used at a provider with more than one access point to the Internet. It helps create a truly redundant network. In fact, in an ideal situation, a lease line failure should result in the BGP routing session to close on the bad leased line and the router on a working circuit should then begin to accept the additional traffic.
In other words, traffic from a down circuit is re-distributed across other circuits, thereby maintaining network integrity. Providers that are multi-homed and correctly setup can actually be more reliable than a single backbone provider because they have multiple paths to multiple.
