How Many Thread Border Routers Do You Need?

If you searched “how many thread border routers do i need”, the short version: one makes Thread devices work, two on the same Thread network is the target for a house that should survive a firmware reboot, and a third or fourth only earns its place by closing a coverage gap. The number that matters more than the border router count is the number of Thread networks in your house. Most people who think they have two border routers actually have two networks with one border router each, which is the worst configuration available, and most of this post is about avoiding it.

One works, two on one network is the goal

A Thread network needs a border router to reach anything outside the mesh, and OpenThread states that “there can be multiple Border Routers in a Thread network” (OpenThread, Node Roles and Types). With one, every Thread device depends on that box. When it reboots for an update, the mesh keeps running internally but loses its route to your controller, so everything Thread goes offline at once from the app’s point of view.

The Thread Group’s white paper makes the redundancy case: “for a shared Thread Mesh, there can be multiple Border Routers that all provide the same routing capabilities redundantly. If one device fails, the others provide seamless, unbroken connectivity to the mesh” (Thread Group, Border Router White Paper). The operative word is shared. Two border routers provide failover only when they hold the same network credentials. Two that each formed their own network provide nothing to each other.

So for a normal apartment or house: two, joined to one network, placed apart. Past that it is a coverage decision.

Count networks before you count border routers

Each ecosystem historically created its own Thread network the first time one of its border routers came online. Home Assistant’s Thread documentation still describes that default: “each vendor forms their own Thread network when you start using their products,” and “these are all separate networks using different credentials. This means devices can’t roam between the Thread networks” (Home Assistant, Thread integration).

The Thread Group named the problem in the 1.4 white paper: “setting up a new Thread Border Router is possible but would typically cause the forming of an entirely new Thread network, in a home where one already exists. This fragmentation of Thread devices over multiple networks could weaken the overall mesh network resilience and connectivity” (Thread Group, Thread 1.4 Features White Paper).

Thread 1.4 answers it with Credentials Sharing: the border router generates a one-time passcode, the app derives a temporary key from it, opens a secure session and pulls the network credentials, which it can hand to a new device or a new border router (Espressif, Thread Network Credentials Sharing). Samsung shipped this to the SmartThings Hub v2, Hub v3 and Aeotec Smart Home Hub in September 2025 as QR or numeric codes (Matter Alpha). Google’s developer docs describe the intended end state: “When a new border router is set up in a home it either creates a new Thread network or joins an existing Thread network” (Google Home Developers, Thread).

Whether the “joins” branch fires in 2026 depends on the vendor pair and the firmware. A merged network is something to verify, not assume.

What you probably already own

Most homes acquire border routers by accident. Before buying a dedicated one, count what is already plugged in:

Vendor	Devices that act as a Thread border router	Source
Apple	HomePod mini, HomePod (2nd gen), Apple TV 4K (2nd gen), Apple TV 4K (3rd gen) Wi-Fi + Ethernet	Apple Support 102078
Google	Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro, Google TV Streamer (4K)	Android Help
Amazon eero	eero 7, Pro 7, PoE 7, Outdoor 7, Max 7, Pro 6E, 6+, Pro 6, 6, PoE 6, eero Pro (Wi-Fi 5), eero Beacon (Wi-Fi 5)	eero Support
Samsung	SmartThings Hub v2, Hub v3, Aeotec Smart Home Hub (Thread 1.4 since September 2025)	Matter Alpha

Two details affect the count. Apple’s list names the Wi-Fi + Ethernet model of the third-generation Apple TV 4K; the Wi-Fi-only variant is not on it. And eero states that “each Thread-capable eero acts as a border router,” so a three-node eero mesh is already three border routers on one network.

Two or more from the same vendor: you are probably done, and the job is verification. Two from different vendors: you have the fragmentation problem until you confirm otherwise.

When a third or fourth actually helps

Extra border routers are a coverage tool, not a reliability multiplier. Two on one network already removes the single point of failure; a third at the far end of a long or multi-floor house shortens the hop count for devices that would otherwise cross several relays to reach an exit.

What an extra border router does not do is fix a mesh with nothing to relay through. Only always-on, mains-powered Thread devices forward traffic. Battery sensors are sleepy end devices that wake “on occasion to poll for messages” from their parent and never relay for anyone else (OpenThread, Node Roles and Types). eero puts it in consumer terms: “eero and other always-on devices like lights and smart plugs also act as Thread routers, forwarding traffic for other devices and extending your Thread network coverage.” If a sensor at the end of the house drops out, a mains-powered plug halfway there is the fix more often than another border router is.

The ceilings are far away for a home. OpenThread caps a network at 32 mesh extenders (the current name for the router role) with up to 511 end devices per extender, and promotes devices to that role while the count is below 16 (OpenThread, Router Selection). Border routers occupy those slots too, but four of them plus a dozen smart plugs is nowhere near the limit. The constraint you will meet is too few relays, never too many border routers.

How to check what you actually have

Border routers advertise themselves on the LAN. The Thread Group white paper notes they “should advertise a _meshcop._udp. record type” over mDNS, which any DNS-SD browser on the same segment can list. Each record is one border router, and the network name in each tells you whether they share a network. If your IoT VLAN blocks mDNS or your Wi-Fi gear filters multicast, the listing will be empty or partial, which is its own diagnosis; the UniFi VLAN segmentation guide on unifiguide.com covers what has to cross the boundary.

Home Assistant’s Thread page does the same job with a UI: it lists every border router it can see, groups them by network, and marks one as preferred. Two groups means two networks. Pick the network whose credentials you can read, then join the other border routers to it using each vendor’s sharing flow. If Home Assistant is the credential authority, the Zigbee vs Z-Wave vs Thread comparison on homeassistanthq.com covers whether to build on Thread at all.

The decision table

Situation	Border routers	Notes
Apartment, few devices, one ecosystem	1, or 2 if already owned	Accept a brief outage during updates, or join the second you probably have
House, one ecosystem	2 on one network	Place them apart, not on the same shelf
Large or multi-floor house	2, plus 1 per dead zone	Add mains-powered relays first
Two or more ecosystems	2 on one network, verified	Two networks with one each is worse than one network with one
Home Assistant with a self-hosted border router	1 self-hosted plus 1 or 2 ecosystem devices joined to it	The self-hosted one is where you can read network state

Placement, hub selection and the self-hosted route are in the border router choosing and placing guide. If devices already drop out, why Matter devices keep going offline walks the failure points; the split-network case is the second one on that list.

Related across the network

• Zigbee vs Z-Wave vs Thread: Which Mesh to Build — homeassistanthq.com
• Home Assistant Hardware: What to Run It On — homeassistanthq.com
• Home Assistant OS vs Container: Which Install Method to Pick — homeassistanthq.com
• How to Install ESPHome on ESP32: Add-on, Docker or pip, Then the First USB Flash — homeassistanthq.com
• Zigbee Devices Going Unavailable: How to Fix It — homeassistanthq.com