Looking for a Splynx Alternative?
How Veloxiom compares on billing, RADIUS, multi-vendor support and Greek e-invoicing — and where migration actually saves you time.
NOC · BGP egress optimization
Latency Routing
BGP picks the shortest AS path, not the fastest one. Latency Routing measures the real round-trip time to every prefix your subscribers actually use, through each of your upstreams, and sends the traffic out of the fastest one, automatically and prefix by prefix.
How it works
- 1Measure
A small agent next to your Route Reflector probes every active prefix through each upstream (ICMP, TCP and traceroute), several samples every minute. It only looks at prefixes with real traffic, taken from NetFlow.
- 2Decide
A provider wins only when the gain is real: by default at least 5 ms and 15% faster, stable for two rounds in a row, and never on a link that is above 85% load.
- 3Inject
The chosen route is injected into the Route Reflector with a higher local-pref and no-export. Your routers keep running plain BGP, and nothing leaks to your peers.
- 4Verify
Every switch is checked after it happens. If the path did not get faster, it is reverted and the prefix stays on normal BGP for an hour.
Built for gaming
Game traffic (Riot, Valve, Blizzard and any ASN you add) gets its own, more sensitive thresholds, starting at 2 ms. Its route is then held for 10 minutes, so a match is never moved mid-game. The Gaming tab shows the ping to game servers through each provider.
What you see
- Active and optimized prefixes, the average gain in ms and how much traffic runs on a faster path
- RTT and load per provider over the last 24 hours
- Every switch, revert and capacity skip in the events log
- Search by IP, prefix, ASN or network name
Safe by design
- Dry-run by default. The agent measures and logs every decision without touching a single route. Switch to Live only when you are happy with what you see.
- Kill switch. One click withdraws every injected route, and all traffic returns to the normal BGP best path.
- Fail-safe. If the agent stops, the Route Reflector withdraws its routes on its own.
- Your rules. Pin a prefix to a provider, or exclude it from optimization entirely.
- Out of the traffic path. Customer traffic never passes through the panel. The panel is only the management plane, and the agent runs inside your network.
What you need
- Two or more upstreams with a full BGP table
- A Route Reflector. The panel generates the MikroTik RouterOS v7 configuration, and you apply it yourself, ideally on CHR or a lab first
- A small VM for the agent (Debian 12, 2 vCPU, 4 GB) and NetFlow export from your edge
Every tenant and every standalone install has its own agent and token, and all data stays in its own database.