One Thread border router is technically enough to connect your Thread mesh to the internet. If you already own an Apple HomePod, an Amazon Echo Hub, a second-generation Nest Hub, or a SmartThings Station, one of those devices is very likely already acting as a border router without you having bought anything extra for the job.
What actually breaks when your only border router goes offline
This is the question that matters more than the raw count, and it’s the part most pages leave vague. If your single border router loses power or drops offline, your Thread devices do not all stop working. The Thread mesh keeps operating locally: Thread devices that talk directly to each other, like a sensor triggering a nearby Thread-connected switch through a local automation, can keep functioning.
What stops is anything that needs to reach outside the mesh: your phone app checking a device’s status remotely, a cloud-based automation, or a voice assistant command that has to route through the internet. That traffic has nowhere to go until another border router takes over the job, according to Homey’s own documentation on border router redundancy. If you have exactly one, that gap lasts until it comes back online.
This distinction (local mesh keeps running, external reach stops) is the actual argument for a second border router, not a vague sense that “more is safer.”
Devices that are secretly already a border router
Before deciding you need to buy anything, it’s worth checking what you already own. Several mainstream smart home devices ship with Thread border router capability built in and enabled by default, without being marketed primarily as one:
- Apple HomePod (2nd generation) and HomePod mini
- Apple TV 4K (2021 or later)
- Amazon Echo (4th generation and later) and Echo Hub
- Google Nest Hub (2nd generation) and Nest Hub Max
- Samsung SmartThings Station and select SmartThings-enabled hubs
If you own two or more of these, you may already have redundancy without realizing it. Whether they’re actually cooperating on the same Thread network is a separate question, covered in why your Thread network may have silently split into two.
Thread 1.4 credential sharing: what it promises and what it does not yet guarantee
Thread 1.4, finalized in 2024, introduced a credential-sharing mechanism specifically aimed at this problem: border routers on the same network discover each other, negotiate which one holds the authoritative network credentials, and synchronize so that all of them operate on the same Thread network rather than each running its own separate one.
That is the promise. The caveat, as of 2026, is that this negotiation depends on each platform’s own implementation of the 1.4 specification. Whether your Apple, Google, SmartThings, Eero, or Home Assistant border routers actually merge into a single shared Thread network is not guaranteed just because all the hardware supports Thread 1.4; it depends on whether that specific combination of platforms has implemented the credential-sharing side of the spec and whether it’s active on your firmware version. This is genuinely still settling across the industry, not a setting you’re missing.
When a second one is worth adding
Given the above, the practical guidance is straightforward:
One border router is enough if:
- You mostly interact with Thread devices locally (through a hub app on the same network) rather than remotely
- A brief gap in remote access or voice-assistant control during a router restart isn’t disruptive
- You’re just getting started with your first Matter-over-Thread device
A second is worth having if:
- You depend on remote access: checking a lock or sensor status while away from home
- You’re running automations that route through the cloud rather than executing locally
- Your existing border router is a device you regularly restart, unplug, or move (a streaming box you power-cycle often, for instance)
If you already own two qualifying devices from the list above, the question becomes whether they’re sharing credentials rather than whether you need to buy a third. See the linked article on split networks for how to check that.
For the broader question of separating a Thread-specific problem from a router, radio, or device-level one, start with the device, radio, router or cloud test, and for a device that used to stay connected and now doesn’t, see why a smart device that was working starts dropping off.
FAQ
Do I need to buy a dedicated Thread border router device?
Usually not. Most households already own at least one qualifying device from a major ecosystem. A dedicated border router is only worth buying if you own none of the common ones and want Thread support specifically.
Does having more than one border router cause conflicts?
Not by design: the protocol supports multiple active border routers on one network specifically for redundancy. Conflicts tend to come from the credential-sharing gap above, where devices end up on separate networks rather than one shared one, not from having “too many.”
Can two different ecosystems’ border routers work together?
That depends on whether both have implemented Thread 1.4 credential sharing and whether it’s active between that specific pair. Some combinations merge cleanly; others currently do not, as of 2026.
Is a Thread border router the same thing as a Matter hub?
No, though the same physical device is often both. A border router bridges the Thread radio mesh to your IP network. A Matter hub or controller is the software layer that lets an app or ecosystem control the device. A single piece of hardware commonly does both jobs.
Will my Thread devices stop working entirely if I unplug my only border router?
No. Local, direct Thread-to-Thread interaction can continue. What stops is anything requiring a path out to the internet or a remote app.
Sources referenced in this article
- Homey, What is a Thread Border Router & Why Do You Need One?
https://homey.app/en-us/wiki/what-is-a-thread-border-router/(accessed 2026-08-06). Source of the “one is technically enough” baseline and the specific local-mesh-continues-but-external-reach-stops failure behavior. - Thread Group, Thread Border Router Best Practices.
https://www.threadgroup.org/Portals/0/documents/support/ThreadBorderRouterBestPractices_2530_1.pdf(accessed 2026-08-06). Source confirming Thread networks support multiple active border routers for redundancy by design.
Review interval: 6 months (Thread and Matter platform behavior changes quickly).