IPv6 and IoT: Why Running Out of Addresses Was a Real Crisis
In the 1970s, a small group of engineers designing the internet made a decision that seemed absurdly generous at the time. They gave the network 4.3 billion addresses.
Four billion. For a research project connecting a few dozen universities, that was infinity. Nobody in that room imagined a world where a single household would burn through forty of them — a phone, a laptop, a TV, a thermostat, a doorbell, a dozen bulbs, a watch, a speaker in every room.
That world arrived. And when it did, the internet quietly ran out of room. 🌐
The Short Version
IPv4's 32-bit address space gives 4.3 billion unique identifiers. The central pool ran out in February 2011. Regional registries fell one after another: Asia-Pacific in April 2011, Europe in September 2012, Latin America in 2014, North America in September 2015. No fresh addresses left.
The market responded the way markets do when something runs scarce: IPv4 addresses became an asset class. A single address that traded for ~$5 in 2011 now sells for $45–65. Companies buy, sell, and lease blocks of them like real estate.
NAT (Network Address Translation) kept the internet alive — your router hides dozens of private devices behind one public address. It works. It also breaks direct reachability, adds latency, and means your devices can reach out but can't easily be reached. For IoT, that last part is the problem.
IPv6 is the real fix. 128-bit addresses. 340 undecillion combinations. Enough to give every grain of sand on Earth its own address — and then do that for billions of Earths. Every device gets its own globally unique, publicly routable address. No sharing. No NAT. No hiding behind a router.
Why IoT Specifically Needed This
Four reasons the address crisis was existential for IoT and not just inconvenient:
- Scale — tens of billions of devices, growing. You cannot address them out of a 4.3-billion pool
- Direct reachability — a sensor with its own address doesn't need a cloud server as a middleman; local, peer-to-peer communication works natively
- No NAT overhead — removes a tax every device pays: latency, connection failures, port-forwarding workarounds
- Self-configuration — IPv6 devices configure their own addresses via SLAAC without a central server handing them out ⚙️
This is why Thread — the mesh underneath Matter — is IPv6-native. When every article in this series says "Thread gives every device an IP address," IPv6 is what that means under the hood.
The Catch: 6LoWPAN
IPv6 was designed for computers with memory and power to spare. A lot of IoT devices have neither.
The clash is concrete: an IPv6 header is 40 bytes. An 802.15.4 radio frame (used by Thread and Zigbee) leaves only ~80 bytes after security overhead. The header alone eats half your frame.
6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks) solves this with header compression so aggressive it can squeeze 40 bytes down to 2 bytes in the best case — a 95% reduction, achieved by not transmitting what both ends already know. It also handles fragmentation and mesh addressing.
This unglamorous adaptation layer is what makes IPv6 practical on a battery-powered sensor. It's the foundation Thread is built on, and it's why your motion sensor can hold a real, globally routable address while running for years on a coin cell.
Where the Transition Stands in 2026
The milestone finally landed this year. In March 2026, for the first time, more than half of all traffic reaching Google came over native IPv6 — 50.10% on 28 March, eighteen years after Google began measuring.
But the picture underneath is uneven. IPv4 still carries the majority of total internet traffic. Expert consensus expects dual-stack operation to continue until at least 2040. IoT is quietly one of the forces tipping the balance — every Thread and Matter deployment is IPv6 from the first packet.
💡 Final Thought
The engineers who chose 4.3 billion addresses weren't wrong — they were building for the world they could see. Their real gift was designing a system that could be replaced when the number ran out.
What's striking is how invisible the whole crisis was. The internet ran out of addresses, an asset market sprang up, a replacement protocol climbed to carry half of all traffic — and almost nobody noticed, because NAT and 6LoWPAN did their jobs in the dark.
Good infrastructure is like that. You only hear about it when it fails.
→ Full breakdown: the IPv4 exhaustion timeline, NAT's limits in depth, how 6LoWPAN compression works, the security wrinkle of direct addressability, and the complete builder's guide: Read the deep dive
Follow for more IoT connectivity deep dives — part of my ongoing 101-story series. 🔬
Comments
Post a Comment