The article is very light on technical details, and tries to imply some advanced things with the whole "mesh network" terminology. In almost every product like

The article is very light on technical details, and tries to imply some advanced things with the whole "mesh network" terminology. In almost every product like this I've seen, it's not load-sharing a single session (like a Skype call) across multiple Internet connections, but instead sharing/routing particular sessions to particular networks. Skype for instance is relatively low-bandwidth, but latency sensitive. Downloads are high bandwidth, and less concerned with latency (within reason). The router can make decisions, most likely based on the protocols and/or ports of the session, and route each session to the most appropriate outbound Internet connection. You can aggregate multiple pipes into one larger "bonded" connection, but this would generally require equipment on both ends of that connection. Technically, feasible, but most likely not in this case. They could also use the mesh network to route some packets, or segments (eg: bunch of packets in a row) to the best outbound pipe, which would be selected based some continuous ping tests (in essence). You could probably make that happen with transparency to the end user, even in Skype. In the end, from the very limited info, this sounds like the next rev of basic multi-homed "load sharing" routers that have been around forever, just with a new twist.