Fusion Central

Fleet

Server	Endpoint	Status	Clients	Capacity	Uptime	Last seen

Fleet history

Throughput Mbit/s, all headends

Clients online and headends up

Bond latency avg probe RTT · worst reorder hold p99

Loss avg bond loss · probe loss

My capacity

Purchases

Date	Capacity	Duration	Amount	Status	Reference

My devices

Device	Tunnel IP	License	Speed	Status	Expiry	Online	Actions

Help & guide

Getting started

Welcome! Your portal has two ideas: licenses (blocks of bonded capacity you own) and devices (the individual routers that use that capacity). Buy or activate a license, create a device under it, then flash the device's key into your CPE. Everything below walks through each step.

Licenses vs devices

A license is a pool of capacity (e.g. 500 Mbps) with a duration. Its countdown starts when the first device under it connects.
A device is one router/site. It draws a slice of speed from a license and inherits that license's remaining term.
You can split one license across many devices, up to its capacity — the My capacity cards show how much is used vs available.

Operating the bond via the client UI

Mode: Stability In this mode; latency, capacity and reliability are constantly monitored and distribution over over all the links is adjusted to maintain the best possible performance for both bandwidth and stability..
Mode: Max Bandwidth In this mode the bond will prioritize bandwidth over stability. This mode is ideal for applications that require high-speed connectivity and minimal latency, such as video streaming or online gaming.
Mode: Redundant In this mode, all links are used simultaneously and only the first packet to arrive at headend is used meaning if a packet from one link is lost the next available packet is used from another link. No aggregation, maxmimum uptime.
Mode: Round Robin In this mode the bond will distribute the traffic across available links based on the percentage set in the the link table.
Direction pinning In the link table on the client UI, there are options to pin a link to a specific direction (up or down). This is useful when you have a link that is not stable and you want to pin it to a specific direction to avoid it from being used in the bond. If a pinned link is down, the bond will automatically switch to the next available link in the direction of the pinned link.
MTU By default MTU is set to 1400 bytes. This can be changed in the settings section of the client UI. Setting it higher might result in fragmentation. For running vpns over the bond, account for the vpn overhead by reducing mtu accordingly.
Jitter Budget By default jitter budget is set to 150ms. This can be changed in the settings section of the client UI. Reducing the jitter budget means packets over that latency will be discared from aggregation.

Buying capacity

Under Buy more capacity, enter the Mbps and number of days — the price updates live. Pay securely in the popup; once it clears, a new license appears automatically in My capacity with its own expiry date. Buying again always creates a separate license, so packages never overwrite each other.

Adding a device

In My devices, choose the license to draw from, give the device a name and a speed (Mbps), then Add device. You'll get:

a tunnel IP — the device's stable address on the bonded network;
a key — the secret you put in that CPE's config so it can connect.

Speed can't exceed the license's free capacity. Removing a device frees its capacity back to the license.

Reading status & graphs

Each device shows a status: Active (running), Grace (term lapsed, still served briefly — renew soon), Expired (stopped), Suspended (paused by an operator) or Perpetual (no expiry). Click a device to see its graphs. The bond charts show what your users actually get: combined throughput, end-to-end latency (the probe RTT through the tunnel, plus how long packets waited to be re-ordered), and loss. Below them the per-link charts — RTT, loss, throughput, jitter — tell you which WAN is carrying the bond. Use the range picker (Live · 1h · … · 90d) to look back up to three months; markers on the charts and the event list underneath flag link changes, reconnects and probe-loss episodes.

Need more help?

Something not adding up? Reach your provider's support team with your account email and the device name — they can see your fleet health and sort it quickly. (More guides will land here over time.)

Fusion Central

Fleet

Throughput Mbit/s, all headends

Clients online and headends up

Bond latency avg probe RTT · worst reorder hold p99

Loss avg bond loss · probe loss

Connected clients

Throughput Mbit/s

Clients online

Bond latency avg probe RTT · worst hold p99

Loss avg bond loss · probe loss

Bond throughput Mbit/s

Bond latency ms · probe RTT, reorder hold p50/p99

Bond loss %

Active links

Link RTT (ms)

Link loss (%)

Link throughput down, Mbit/s

Link jitter (ms)

Estate health

Login profiles

Devices

My capacity

My estate

Buy more capacity

Purchases

Package downloads

My devices

Bond throughput Mbit/s

Bond latency ms · probe RTT, reorder hold p50/p99

Bond loss %

Active links

Link RTT (ms)

Link loss (%)

Link throughput down, Mbit/s

Link jitter (ms)

Help & guide

Sign in

Create account

Fleet

Throughput Mbit/s, all headends

Clients online and headends up

Bond latency avg probe RTT · worst reorder hold p99

Loss avg bond loss · probe loss

Connected clients

Throughput Mbit/s

Clients online

Bond latency avg probe RTT · worst hold p99

Loss avg bond loss · probe loss

Bond throughput Mbit/s

Bond latency ms · probe RTT, reorder hold p50/p99

Bond loss %

Active links

Link RTT (ms)

Link loss (%)

Link throughput down, Mbit/s

Link jitter (ms)

Estate health

Login profiles

Devices

My capacity

My estate

Buy more capacity

Purchases

Package downloads

My devices

Bond throughput Mbit/s

Bond latency ms · probe RTT, reorder hold p50/p99

Bond loss %

Active links

Link RTT (ms)

Link loss (%)

Link throughput down, Mbit/s

Link jitter (ms)

Help & guide