In this Tech Insight, we look at why IPv6 is now 30 years old, what it was designed to solve, how it works in practice, and why it continues to matter to the modern internet despite never fully replacing IPv4.
What Is IPv6?
IPv6, or Internet Protocol version 6, is the system used to identify devices on the internet and route data between them. Every device connected to the public internet needs an IP address so information can be sent to the correct destination.
IPv6 is the successor to IPv4 and uses a much larger 128 bit address format, allowing vastly more unique addresses. This expansion was designed to ensure the internet could continue to grow as more people, devices, and services came online.
Why Was A New Internet Addressing System Needed?
The origins of IPv6 lie in a problem identified more than three decades ago. Internet Protocol version 4, introduced in the early 1980s, used 32 bit addresses, allowing for around 4.3 billion unique IP addresses. At a time when the internet was largely confined to universities, research institutions, and government networks, that seemed more than sufficient.
By the early 1990s, however, growth was accelerating much faster than expected. Commercial internet service providers were emerging, personal computers were becoming commonplace, and policymakers and engineers began to worry that the available supply of IPv4 addresses would eventually run out. Without addresses, new devices could not connect to the public internet, creating a real risk of slowing innovation and economic growth.
The responsibility for solving this problem fell to the Internet Engineering Task Force, the open standards organisation that develops the technical foundations of the internet. After several years of debate and experimentation, the IETF published RFC 1883 in December 1995, formally defining Internet Protocol version 6.
What Was Different About IPv6?
The most significant change introduced by IPv6 was the expansion of the address space. For example, IPv6 uses 128 bit addresses, increasing the number of possible addresses to approximately 340 undecillion (36 zeros!). In practical terms, this removed address scarcity as a constraint on future internet growth.
IPv6 also introduced a simplified packet header (the addressing and delivery instructions for data) to improve routing efficiency, removed some legacy features that had accumulated in IPv4, and standardised support for multicast traffic. Address assignment was redesigned through stateless address autoconfiguration, which allowed devices to generate their own addresses automatically when connecting to a network, without relying on manual configuration.
Security
Security considerations were part of the design from the outset. For example, support for IPsec was specified within IPv6, reflecting the growing importance of encryption and authentication on the public internet. Even so, IPv6 was deliberately conservative in that it was designed to change as little as possible beyond what was required to address scaling limits.
Not Backward Compatible
However, it’s worth noting here that IPv6 was not designed to be backward compatible with IPv4, i.e., IPv6 cannot directly communicate with IPv4, a decision that proved controversial because devices using one protocol could not directly communicate with devices using the other without translation mechanisms or running both protocols in parallel.
Why IPv6 Did Not Replace IPv4
At the time IPv6 was standardised, many assumed the internet would gradually migrate from IPv4 to IPv6. However, that transition never occurred in a clean or coordinated way.
Instead, network operators adopted Network Address Translation, known as NAT. NAT allows many devices to share a single public IPv4 address by using private address ranges internally. Homes, offices, and even entire mobile networks could connect large numbers of devices while consuming very few public IPv4 addresses.
This workaround fundamentally changed the incentives around IPv6 adoption. NAT was popular because it was relatively easy to deploy, worked with existing equipment, and avoided the need for large scale network redesign. Over time, IPv4 addresses became scarce but still usable, with regional internet registries overseeing address transfers between organisations.
As a result, IPv6 deployment slowed. Vendors had limited motivation to prioritise IPv6 support, and many organisations saw little short term benefit in migrating. Dual stack operation, where IPv4 and IPv6 run side by side, increased complexity and operational cost.
Where IPv6 Has Actually Been Successful
Judging IPv6 purely by whether it replaced IPv4 misses how the protocol is used today. In fact, IPv6 has carried much of the internet’s growth over the past decade, particularly in environments where scaling pressures are highest.
Mobile networks are a clear example. Many operators now deploy IPv6 as the default protocol for smartphones, using translation technologies only when IPv4 connectivity is required. This approach allows mobile providers to connect millions of devices without relying entirely on increasingly complex NAT systems.
Cloud infrastructure also shows a similar pattern. For example, large providers support IPv6 extensively within their internal networks and data centres. New virtual machines and services are often IPv6 capable by default, even if they still need to interoperate with IPv4 clients.
Data from Google, the Asia Pacific Network Information Centre, and Cloudflare shows that IPv6 adoption remains uneven worldwide, with global usage hovering in the mid 40 per cent range, some countries exceeding 50 per cent adoption, and others still relying heavily on IPv4.
What IPv6 Means for Modern Internet Architecture
Over the past 30 years, the internet has evolved in ways few engineers anticipated in the 1990s. For example, applications increasingly rely on domain names rather than fixed IP addresses, encryption is now the default for web traffic, and protocols such as QUIC reduce reliance on long lived client addressing by operating at higher layers.
These changes have led some to question whether IP addressing matters as much as it once did. In reality, scalable addressing still underpins everything. Data must still be routed efficiently across global networks, and infrastructure still needs predictable, manageable address allocation.
Simplifies Large Scale Network Design
In fact, IPv6 allows networks to be designed more simply at scale because large address blocks can be allocated hierarchically, which reduces routing complexity and makes networks easier to manage, particularly in data centres, content delivery networks, and emerging Internet of Things deployments where device counts can grow rapidly.
Ongoing Challenges
Despite its advantages, IPv6 is not without its drawbacks. For example, running IPv4 and IPv6 side by side increases operational overhead because security teams must monitor and protect two protocols at once, and misconfigured IPv6 can create unexpected exposure if administrators focus only on IPv4 controls.
Also, some older hardware and software either lacks IPv6 support or implements it poorly, which leads organisations in those environments to disable IPv6 entirely to avoid instability, even though doing so can create long term technical debt.
IPv6 migration also requires planning, testing, and staff training, and analysts at Gartner have repeatedly noted that many organisations struggle to justify IPv6 projects without external pressure such as address exhaustion, cloud pricing models, or regulatory expectations.
Why IPv6 Still Matters in 2026
As the global pool of unused IPv4 addresses has become effectively exhausted, supporting new services, devices, and networks increasingly depends on complex translation layers, which are harder to scale and manage over time, while IPv6 provides a way to support continued growth without compounding that complexity indefinitely.
IPv6 was designed as underlying infrastructure rather than a visible end user technology, with its value lying in the capacity and flexibility it provides to support internet expansion as higher level protocols, encryption, and application architectures continue to evolve.
Viewed in that context, IPv6 has not failed, but has quietly fulfilled its original purpose by allowing the internet to keep growing without breaking under the strain of address scarcity and architectural workarounds.
What Does This Mean For Your Business?
IPv6’s 30 year history shows that it was never meant to be a dramatic switchover moment, but a long term safety valve for internet growth, and that role is now clearer than ever. IPv4 continues to function through layers of workarounds, trading markets, and translation systems, while IPv6 quietly carries much of the internet’s newest traffic, particularly where scale and automation matter most. The result is an internet that runs on both protocols at once, not because that was the ideal outcome, but because it proved to be the most practical one.
For UK businesses, this creates a more immediate and pragmatic challenge than a theoretical one. For example, organisations planning cloud migrations, rolling out new digital services, or deploying large numbers of connected devices increasingly need to understand how IPv6 fits into their infrastructure, even if customers never notice it directly. Ignoring IPv6 entirely can introduce hidden risks, from security blind spots to unexpected compatibility issues with cloud platforms and mobile networks that already assume IPv6 support by default.
For network operators, regulators, vendors, and standards bodies, IPv6 remains a reminder that core internet technologies evolve slowly and unevenly, shaped as much by economics and operational reality as by technical design. Thirty years on, IPv6 has neither transformed the internet nor been left behind by it. Instead, it seems to have become part of the underlying fabric that allows the internet to keep expanding, quietly doing the job it was built to do while the debate about its future continues.
