Addressing 2020

By on 15 Jan 2021

Category: Tech matters

Tags: , , ,


Blog home

addressing 2020

Time for another annual roundup from the world of IP addresses. Let’s see what has changed in the past 12 months in addressing the Internet and look at how IP address allocation information can inform us of the changing nature of the network itself.

Around 1992, the IETF gazed into their crystal ball and tried to understand how the Internet was going to evolve and what demands that would place on the addressing system as part of the ‘IP Next Generation’ study.

The staggeringly large numbers of connected devices that we see today were certainly within the range predicted by that exercise. Doubtless, these device numbers will continue to grow. We continue to increase silicon production volumes and at the same time continue to refine the production process.

Back then, we also predicted that the only way we could make the Internet work across such a massive pool of connected devices was to deploy a new IP protocol that came with a massively larger address space — from that reasoning, IPv6 was designed. This world of abundant silicon was the issue that IPv6 was primarily intended to solve. The copious volumes of address space were intended to allow us to uniquely assign a public IPv6 address to every such device, no matter how small, or in whatever volume they might be deployed.

Rate of deployment

But while the Internet has grown at such amazing rates, the deployment of IPv6 continues at a more measured pace. There is still no common sense of urgency about the deployment of this protocol, and still there is no common agreement that the continued reliance on IPv4 is failing us.

Much of the reason for this apparent contradiction between the designed population of the IPv4 Internet and the actual device count, which is of course many times larger, is that the Internet is now a client/server network.

Clients can initiate network transactions with servers but are incapable of initiating transactions with other clients. Network Address Translators (NATs) are a natural fit to this client/server model, where pools of clients share a smaller pool of public addresses, and only required the use of an address while they have an active session with a remote server. NATs are the reason why in excess of 20 billion connected devices can be squeezed into some 2 billion active IPv4 addresses. Applications that cannot work behind NATs are no longer useful and no longer used.

However, the pressures of this inexorable growth in the number of deployed devices in the Internet means that the even NATs cannot absorb these growth pressures forever. NATs can extend the effective addressable space by up to 32 ‘extra’ bits, and they can enable the time-based sharing of addresses. Both of these are effective measures in stretching the address space to encompass a larger device pool, but they do not transform the address space into an infinitely elastic resource.

The inevitable outcome of this process is that either we will see the fragmenting of the IPv4 Internet into several disconnected parts, so that the entire concept of a globally unique and coherent address pool layered over a single coherent packet transmission realm will be foregone, or we will see these growth pressures motivate the further deployment of IPv6, and the emergence of IPv6-only elements of the Internet, as it tries to maintain a cohesive and connected whole.

There are commercial pressures pulling the network in both of these directions, so it’s entirely unclear what path the Internet will follow in the coming years, but my (admittedly cynical and perhaps jaded) personal opinion lies in a future of a highly fragmented network.

Can address allocation data help us to shed some light on what is happening in the larger Internet? Let’s look at what happened in 2020.

IPv4 in 2020

It appears that the process of exhausting the remaining pools of unallocated IPv4 addresses is proving to be similarly protracted as the process of the transition to IPv6, although by the end of 2020 the end of the old registry allocation model was in sight, with the depletion of the residual pools of unallocated addresses in each of the RIRs.

It is increasingly difficult to talk about ‘allocations’ in today’s Internet. There are still a set of transactions where addresses are drawn from the residual pools of RIR-managed available address space and allocated or assigned to network operators. At the same time, there are also a set of transactions where addresses are traded between networks in what is essentially a sale. These address transfers necessarily entail a change of registration details, so the registry records the outcome of a transfer, or sale, in a manner that is similar to an allocation or assignment.

If we want to look at the larger picture of the amount of IPv4 address space that is used or usable by Internet network operators, then perhaps the best metric to use is the total span of allocated and assigned addresses, and the consequent indication of annual change in the change in this total address span.

What is the difference between ‘allocated’ and ‘assigned’?

When a network operator or sub-registry has received an allocation, it can further delegate that IP address space to customers, along with using it for their own internal infrastructure. When a network operator has received an assignment, this can only be used for their own internal infrastructure.

Read: Using address space – FAQs

I personally find the distinction between these two terms somewhat of an artifice these days, so from here on I’ll use the term ‘allocation’ to describe both allocations and assignments.

The total IPv4 allocated address pool expanded by some 2.2 million addresses in 2020, on top of a base of 3.682 billion addresses that were already allocated at the start of the year. This represents a growth rate of 0.1% for the total allocated IPv4 public address pool. This is less that one tenth of the growth rate in 2010 (the last full year before the onset of the depletion of the unallocated IPv4 address pool).

Address Span (Billions)2.9853.2273.3953.4833.5373.5933.6243.6433.6573.6573.6823.684
Annual Change (Millions)189.4241.7168.088.453.955.930.619.413.20.624.92.2
Relative Growth7.9%8.1%5.2%2.6%1.5%1.6%0.9%0.5%0.4%0.0%0.7%0.1%

Table 1 — IPv4 allocated addresses by year

The record of annual change in allocations, per RIR, over the same period is shown in Table 2. There are some years when the per-RIR pool of allocated addresses shrunk is size. This was generally due to inter-RIR movement of addresses, due to administrative changes in some instances and inter-RIR address transfers in others.

RIPE NCC43.452.340.537.

Table 2 — IPv4 allocated addresses (millions). Distribution by RIR

Each of the RIRs are running through their final pools of IPv4 addresses. Some of the RIRs have undertaken address reclamation efforts during 2020, particularly in the area of re-designating previously ‘Reserved’ addresses as ‘Available’, notably in APNIC and LACNIC.

At the end of 2020, across the RIR system, there are some 6.2 million addresses in the available pool, mainly in APNIC (4 million) and AFRINIC (1.9 million). Some 12 million addresses are marked as reserved, with 5.5 million held by ARIN, some 2.8 million addresses held by AFRINIC and 2.5 million addresses held by APNIC. See Table 3.

RIPE NCC1,536 328,448 1,072,608 965,728
ARIN 4,096 4,352 6,137,600 5,509,888
LACNIC 50,688 1,416,448 266,240
AFRINIC 2,638,848 1,925,888 1,920,256 2,853,888
TOTAL 5,632,256 6,261,760 14,945,760 12,079,712

Table 3 — IPv4 available and reserved pools, December 2020

The RIR IPv4 address allocation volumes by year are shown in Figure 1.

Figure 1 — IPv4 address allocations by RIR by year
Figure 1 — IPv4 address allocations by RIR by year

The number of RIR IPv4 address allocations by year are shown in Figure 2.

Figure 2 — IPv4 allocations by RIR by year
Figure 2 — IPv4 allocations by RIR by year

It is clear from these two figures that the average size of an IPv4 address allocation has shrunk considerably in recent years, corresponding to the various unallocated IPv4 pool depletion policies in each of the RIRs.

IPv4 Address Transfers

In recent years, the RIRs have permitted the registration of IPv4 transfers between address holders, allowing secondary re-distribution of addresses, as an alternative to returning unused addresses to the registry. This has been in response to the issues raised by the unallocated IPv4 pool depletion — where the underlying motivation was to encourage the reuse of otherwise idle or inefficiently used address blocks — through the incentives provided by a market for addresses, and to ensure that such address movement is publicly recorded in the registry system.

The registered transfer numbers in the past six years are shown in Table 4. This includes both inter-RIR and intra-RIR transfers. Each transfer is treated as a single transaction. In the case of inter-RIR transfers, this is accounted in the receiving RIR’s totals.

Recieving RIR201220132014201520162017201820192020
APNIC 167 194 350 464 867 889 500 565 815
RIPE NCC 10 171 1,054 2,836 2,412 2,368 3,190 3,456 4,183
ARIN 4 22 28 27 76 99
Total 177 365 1,404 3,304 3,301 3,285 3,726 4,104 5,103

Table 4 — IPv4 address transfers per year

A slightly different view is that of the volume of addresses transferred per year, shown in Table 5.

Receiving RIR201220132014201520162017201820192020
APNIC 1.8 2.6 4.2 6.6 8.3 5.2 10.2 4.5 16.8
RIPE NCC 0.1 2.0 9.6 11.6 9.5 23.0 14.4 9.7 9.4
ARIN 0.1 0.3 0.2 0.3 0.2
Total 1.9 4.5 13.8 18.3 18.1 28.3 24.7 14.6 26.4

Table 5 — Volume of transferred IPv4 addresses per year (millions of addresses)

A plot of these numbers is shown in Figures 3 and 4.

Figure 3 — Number of transfers, 2012 - 2019
Figure 3 — Number of transfers, 2012 – 2019
Figure 4 — Volume of transferred addresses, 2012 - 2019
Figure 4 — Volume of transferred addresses, 2012 – 2019

The aggregate total of addresses in the transfer logs, since 2012, is some 150 million addresses, or the equivalent of 9 /8s, which is some 4% of the total delegated IPv4 address space of 3.7 billion addresses.

This data raises some questions about the nature of transfers.

The first question is whether address transfers have managed to be effective in dredging the pool of allocated, but unadvertised, public IPv4 addresses.

It was thought that by being able to monetize these addresses, holders of such addresses may have been motivated to convert their networks to use private addresses and resell their holding of public addresses. In other words, the opening of a market in addresses would provide incentive for otherwise unproductive address assets to be placed on the market. Providers who had a need for addresses would compete with other providers who had a similar need in bidding to purchase these addresses.

In conventional market theory, the most efficient user of addresses (here, ‘most efficient’ is based on the ability to use addresses to generate the greatest revenue) would be able to set the market price. Unused addresses would be put to productive use and, as long as demand outstrips supply, the most efficient use of addresses is promoted by the actions of the market. In theory.

However, the practical experience with transfers is not so clear.

The data relating to address recycling is inconclusive. Between 2011 and late 2017, the pool of unadvertised addresses sat between some 43 and 44 /8s. This pool of unadvertised addresses rose from the start of 2018 and by the end of 2020 there were just under 50 /8s that were unadvertised in the public Internet. Rather than reducing the pool of unused (unadvertised) addresses, this pool appears to be expanding in size over the past 36 months. See Figure 5.

Figure 5 — IPv4 Unadvertised address pool size
Figure 5 — IPv4 Unadvertised address pool size

In relative terms, expressed as a proportion of the total pool of allocated IP addresses, the unadvertised address pool dropped from 28% of the total allocated address pool in 2011 to a low of some 24% at the start of 2016, and subsequently rose to 29% by the end of 2020. This data points to the conclusion that address transfer activity has not made a substantial change in the overall picture of address utilization efficiency in the past 12 months. See Figure 6.

Figure 6 — Ratio of unadvertised pool to total pool
Figure 6 — Ratio of unadvertised pool to total pool

Perhaps there is a slightly broader conclusion that can be drawn from this data. We have probably not yet reached that point of true scarcity of IPv4 addresses where the degree of over-reach of need versus supply would cause us to look under every rock and reach deep within every cranny.

The market price for IPv4 addresses for sale is at best sluggish in terms of price movement and the pool of unadvertised IPv4 addresses is increasing in size. The total volume of transferred addresses has dropped by 50% over the 2017-2018 volumes for the past two years.

We have seen this industry react with a fervour close to hysteria when competitive pressures are bought to bear on a finite resource, as we’ve seen in various public auctions of spectrum space. The almost lackadaisical industry reaction to the unallocated IPv4 pool depletion issue tends to suggest that whatever else this protracted transition might be, it is not seen as a crisis in any way or shape.

There is a slightly different aspect to this question, concerning whether the transferred addresses are being traded as a speculative good.

One way to provide some insight into answering this question is to look at the age of transferred addresses. Are such addresses predominately recently allocated addresses, or are they longer-held addresses where the holder is wanting to realise the inherent value in otherwise unused assets? The basic question concerns the age distribution of transferred addresses where the age of an address reflects the period since it was first allocated or assigned by the RIR system.

The cumulative age distribution of transferred addresses by transaction is shown on a year-by-year basis in Figure 7. In 2012, some 70% of the transferred address blocks were originally assigned or allocated by an RIR within the previous 10 years. In 2020, some 50% of these transactions relate to addresses that were originally allocated by an RIR in the previous 10 years.

By volume, the overall majority of transferred addresses (some 50% of all transferred addresses) were drawn from legacy address holders, as shown in Figure 8.

The comparison of Figures 7 and 8 also leads to the observation that the transfers of older address blocks have far larger address spans, which corresponds to the very early IPv4 address allocations of /8 and /16 prefixes.

Figure 7 — Age distribution of transfer transactions
Figure 7 — Age distribution of transfer transactions
Figure 8 — Age distribution of transfer transactions
Figure 8 — Age distribution of transfer transactions

The second question is whether the transfer process is further fragmenting the address space by splitting up larger address blocks into successively smaller address blocks.

There are 24,769 transactions described in the RIRs’ transfer registries from the start of 2012 until the start of 2021. Of these, 17,184 entries list transferred address blocks that are the same size as the original allocated block. The remaining 7,585 entries are fragments of the originally allocated address blocks.

These 7,585 transfer entries that have fragmented the original allocation are drawn from 4,687 such original allocations. On average, the original allocation is split into 1.6 smaller address blocks. This data implies that address blocks are being fragmented because of address transfers, but in absolute terms this is not a major issue. There are 217,992 distinct address allocations from the RIRs to end entities as of the end of 2020, and the fragmentation reflected in 7,585 of these address blocks is around 3% of the total pool of allocated address prefixes.

The third question concerns the inter-economy flow of transferred addresses. Using the RIR-published transfer data for 2020, let’s look at the ten economies which:

  • Sourced the greatest volume of transferred addresses, irrespective of their destination (that is, including domestic transfers within the same economy), seen in Table 6
  • Had the ten largest recipients of transfers, Table 7
  • Had the ten largest economy-to-economy address transfers, Table 8
RankCCAddresses (M)Source Economy
3GB3.6United Kingdom of Great Britain and Northern Ireland
4RU3.2Russian Federation
5US2.7United States of America

Table 6 — Top 10 source economies providing transferred IPv4 addresses in 2020(millions of addresses)

RankCCAddresses (M)Destination Economy
2RU2.6Russian Federation
3US2.5United States of America
4GB2.1United Kingdom of Great Britain and Northern Ireland
9HK0.8Hong Kong Special Administrative Region of China

Table 7 — Top 10 economies receiving transferred IPv4 addresses in 2020

Notable in 2020 is the transfer of a large collection of addresses ( in August 2020 from APIDT (the Asia Pacific Internet Development Trust) to ‘ Singapore E-Commerce’. Several other address transfers in 2020 have been to Huawei International, also registered in Singapore. This use of Singapore as an economy of registration for large multinational enterprises with strong associations to Chinese entities probably lies behind the relatively small volume of address transfers into China and the large volume into Singapore in 2020.

RankFromToAddresses (M)Source Destination
3RURU2.4Russian FederationRussian Federation
4GBGB1.8United KingdomUnited Kingdom
6GBUS1.3United KingdomUnited States of America
14USDE0.4United States of AmericaGermany
16USUS0.3United States of AmericaUnited States of America
17USCN0.3United States of AmericaChina
18HKHK0.3Hong KongHong Kong

Table 8 – Top 20 economy-to-economy IPv4 address transfers in 2020

The 2020 transfer logs contain 3,132 domestic address transfers, with a total of 8,360,064 addresses, with the largest activity in domestic transfers in Russia, the United Kingdom and China. 1,971 transfers appear to result in a movement of addresses between economies, involving a total of 17,990,400 addresses.

It appears that the IPv4 address supply hiatus has motivated most Internet service providers to use address sharing technologies such as Carrier Grade NAT (CGN) on the access side, and name-based server pooling on the content side, as a means of increasing the level of sharing of addresses. This has been accompanied by a universal shift in the architecture of the Internet to a client/server model.

The result is that the pressure on the IPv4 address space has been relieved to a considerable extent, and the sense of urgency to migrate to an all-IPv6 network has been largely, but not completely, mitigated over this period.

The outstanding question about this transfer data is whether all address transfers that have occurred have been duly recorded in the registry system. This question is raised because registered transfers require conformance to various registry policies, and it may be the case that only a subset of transfers are being recorded in the registry as a result. This can be somewhat challenging to detect, particularly if such a transfer is expressed as a lease or other form of temporary arrangement, and if the parties agree to keep the details of the transfer confidential.

It might be possible to place an upper bound on the volume of address movements that have occurred in any period. One way to achieve this might be through a simple examination of the routing system, looking at addresses that were announced in 2020 by comparing the routing stable state at the start of the year with the table state at the end of the year. See Table 9.

Announcements814,253855,76741,514 697,928 24,299 92,026133,540
Root Prefixes:387,073399,81212,739 336,842 15,082 29,543 47,888
Address Span (/8s)169.73170.751.02160.202.016.778.53
More Specifics:427,180455,95528,775 361,086 9,217 62,483 85,652
Address Span (/8s)64.0265.691.6758.281.085.406.33

Table 9 — IPv4 BGP changes during 2020

While the routing table grew by 41,514 entries over the year, the nature of the change is slightly more involved.

92,026 prefixes announced at the start of the year were removed from the routing system throughout the year, and 133,540 prefixes were announced by the end of the year that were not announced at the start of the year. A further 24,299 prefixes had changed their originating Autonomous System number, indicating some form of change in the prefix’s network location, in some manner.

If we look at the entirety of all updates through 2020 then we see a larger collection of transient address prefixes. A total of 1,108,621 distinct prefixes were observed in the total of all BGP updates through 2020, or 294,368 additional prefixes from the initial set at the start of the year.

We can compare these prefixes that change in 2020 against the transfer logs for the two-year period of 2019 and 2020. Table 10 shows the comparison of these routing numbers against the set of transfers that were logged in these two years.

All 1,901   22,3987.8%
Root Prefixes 1,534   13,32610.3%
All 3,153   88,8733.4%
Root Prefixes 2,259   27,2847.6%
All 6,358 127,1824.8%
Root Prefixes 4,580   43,3089.6%

Table 10 — Routing changes across 2020 compared to the transfer log entries for 2019 – 2020

These figures show that 5%-10% of the changes in advertised addresses from the beginning to the end of the year are reflected as changes as recorded in the RIRs’ transfer logs.

This should not imply that the remaining changes in advertised prefixes reflect unrecorded address transfers.

There are many reasons for changes in the advertisement of an address prefix and a change in the administrative controller of the address is only one potential cause. However, it does establish some notional upper ceiling on the number of movements of addresses in 2020, some of which relate to transfer of operational control of an address block, that have not been captured in the transfer logs.

Finally, we can perform an age profile of the addresses that were added, removed, and re-homed during 2019, and compare it to the overall age profile of IPv4 addresses in the routing table. This is shown in Figure 9.

In terms of addresses that were added in 2019, they differ from the average profile due to a skew in favour of ‘recent’ addresses, and 20% of all announced addresses were allocated or assigned in the past 30 months. 20% of all added and removed addresses are more than 20 years old. Addresses that re-home appear to be disproportionately represented in the age bracket of between 5 to 10 years old.

Figure 9 — Change in the size of the BGP routing table across 2019
Figure 9 — Change in the size of the BGP routing table across 2019.

However, as IPv4 moves into its unallocated final stages, we are perhaps now able to take stock of the overall distribution of IPv4 addresses and look at where the addresses landed.

Table 11 shows the ten economies that have the largest pools of allocated IPv4 addresses. However, I must note the assignment of a country code is an address which registration reflects.

RankCCIPv4 Pool% TotalPer-CapitaEconomy
1US1,614,294,36843.8%4.88United States of America
2CN 344,408,5769.3%0.24China
3JP 189,992,4485.2%1.50Japan
4DE 123,787,3923.4%1.48Germany
5GB 114,504,8243.1%1.69United Kingdom
6KR 112,473,0883.1%2.19Korea
7BR 87,115,0082.4%0.41Brazil
8FR 82,368,5282.2%1.26France
9CA 69,753,8561.9%1.85Canada
10IT 54,950,9761.5%0.91Italy

Table 11 — IPv4 allocated address pools per national economy

If we divide this address pool by the current population of each national entity, then we can derive an address per capita index. The global total of 3.70 billion allocated addresses, with an estimated global population of 7.8 billion people, gives an overall value of 0.47 IPv4 addresses per capita.

RankCCIPv4 Pool% TotalPer-CapitaEconomy
1SC 8,118,7840.2%82.55Seychelles
2VA 10,7520.0%13.42Holy See
3GI 265,7280.0%7.89Gibraltar
4US1,614,294,36843.8%4.88United States of America
5SG 23,359,7440.6%3.99Singapore
6VG 102,9120.0%3.40British Virgin Islands
7SE 29,957,4800.8%2.97Sweden
8LI 112,6720.0%2.96Liechtenstein
9NL 50,392,6081.4%2.94Netherlands
10NO 15,670,0320.4%2.89Norway

Table 12 — IPv4 allocated address pools per capita

IPv6 in 2020

Obviously, the story of IPv4 address allocation is only half of the story, and to complete the picture it’s necessary to look at how IPv6 has fared over 2020.

IPv6 uses a somewhat different address allocation methodology than IPv4, and it is a matter of choice for a service provider as to how large an IPv6 address prefix is assigned to each customer.

The original recommendations published by the IAB and IESG in 2001, documented in RFC3177, envisaged the general use of a /48 prefix as an end site prefix.

Subsequent consideration of long-term address conservation saw a more flexible approach being taken with the choice of the end site prefix size being left to the service provider.

Today’s IPv6 environment has some providers using a /60 end site allocation unit, many using a /56, and many other providers using a /48. This variation makes a comparison of the count of allocated IPv6 addresses somewhat misleading. An ISP using /48s for end sites will require 256 times more address space to accommodate a similarly sized customer base as a provider who uses a /56 end site prefix, and 4,096 times more address space than an ISP using a /60 end site allocation!

For IPv6, let’s use both the number of discrete IPv6 allocations and the total amount of space that was allocated to see how IPv6 fared in 2019.

Comparing 2019 to 2020, the number of individual allocations of IPv6 address space has declined slightly, while the number of IPv4 allocations has halved.

IPv61,2792,461 3,5883,3024,020 4,537 4,736 5,5935,765 6,311 6,9225,455

Table 13 — Number of individual address allocations, 2009 – 2020

The amount of IPv6 address space distributed in 2019 is slightly less than the amount seen in 2018. As seen in Table 14.

IPv6 (/32s) 1,091 5,844 15,018 17,740 24,103 17,917 20,234 25,300 19,986 39,278 36,507 21,835
IPv4 (/32s)(M)190.1248.8201111.865.26464.437.951.950.642.523.3

Table 14 — Volume of address allocations, 2007 – 2018

Regionally, each of the RIRs saw IPv6 allocation activity in 2020 that was on a par with those seen in the previous year, except for the RIPE NCC, which saw a 50% decrease in allocations. See Table 15.

ARIN 394 638 1,039 611 560 512 604 646 684 659 605 644
APNIC 194 670 641 599 540 528 778 1,681 1,3691,474 1,484 1,498
RIPENCC 642 1,048 1,647 1,756 2,151 2,227 2,207 2,141 2,0512,620 3,104 1,403
LACNIC 35 50 132 253 696 1,208 1,061 1,009 1,5491,448 1,614 1,801
AFRINIC 14 55 129 83 73 62 86 116 112 110 115 109
1,279 2,461 3,588 3,302 4,020 4,537 4,736 5,593 5,765 6,311 6,922 5,455

Table 15 — IPv6 allocations by RIR

The address assignment data tells a slightly different story. Table 15 shows the number of allocated IPv6 /32’s per year. There were two /20 allocations in the year; one to CERNET in China and a second to Cable One in the United States. A second large allocation, a /21, was also made to CERNET in China in 2019.

Addresses (/32s)200920102011201220132014201520162017201820192020
ARIN 257 584 2,280 1,676 12,581 5,232 642 1,088 1,372 845 5,522 4,975
APNIC 175 3,241 9,506 3,807 4,462 2,663 2,109 1,236 4,228 19,690 7,945 7,365
RIPENCC 617 1,869 2,425 3,729 6,385 8,608 12,039 21,717 12,844 17,335 21,180 7,737
LACNIC 32 46 652 4,325 608 1,363 973 1,181 1,429 1,336 1,496 1,669
AFRINIC 9 104 155 4,203 67 51 4,471 78 113 72 364 89
1,091 5,844 15,018 17,740 24,103 17,917 20,234 25,300 19,986 39,278 36,507 21,835

Table 16 — IPv6 address allocation volumes by RIR

Dividing addresses by allocations gives the average IPv6 allocation size in each region, as seen in Table 16. ARIN average allocations increased in size due to some larger allocations in 2019. Overall, the average IPv6 allocation size remains around a /30.

Addresses (/32s)200920102011201220132014201520162017201820192020

Table 17 — Average IPv6 address allocation size by RIR

The number and volume of IPv6 allocations per RIR per year are shown in Figures 10 and 11.

Figure 10 — Number of IPv6 allocations per year
Figure 10 — Number of IPv6 allocations per year
Figure 11 — Volume of IPv6 allocations per year
Figure 11 — Volume of IPv6 allocations per year

It might be tempting to ascribe the decline of IPv6 allocations in 2020 from the RIPE NCC to the year where many European countries were hit hard by COVID-19 measures. Arguing against that is the observation that countries all over the world have been similarly affected, yet the decline in IPv6 allocation activity in 2020 is only seen in the data from the RIPE NCC.

READ: IPv6 in China

An interesting question to ask is why IPv6 address allocation activity has slumped in the European economies, but not in China, the US and Brazil? See Table 19.


Table 18 — IPv6 allocations by year by economy

Table 18 shows the countries who received the largest number of individual IPv6 allocations, while Table 19 shows the amount of IPv6 address space assigned on a per economy basis for the past 5 years (using units of /32s).

1UK 9,571China 2,245China 17,647China 6,787China 6,765
2Germany 1,525USA 1,497Russia 4,675USA 5,510USA 5,051
3Netherlands 1,312Germany 1,364Germany 1,932Russia 3,716Brazil 1,358
4USA 1,142Russia 1,358UK 1,209Germany 2,522Netherlands 1,331
5Russia 1,005Netherlands 1,296Singapore 1,055Netherlands 2,516Germany 716
6France 926Spain 1,170Netherlands 1,025UK 1,355Russia 715
7Brazil 727India 1,087Brazil 1,007France 1,182UK 552
8Spain 702UK 1,072USA 874Italy 1,052Italy 391
9Italy 679Brazil 1,049Spain 851Brazil 1,049France 390
10China 597France 714France 722Spain 854Turkey 290

Table 19 — IPv6 address allocation volumes by year by economy (/32s)

Historical allocation

Some twenty years ago it was common practice to point out the inequities in the state of IPv4 address deployment. Some US universities had more IPv4 addresses at their disposal than some highly populated developing economies, and the disparity was a part of the criticism of the address management practices of the time.

The RIR system was intended to address this issue of predisposition to a biased outcome. The concept behind the system was that within the regional community each community had the ability to develop their own address distribution policies and could determine for themselves what they meant by such terms as ‘fairness’ and ‘equity’ and then direct their regional address registry to implement these policies.

While IPv4 had a very evident early adopter reward in that the address allocations in the IPv4 class-based address plan could be quite extravagant, the idea for IPv6 was that address allocations were developed from the outset through local bottom-up policy determinate frameworks, so evident inequities in the outcome would be avoided.

It was also envisaged that with such a vast address plan provided by 128 bits of address space, the entire concept of scarcity and inequity would be largely irrelevant. 2128 is a huge number and the entire concept of comparison between two vast pools of addresses is somewhat irrelevant. So, when we look at the metric of /48s per head of population don’t forget that a /48 is actually 80 bits of address space, which is massively larger than the entire IPv4 address space. Even India’s average of 0.1 /48s per capita is still a truly massive number of IPv6 addresses!

However, before we go too far down this path, it is also useful to bear in mind that the 128 bits of address space in IPv6 has become largely a myth.

We sliced off 64 bits in the address span for no particularly good reason, as it turns out. We then sliced off a further 48 bits for, again, no particularly good reason.

READ: Testing transition mechanisms in IPv6-only networks

So, the vastness of the address space represented by 128 bits in IPv6 is not so vast and the usable address prefix space in IPv4 roughly equates to a /32 end address in IPv4, with around a /48 address in IPv6. So perhaps this comparison of /48s per capita is not entirely fanciful, and there is some substance to the observation that there are inequities in the address distribution in IPv6 so far. However, unlike IPv4, the unallocated IPv6 address space is still quite some time off, and we still believe that there are sufficient IPv6 addresses to support a uniform address utilization model across the entire world of silicon over time.

So, for IPv6 it’s still relatively early days and no doubt the picture will change as deployment of IPv6 matures.

RankCCAllocated (/48s)% Total/48s p.c.Advertised /48s% DeploymentName
1US 3,781,720,29918.1%11.4 995,561,50311.5%USA
2CN 3,583,049,82017.2%2.5 1,385,479,85316.0%China
3DE 1,444,151,9226.9%17.2 1,007,210,02111.7%Germany
4GB 1,341,718,7556.4%19.8 386,508,0834.5%UK
5FR 918,880,3874.4%14.1 142,697,4931.7%France
6RU 809,632,0463.9%5.5 213,602,5342.5%Russia
7JP 660,938,9403.2%5.2 506,102,0535.9%Japan
8IT 623,054,8723.0%10.3 394,403,9644.6%Italy
9AU 615,253,1582.9%24.1 305,355,5513.5%Australia
10NL 579,141,9302.8%33.8 249,749,1342.9%Netherlands
11BR 513,171,8552.5%2.4 297,615,0843.4%Brazil
12SE 426,377,5412.0%42.2 352,600,4544.1%Sweden
13ES 361,168,9251.7%7.7 89,469,5331.0%Spain
14PL 353,173,7191.7%9.3 196,706,9872.3%Poland
15AR 347,670,8841.7%7.7 280,830,3953.3%Argentina
16KR 344,719,3701.7%6.7 6,226,2040.1%Korea
17ZA 315,429,2861.5%5.3 286,032,5293.3%South Africa
18EG 269,090,8181.3%2.6 268,894,2093.1%Egypt
19CH 225,181,8651.1%26.0 105,767,8381.2%Switzerland
20TR 196,608,0230.9%2.3 37,666,5660.4%Turkey
21CZ 193,527,9170.9%18.1 105,042,5771.2%Czech Republic
22TW 167,444,4940.8%7.0 154,670,3841.8%Taiwan
23IR 164,495,3670.8%2.0 24,268,8800.3%Iran
24UA 150,208,6730.7%3.4 48,230,8380.6%Ukraine
25IN 147,063,4010.7%0.1 84,026,1621.0%India

Table 20 — IPv6 allocated address pools per national economy

To what extent are allocated IPv6 addresses visible as advertised prefixes in the Internet’s routing table?

Figure 12 shows the overall count of advertised, unadvertised, and total allocated address volume for IPv6 since 2010, while Figure 13 shows the advertised address span as a percentage of the total span of allocated and assigned IPv6 addresses.

Figure 12 — Allocated, unadvertised, and advertised IPv6 addresses
Figure 12 — Allocated, unadvertised, and advertised IPv6 addresses
Figure 13 — Advertised IPv6 addresses as a percentage of the allocated address pool
Figure 13 — Advertised IPv6 addresses as a percentage of the allocated address pool

The drop in the allocated address span in 2013 is the result of a change in LACNIC, where a single large allocation into Brazil was replaced by the recording of direct allocation and assignments to ISPs and similar end entities.

From a history of careful conservation of IPv4 addresses, where some 77% of allocated or assigned IPv4 addresses are advertised in the BGP routing table, a comparable IPv6 figure of 40% does not look all that impressive. But that’s not the point. We chose the 128-bit address size in IPv6 to allow addresses to be used without overriding concerns about conservation. We are allowed to be inefficient in address usage. At the start of 2021, we have advertised an IPv6 address span which is the equivalent of 130,000 /32s, or 9 billion end site /48 prefixes. That is just 0.003% of the total number of /48 prefixes in IPv6.

The Outlook for the Internet

Once more the set of uncertainties that surround the immediate future of the Internet are considerably greater than the set of predictions that we can be reasonably certain about.

The year 2017 saw a sharp rise in IPv6 deployment, influenced to a major extent by the deployment of IPv6 services in India, notably by the Jio service.

The next year, 2018, was a quieter year, although the rise in the second half of the year is due to the initial efforts of mass scale IPv6 deployment in the major Chinese service providers.

This movement accelerated in 2019, and the overall movement of some 5% in the network wide IPv6 deployment levels has a lot to do with the very rapid rise of the deployment of IPv6 in China.

Figure 14 — IPv6 deployment measurement, 2010 - 2020
Figure 14 — IPv6 deployment measurement, 2010 – 2020

While several service operators have reached the decision point that the anticipated future costs of NAT deployment are unsustainable for their service platform, there remains a considerable school of thought that NATs will cost-effectively absorb more years of Internet device population growth. At least, that’s the only rationale I can ascribe to a very large number of service providers who are making no visible moves to push out Dual-Stack services at this point in time. Given that the ultimate objective of this transition is not to turn on Dual-Stack everywhere, but to turn off IPv4, there is still some time to go. The uncertainty lies in trying to quantify what that time might be.

The period of the past decade has been dominated by the mass marketing of mobile internet services, and the Internet’s growth rates for 2014 through 2016 might have been the highest so far recorded. This would have been visible in the IP address deployment data, were it not for the depletion of the unallocated IPv4 address pool.

In address terms, this growth in the IPv4 Internet is being almost completely masked using Carrier Grade NATs in the mobile service provider environment, so that the resultant demands for public addresses in IPv4 are quite low and the real underlying growth rates in the network are occluded by these NATs.

In IPv6, the extremely large size of the address space masks out much of this volume. A single IPv6 /20 allocation to an ISP allows for 268 million /48 allocations or 68 billion /56 allocations, so much of the growth in IPv6-using networks is simply hidden behind the massive address plan that lies behind IPv6.

It has also been assumed that we should see IPv6 address demands for deployments of large-scale sensor networks and other forms of deployments that are encompassed under the broad umbrella of the Internet of Things.

This does not necessarily imply that the deployment is merely a product of an over-hyped industry, although that is always a possibility. It is more likely to assume that, so far, such deployments are taking place using private IPv4 addresses which rely on NATs and application-level gateways to interface to the public network.

Time and time again we are lectured that NATs are not a good security device. In practice, NATs offer a reasonable front-line defence against network scanning malware so there may be a larger story behind the use of NATs and device-based networks than just a simple conservative preference to continue to use an IPv4 protocol stack.

More generally, we are witnessing an industry that is no longer using technical innovation, openness, and diversification as its primary means of propulsion. The widespread use of NATs in IPv4 limit the technical substrate of the Internet to a very restricted model of simple client/server interactions using TCP and UDP. The use of NATs forces the interactions into client-initiated transactions. The model of an open network with considerable flexibility in the way in which communications take place is no longer being sustained in today’s network. Incumbents are entrenching their position while innovation and entrepreneurship are taking a back seat as we sit out this protracted IPv4/IPv6 transition.

Today’s Internet carriage service is provided by a smaller number of very large players, each of whom appears to be assuming a very strong position within their respective markets. The drivers for such larger players tend towards risk aversion, conservatism, and increased levels of control across their scope of operation. The same trends of market aggregation are now appearing in content provision, where a small number of content providers are exerting a completely dominant position across the entire Internet.

The evolving makeup of the Internet industry has quite profound implications in terms of network neutrality, separation of functions of carriage and service provision, investment profiles, expectations of risk and return on infrastructure investments, and on the openness of the Internet itself.

Given the economies of volume in this industry, it was always going to be challenging to sustain an efficient, fully open and competitive industry, but the degree of challenge in this agenda is multiplied many-fold when the underlying platform has run out of the basic currency of IP addresses.

The pressures on the larger players within these markets to leverage their incumbency into overarching control gains traction when the stream of new entrants with competitive offerings dries up, and the solutions in such scenarios typically involve some form of public sector intervention, directed to restore effective competition, and revive the impetus for more efficient and effective offerings in the market.

As the Internet continues to evolve, it is no longer the technically innovative challenger pitted against the venerable incumbent industries of telephony, print newspapers, television entertainment and social interaction — the Internet is now the established norm.

The days when the Internet was touted as a poster child of disruption in a deregulated space are long since over, and these days we appear to be increasingly looking further afield for a regulatory and governance framework that can challenge the increasing complacency of the newly established incumbents. It is unclear how successful we will be in this search. We can but wait and see.

Rate this article

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.


  1. Dovydas

    Why does historical data doesn’t match historical data in 2019 report? E.g. data in 2020 Table4 differs from 2019 Table4

  2. Geoff Huston

    Yes, is indeed a point of contention for me. These days the RIRs all publish a JSON transfer log. However the JSON reports differ from each other in subtle ways, but more critically the processes used to generate the JSON files from the registry data appear to differ for each RIR. In 2019 I used the transfer logs published as a simple html tables on the RIRs’ web pages. This year I used the JSON reports. Yes, the results are different. Obviously this should not be the case, however I have no insight as to how this has occurred and what the root cause may be.


Leave a Reply

Your email address will not be published. Required fields are marked *