A Thread border router bridges your Thread mesh to the rest of your home network using IPv6: neighbor discovery, router advertisements, and packet forwarding on the home-network side, according to Silicon Labs’ OpenThread documentation. If your router has IPv6 turned off, or your internet connection has never had it enabled, the border router has nothing to bridge to on that side, and Matter-over-Thread setup can fail even when the border router hardware itself is working correctly.
What “IPv6 disabled” actually breaks, and what keeps working anyway
This is worth being precise about, because it’s easy to assume the whole system fails at once. It doesn’t.
The Thread radio mesh itself (the low-power wireless layer that Thread devices use to talk to each other and to the border router) is IPv6-only at the protocol level, but that part operates independently of your home router’s own IPv6 setting. Thread devices can still form a mesh and talk to each other and to the border router without your router having IPv6 enabled at all.
What breaks is the bridge outward: getting from that Thread mesh onto your regular home network and the internet, so your phone app, a voice assistant, or a cloud automation can reach the device. That bridging step depends on IPv6 connectivity on the home-network side of the border router. The OpenThread documentation describes this as bidirectional IPv6 connectivity with neighbor discovery and router advertisements on the connected network. Without it, the border router can’t establish that bridge, and commissioning a new device or reaching an existing one from outside the mesh fails, even though the mesh itself may be fine.
Where to check whether your router even has IPv6
Many consumer routers, especially ones supplied directly by an ISP, either hide the IPv6 setting several menus deep, or don’t support IPv6 at all depending on the ISP’s own network. This is a genuinely common gap, not a rare misconfiguration.
What’s worth checking, in order:
- Your router’s admin panel, usually under a section labeled “WAN,” “Internet,” or “Advanced Network Settings”: look specifically for an IPv6 toggle or IPv6 connection type setting.
- Whether it’s enabled but set to a mode your ISP doesn’t actually support. Some routers show an IPv6 option that’s present in the interface but non-functional unless the ISP is also delivering IPv6 to your connection.
- Your ISP’s own documentation or support line, if the router shows no IPv6 setting at all. This is frequently an ISP-side limitation rather than something the router itself is blocking.
If you find IPv6 present but switched off, turning it on is the direct fix. If your router doesn’t expose the setting or your ISP doesn’t provide IPv6 at all, that’s a different situation, covered next.
The NAT64 fallback, and why it is not a guaranteed fix
Thread’s own documentation describes a fallback path for exactly this situation: NAT64, which translates between the Thread mesh’s IPv6 traffic and an IPv4-only home network, letting a border router bridge out even without native IPv6 support on the router side.
The caveat is that this depends on the specific border router’s own implementation of NAT64: it isn’t a feature of the Thread protocol that every border router automatically provides. Whether your particular border router (built into your HomePod, Echo, Nest Hub, or other hardware) supports this fallback varies by device and firmware version, and isn’t something this article can confirm for a specific product without testing it directly. If IPv6 genuinely isn’t available on your network, checking whether your specific border router’s documentation mentions IPv4 or NAT64 support is the next step, rather than assuming it will work automatically.
When this is an ISP problem, not a router setting
If you’ve confirmed your router genuinely has no IPv6 option, or the option is present but non-functional no matter how you configure it, the limitation is very likely upstream at the ISP, not something fixable in your router’s settings. Some ISPs simply have not rolled out IPv6 to every connection type or region.
In that case, your options are narrower: contact the ISP to ask whether IPv6 can be enabled on your account or connection type, check whether your specific border router supports the NAT64 fallback above, or accept that Matter-over-Thread setup may not work reliably on that connection until one of those changes.
This is a genuinely different failure from a device that’s simply out of range or poorly placed. For separating a network-layer cause like this one from a device, radio, or router-hardware cause more broadly, see the device, radio, router or cloud test. And if you’re still deciding how many border routers your home actually needs before troubleshooting further, how many Thread border routers you actually need covers that first.
For the wider pattern this fits into, a smart device that used to connect reliably and now doesn’t, see why a smart device that was working starts dropping off.
FAQ
Will enabling IPv6 on my router immediately fix Thread setup?
If IPv6 was the only thing missing, yes, generally. If your ISP doesn’t actually deliver IPv6 to your connection, simply toggling the router’s setting on won’t create IPv6 connectivity that isn’t there.
Can I use Thread entirely over IPv4 instead?
Not for the mesh itself, which is IPv6 by design. The NAT64 fallback bridges IPv6 mesh traffic onto an IPv4 network for connectivity outward, but it depends on your specific border router supporting that translation.
Why did Thread setup work fine on a different network, like a coffee shop or a friend’s house?
That network almost certainly has IPv6 enabled and working, which is exactly the variable this article is about. It’s a property of the network you’re on, not of the Thread device.
Does every home router support IPv6 in 2026?
No. Support varies by router model and, more significantly, by whether the ISP delivering the connection has enabled IPv6 on that account or region.
If my border router already worked before, could IPv6 have gotten disabled somehow?
Yes: a router firmware update, a factory reset, or a router replacement can all reset network settings including IPv6, which is worth checking if something that used to work suddenly doesn’t after any of those events.
Sources referenced in this article
- Silicon Labs, OpenThread: Border Router (Thread Fundamentals documentation).
https://docs.silabs.com/openthread/latest/thread-fundamentals/10-border-router(accessed 2026-08-06). Source of the bidirectional IPv6 connectivity requirement, the neighbor discovery/router advertisement mechanism, and the NAT64 IPv4-fallback description. - 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 NAT64 depends on the border router’s own IPv4 address pool and implementation.
Review interval: 12 months (router-firmware and ISP IPv6 rollout behavior).