Frequently Asked Questions

For a bond with only DSL connections, you will get almost the full combined speed of each connection. For example, a site with three 6 Mbps down/1 Mbps up DSL lines will be able to download at nearly 18 Mbps and upload at close to 3 Mbps, with compression disabled.

Yes, we have data compression which can compress data up to 3-5 times. See the Performance page for more information and examples. We have many more WAN optimization features in the roadmap.

Absolutely. Our product includes quality of service (QoS) features to prioritize VoIP and other interactive applications over bulk traffic. This means that protocols such as SIP/RTP, ICMP, and SSH are sent before non-interactive data such as web, mail, and FTP transfers. This prioritization is performed for both the outbound and inbound connections.

Your VoIP traffic benefits from all of the other benefits of bonded internet plus QOS, even over broadband circuits.

You will not experience any downtime when a connection fails. For example, view the failover demo video. Bonded Internet detects connection failure within 0.3 seconds and automatically removes the failed line from the bond. Bonded Internet begins using the line again within 0.1 seconds when connectivity is restored.

No. Bonded Internet is completely transparent to your network as well as to inbound traffic. You will only need to reconfigure your firewall or router with a new Static IP Address.

No. Unlike load balancing solutions, our service requires no complicated DNS configuration. Your firewall is assigned a public, static IP address. All incoming traffic uses that address regardless of the traffic load or whether any connections in the bond have failed.

Yes, you can add Internet connections at any time. If you have multiple lines from a single provider, adding any combination of cable, fixed wireless, or DSL connections from another provider is a great way to increase the reliability of your bonded connection, while achieving the bandwidth required by your organization.

There is no limit to the number of connections that can be bonded.

No. We are constantly improving our software to bring you greater performance and reliability. You will receive these updates as part of the monthly software licensing fees.

Yes. If this is not an option, we can connect you with another partner so that you can work together.

Yes, we fully expect you to do that.

A key part of our product is a centralized configuration server. Technicians use a web application on this server to manage, monitor, and report on each CPE.

Each CPE is connected to a management server that remotely controls its configuration. Your technicians use a private web-based application to manage all devices, connections, reporting, and monitoring. You never need to update configuration files on the device using CLI commands – all configuration is web-based.

You need to provide the following: Server hardware for the configuration server.

Server hardware for at least one, but preferably two aggregation servers.

Bandwidth to the aggregators appropriate for the amount of traffic you expect your customers to use.

A small network and server for CPE provisioning using PXE boot.

IP addresses for each server, as well as a public /30 or larger subnet for each CPE. After you provide remote access to your servers, we will configure the environment and network.

Use the web interface to configure their options, Internet connection info, and bonded IP address. The system will assign an API key to their CPE. Then boot the CPE on the provisioning network, providing the API key when requested. The whole process takes less than 20 minutes, most of which is the CPE configuring its operating system automatically.

Once your new server hardware is racked up and connected, you can use our ISO image to install the software. The procedure is nearly identical to deploying a CPE bonder. The software install and configuration process can take as little as 15 minutes once the hardware is online.

Yes. Redundant aggregators can be configured upon request. Alternatively, in the event of a failure you can use the web interface to switch a customer to a different aggregation server. We will add support for application-level aggregator failover in a future release.

Redundant config servers can be added upon request. Note that a failed configuration server has no effect on customer traffic; only management, monitoring, and reporting functions are impacted.