Update, 12 November 2026: WANplex has launched. This piece is the pre-launch story, written when WANplex was just one line in the RutOS 7.26.1 changelog. Five of my six guesses held up. The one I got wrong: WANplex isn’t built on Bondix, it’s Teltonika’s own service. For how it works, pricing, supported routers and a step-by-step guide to running your own hub on a VPS, read Teltonika WANplex: how it works and how to run your own hub.
On 29 October Teltonika slipped one line into the RutOS 7.26.1 changelog: “WANplex: added WANplex service”. No press release, no wiki page, no explanation. Within hours someone on the Teltonika Community forum was asking what WANplex in RutOS 7.26.1 actually was, and nobody outside Teltonika could tell them. So this is me reading the tea leaves: what was public, how WAN bonding works, and my best guesses at what Teltonika was about to launch.
It also follows on nicely from earlier this week, when I asked whether a remote site really needs managed bonded 4G or whether a second router will do. If WANplex is what I think it is, it adds a new option to that list.
The short answer, as it stood before launch: nobody outside Teltonika knew exactly what WANplex was. What was public was a new service in RutOS 7.26.1, a router service page that pointed you to RMS to configure it, and a Teltonika statement that the full release and documentation were coming later in November. Everything pointed to WAN bonding managed from RMS.
What was public about WANplex in RutOS 7.26.1
| What | What was public | Where from |
|---|---|---|
| Firmware | “WANplex: added WANplex service” in RutOS 7.26.1, released 29 October 2026 | Teltonika wiki changelogs |
| Routers | Listed for the RUTX firmware build and the RUTC50; forum users reported seeing it on the RUTX11 and RUTX12 | Teltonika wiki and Community |
| Configuration | The service page in the router refers you to RMS | Teltonika Community |
| API | Teltonika’s Web API reference for the RUTX12 on 7.26.1 includes a WANplex status call | Teltonika developers site |
| Launch | Teltonika’s team said the full release, documentation and supported devices were planned for later in November | Teltonika Community, 3 November |
That was it. No pricing, no device list, no explanation of what it did. Everything below that table is me joining the dots.
How WAN bonding works
Worth a quick refresher, because bonding and failover still get muddled in quotes. RutOS already does failover and load balancing natively. Failover waits for a link to die, then moves you over. Load balancing spreads separate sessions across links, so one big upload still rides one SIM. Bonding splits traffic across every link at once and reassembles it at a server at the far end, so a single session uses all of them and survives any one dropping.
That hub is the whole game. Managed services like CSL’s Outpost run it for you. Self-managed bonding means building it yourself: before WANplex, on Teltonika that usually meant Bondix, installed from the RutOS Package Manager with a Bondix server at the far end, which I covered in bonded 5G with Bondix on the RUTM52. Teltonika and Bondix also ran a joint webinar in September on bonded routers for critical networks, so bonding was clearly high on Teltonika’s list.
My pre-launch guesses
Here’s where I stuck my neck out. I’ve left the guesses as I wrote them, and marked each one now that Teltonika has launched.
- It’s bonding, plus smarter failover. The name gives it away: multiplexing your WANs. I’d expect true bonding for throughput and some form of quality-based failover that moves traffic off a struggling link before it dies outright. Verdict: right.
- It lives in RMS, probably under an SD-WAN banner. The router already points you to RMS to configure it. Teltonika already runs RMS Connect and RMS VPN there, so an SD-WAN section sitting alongside them would be the obvious home. Verdict: right.
- You’ll still need a hub, and I’d bet you can run your own. RMS VPN hubs are hosted by Teltonika, but a bonding hub carries every byte of a site’s internet traffic. My guess is that RMS will let you define a hub and run the server end yourself, quite possibly on a Linux VPS. Verdict: right.
- Hub resilience will be built in. A single hub is a single point of failure for every site behind it. I’d expect a primary and backup hub option from day one. Verdict: right.
- It starts with the higher-end routers. The RUTX range and the RUTC50 are already in the changelog. The dual-modem RUTM range would be the obvious next step. Verdict: right, and RUTM was there from launch.
- It’s built on Bondix, or at least borrows from it. One forum reply assumed exactly that. Verdict: wrong. WANplex is Teltonika’s own service, and Bondix carries on as a separate option.
One idea I still want to test: a RUTC50 already has a 5G modem built in, and bonding normally treats an Ethernet WAN as just another internet connection. Turn a couple of its LAN ports into WANs, hang a RUT200 off each one with its own SIM, and you’d have a home-built multi-modem bonded box, a bit like a DIY Outpost. As I said in the CSL piece, more SIMs isn’t the same as more resilience when the UK only has three mobile network groups, but it’s an intriguing build.
If you run your own hub, size it properly
A self-hosted bonding hub lives or dies on a few things people tend to skip:
- CPU matters more than you’d think. Every packet from every site is encrypted, reordered and reassembled at the hub. A tiny VPS that’s fine for one site can fall over with twenty uploading at once.
- Test with everything live. One fast tunnel on the bench tells you very little. Watch CPU, packet loss, latency and data transfer charges with all sites running, and try a single TCP flow as well as a multi-stream test.
- Price the egress. Cloud providers charge for traffic leaving a server, and a bonded site sends all its internet traffic out through yours. On a busy CCTV site that can cost more than the server.
- Lock it down. A bonding hub with its admin interface open to the internet is a gift to somebody.
Teltonika has now published its hub requirements and installer. I’ve written them up, with a VPS setup walkthrough, in the WANplex setup guide.
Quick answers
What did RutOS 7.26.1 add?
RutOS 7.26.1, released on 29 October 2026, added a new WANplex service, listed in the changelogs as “WANplex: added WANplex service”. At the time there was no documentation, and the router’s service page simply referred users to RMS.
When did Teltonika launch WANplex?
Teltonika said on 3 November 2026 that the full release would follow later that month, and it launched WANplex with a product page, pricing and RMS documentation in November 2026.
Is WANplex built on Bondix?
No. WANplex is Teltonika’s own bonding service. Bondix remains a separate third-party option for Teltonika routers.
Where can I find out how to set up WANplex?
The Teltonika WANplex setup guide covers how it works, pricing, supported routers and how to run your own hub on a VPS.
Sources: Teltonika Networks Wiki, RUTX50 and RUTC50 firmware changelogs (RutOS 7.26.1); Teltonika Community, “New WANPlex Service” thread, 29 October to 3 November 2026; Teltonika Networks Web API reference, RUTX12 7.26.1; Teltonika Networks, Teltonika + Bondix webinar, September 2026. Guesses were the author’s speculation ahead of launch; verdicts added after Teltonika’s November 2026 launch.



