Thread Mesh Calculator: Border Routers, Hops and Fabric Limits
Compare planned Thread layouts before buying: how many hops the mesh forces, how much load funnels through each border router, and whether the design has any redundancy at all. The model behind these figures is written out below.
How these numbers are derived
This is a planning heuristic, not a measurement. Nothing here is instrumented against live hardware, and the figures should be read as the shape of a relationship rather than a prediction of what your house will do. The model is deliberately simple and stated in full so you can judge it:
- Average hops is estimated as end devices divided by mains-powered Thread routers, rounded up, with a floor of one. Only mains-powered devices relay; battery sensors sleep and consume mesh capacity rather than adding it.
- Modelled mesh latency is
5 ms + (3.5 ms × hops) + (1.5 ms × fabrics). The base cost stands in for radio and controller overhead, the per-hop increment for each relay a packet crosses, and the per-fabric increment for the extra session state a device carries for every fabric it belongs to. Those three constants are chosen to produce sensible relative behaviour; they are not measured values, which is why the output is only useful for comparing one planned layout against another. - Egress pressure bands end devices per border router as a proxy for how much traffic funnels through a single exit point: Low up to 30 per border router, Elevated above 30, High above 60. It is deliberately not expressed as a loss percentage, because nothing here measures one.
- Border router status is binary: a single border router is a single point of failure for every Thread device in the house, because its reboots take the mesh's route to the IP network with them.
Real latency depends on channel congestion, physical layout, device firmware, and how much 2.4 GHz noise the house generates. Use this to compare two planned layouts against each other, not to predict absolute response times.
Fabric count is a planning input, not a device's supported fabric limit. Check the device documentation and the Matter multi-admin sharing guide before adding another controller. The redundancy model also assumes that border routers share one Thread network and provide reachable alternate paths.
Background reading
- Matter vs Thread vs Border Router: How the Layers Stack explains the layering the inputs above assume.
- The Thread border router guide covers which products contain one and where to place them.
- Thread vs Zigbee sets out what the two meshes share and where they diverge.
- Matter pairing failures is the fix list for when commissioning breaks.