Every device on your network needs an IP address, and for most of the internet's history that meant an IPv4 address like 192.168.1.20. But the internet quietly passed a milestone in early 2026: for the first time, more than half of the traffic reaching Google's services arrived over IPv6. If your home internet is reasonably modern, you are almost certainly using IPv6 already - often without realizing it. This guide explains what IPv6 is, how it changes the way your devices get addresses, and whether you should leave it switched on.
What IPv6 actually is
IPv6 is the current version of the Internet Protocol, the addressing system that lets devices find one another on a network. The version most people grew up with, IPv4, uses 32-bit addresses, which allows for about 4.3 billion of them. That felt limitless in the 1980s, but the world handed out the last fresh IPv4 addresses years ago.
IPv6 uses 128-bit addresses instead. The result is an almost unimaginable pool - 340 undecillion addresses, or 340 followed by 36 zeros - which is enough to give every device its own unique, globally reachable address for the foreseeable future. An IPv6 address is written as eight groups of four hex digits separated by colons, such as 2001:0db8:85a3:0000:0000:8a2e:0370:7334. To keep them readable, leading zeros in a group can be dropped and one run of all-zero groups can be collapsed to a double colon, so that example is usually written 2001:db8:85a3::8a2e:370:7334.
Why IPv6 exists: address exhaustion and NAT
Because IPv4 addresses are scarce, home networks have always leaned on a workaround called Network Address Translation (NAT). Your ISP gives your router a single public IPv4 address, and the router shares that one address among all your devices by handing out private addresses (192.168.x.x) internally. NAT works, but it is a patch: it hides your devices behind one address and complicates anything that needs an incoming connection, which is the whole reason port forwarding exists.
As IPv4 ran dry, many providers - especially mobile carriers and newer ISPs - went a step further with carrier-grade NAT (CGNAT), sharing one public address among dozens or hundreds of customers at once. That quietly breaks self-hosting, peer-to-peer apps, and some online-gaming features. IPv6 removes the need for these workarounds entirely: there are enough addresses for every device to have its own, so NAT is no longer required to make a network function.
How your devices get an IPv6 address
With IPv4, a device asks your router's DHCP server for an address. IPv6 usually does this more automatically, in one of two ways:
- SLAAC (Stateless Address Autoconfiguration): your router broadcasts the network's prefix in a router advertisement, and each device builds its own address from that prefix. No central server hands out addresses, and this is the most common method at home.
- DHCPv6: a stateful server assigns addresses much as IPv4 DHCP does. It is more common on business networks. Worth knowing: Android devices do not support DHCPv6 and rely on SLAAC, which is one reason SLAAC dominates on home networks.
Your ISP typically hands your router a whole block of addresses - a prefix, often a /64 or a larger /56 - through a process called prefix delegation. Your router then gives each of your devices a genuine, internet-routable address from that block. In other words, every device can have its own public address rather than hiding behind a shared one.
Dual stack: IPv4 and IPv6 at the same time
You do not have to choose between the two protocols. Almost every home network runs dual stack, meaning each device holds both an IPv4 and an IPv6 address and uses whichever a given destination supports. Modern devices use a technique called Happy Eyeballs to try both and quietly settle on the one that responds fastest, so the handoff is invisible. This is exactly why enabling IPv6 rarely breaks anything - IPv4 keeps right on working for the sites and devices that still need it.
Do you already have IPv6?
You very likely do. Three quick ways to check:
- Visit a tester such as test-ipv6.com, which scores your connection out of 10 and shows your IPv6 address if you have one.
- Open your router's status page - see how to access your router settings - and look for an IPv6 or WAN IPv6 address line.
- On a computer, run ipconfig (Windows) or ip -6 addr (macOS and Linux) and look for a public address that begins with 2 or 3.
You may notice several IPv6 addresses on a single device, which is normal. A link-local address (beginning fe80) is used only on the local segment; a global address is your public one; and privacy features rotate temporary addresses for outbound connections so you cannot be tracked by one fixed address. Some networks also use unique local addresses (beginning fd), the IPv6 equivalent of the private 192.168 range for traffic that never leaves your home.
Should you enable it?
For the large majority of home users the answer is to leave it on, since it is usually enabled by default whenever your ISP supports it. The benefits are real:
- You are future-proof. IPv6 is now the majority protocol by Google's measure and the direction every network is heading.
- No CGNAT headaches. A genuine public address makes self-hosting, VPNs, game hosting, and peer-to-peer apps behave the way they should.
- It avoids extra translation layers. Traffic can take a more direct path instead of being squeezed through NAT or carrier-grade NAT.
The one thing to understand is less a downside than a change in mindset, and it is about security.
The security shift: firewalls, not NAT
On IPv4, NAT gave you an accidental side benefit: because your devices hid behind one shared address, the outside world could not reach them directly. With IPv6 every device has its own public address, so that incidental cover is gone. This alarms people, but it should not. Modern routers ship with an IPv6 firewall enabled by default that blocks unsolicited incoming connections, doing deliberately what NAT only did as a side effect. The protection now comes from a real stateful firewall rather than a quirk of address sharing, which is arguably the cleaner arrangement.
Two practical points follow. First, confirm your router's IPv6 firewall is switched on - it almost always is. Second, exposing a service to the internet over IPv6 means allowing it through that firewall rather than setting up a NAT port-forward. Treat all of this as one layer within a complete home network security plan.
How to enable or disable IPv6 on your router
The setting lives in your router's admin pages, usually under Internet, WAN, or a dedicated IPv6 section - again, see how to access your router settings. The exact wording is vendor-specific, but you will generally pick an IPv6 connection type:
- Native or Automatic (SLAAC/DHCPv6): the right choice for most people, because it simply accepts whatever your ISP provides. This is the option to select if you are turning IPv6 on.
- Prefix delegation size: some routers let you request a prefix such as /56 or /64; the default is almost always correct.
- DNS: IPv6 has its own DNS server addresses, so if you set custom DNS, add IPv6 resolvers too - see how to change your DNS server.
To turn it off, set the IPv6 connection type to Disabled in that same section. If only one machine is misbehaving, you can usually disable IPv6 on that single device in its network settings instead, which is a far better first step than switching it off for the whole household.
When IPv6 causes trouble (and what to do)
Problems are uncommon on modern equipment, but a few are worth recognizing:
- Broken or partial IPv6. If your router advertises IPv6 but the connection does not actually work, dual-stack devices can stall while they wait for it to time out. When only some sites load slowly, testing with IPv6 briefly disabled is a fast way to confirm whether it is the cause.
- MTU and tunnels. IPv6 has a minimum MTU of 1280 bytes and depends on ICMPv6 messages to discover the correct packet size, so a firewall that blocks all ICMPv6 can cause stalls. Native connections rarely have trouble; tunneled or 6rd setups are the usual culprits.
- Older devices and VPNs. A handful of aging IoT gadgets and legacy VPN clients assume IPv4 only. Moving such a device onto its own network, or disabling IPv6 just for it, is normally enough.
The bottom line
IPv6 is no longer the future - as of 2026 it carries around half of the internet's traffic, and your ISP has very likely switched it on for you already. For almost every home network the right move is simply to leave it enabled, confirm the router's IPv6 firewall is active, and enjoy a connection that is more direct and genuinely ready for what comes next. While you are in the router anyway, it is a good moment to revisit the best home network security plan and take a quick look at your DHCP settings.
