Get ready for European IPv4 addresses

If you want ripe RIPE IPv4 addresses, there will be a literal waiting list to join.
In a new policy approved and posted on Tuesday, the regional internet registry (RIR) that serves Europe, the Middle East and Central Asia, dubbed RIPE, has decided that the only way it can deal with the ever-diminishing number of unassigned IPv4 addresses is for everyone to form an orderly queue.
“On application for IPv4 resources, LIRs will receive IPv4 addresses according to the following,” notes the new policy. And the first bulletpoint? “All allocation requests are placed on a first-come-first-served waiting list. No guarantees are given about the waiting time.”
The registry has also decided that it is not worth its while dishing out tiny numbers of public IP addresses, and will only make an allocation once it has a full /24 block, i.e. 256 consecutive addresses, to hand over.
The new policy: “All address blocks smaller than the allocation size will be held by the RIPE NCC and are declared unallocatable until the missing fragments are received/recovered by the RIPE NCC and they can be allocated as a contiguous allocation.”
And a /24 is all you’re going to get. From the policy: “The size of the allocation made will be exactly one /24. The sum of all allocations made to a single LIR by the RIPE NCC is limited to a maximum of 256 IPv4 addresses (a single /24). If this allocation limit has been reached or exceeded, an LIR cannot request an IPv4 allocation under this policy.”
In other words, you will have to queue for an indefinite period of time to get your hands on a block of 256 addresses.
The good news is that faced with the absolutely stark, irrefutable fact that there really are no new IPv4 addresses, all corporations in Europe have collectively decided to expend all necessary resources to move permanently to IPv6.
Ha! Who you kidding? It’s NATs-a-go-go, and record prices on the IPv4 black market. Remind us again why the IETF didn’t make IPv6 backwards compatible… ®
Updated to add
We’d like to stress that the waiting list policy was announced only this week, and so, has yet to be implemented. Stay tuned, though: it will kick in when RIPE deems it necessary, likely when it runs out of IPv4 addresses later this year or early 2020.
Also, yes, as some have pointed out, there is a black market for IPv4 addresses if you want to get your hands on some right now rather than get in line.
And for those of us in North America, yes, ARIN already has an IPv4 waiting list of sorts. That registry notes:The IPv4 Waiting List is one of several ways an organization may request IPv4 addresses from ARIN. Other available options are to transfer resources or request IPv4 addresses from pools reserved specifically for micro-allocations (NRPM 4.4) or Dedicated IPv4 block to facilitate IPv6 Deployment (NRPM 4.10).
Related Posts

Running-Code Primacy: Why IPv4 Leasing Should Be Judged by Operational Proof
IPv4 leasing often begins with a simple question: Can this provider give us the addresses? But for businesses that depend on IPv4 for hosting, VPN, SaaS, cloud, telecom, security, email delivery, or customer-facing platforms, that question is not enough. A better question is: Can this IPv4 structure prove that it works operationally? That is where Running-Code Primacy matters. Running-Code Primacy means that live operational reality should come before institutionalRead more Related Posts IPv4 Poverty Penalty: Why Small Networks Pay More IPv4 access can look equal on paper.The same registry forms.The same transfer rules.The same provider contracts.The same compliance language.The same Read more IPv4 Renewal Risk: When Weak Accountability Becomes Running-Code Betrayal Who is actually responsible for keeping this IPv4 access alive? Not who sold it.Not who introduced it.Not who issued the Read more Why self-holding can expose IPv4 assets to registry risk Self-holding IPv4 assets increases exposure to registry risk as compliance responsibility, transfer validation, and governance pressure are concentrated internally.Key points Self-holding Read more .related-post {} .related-post .post-list { text-align: left; } .related-post .post-list .item { margin: 5px; padding: 10px; } .related-post .headline { font-size: 18px !important; color: #999999 !important; } .related-post .post-list .item .post_thumb { max-height: 220px; margin: 10px 0px; padding: 0px; display: block; } .related-post .post-list .item .post_title { font-size: 16px; color: #3f3f3f; margin: 10px 0px; padding: 0px; display: block; text-decoration: none; } .related-post .post-list .item .post_excerpt { font-size: 13px; color: #3f3f3f; margin: 10px 0px; padding: 0px; display: block; text-decoration: none; } @media only screen and (min-width: 1024px) { .related-post .post-list .item { width: 30%; } } @media only screen and (min-width: 768px) and (max-width: 1023px) { .related-post .post-list .item { width: 90%; } } @media only screen and (min-width: 0px) and (max-width: 767px) { .related-post .post-list .item { width: 90%; } }

IPv4 Poverty Penalty: Why Small Networks Pay More
IPv4 access can look equal on paper. The same registry forms.The same transfer rules.The same provider contracts.The same compliance language.The same renewal process. But equal paperwork does not always create equal outcomes. For large operators, IPv4 friction may be manageable. They may have legal teams, policy staff, network engineers, compliance support, capital reserves, and enough customers to spread the cost of delay across a larger business. For smaller operators,Read more Related Posts Running-Code Primacy: Why IPv4 Leasing Should Be Judged by Operational Proof IPv4 leasing often begins with a simple question:Can this provider give us the addresses?But for businesses that depend on IPv4 Read more IPv4 Poverty Penalty: Why Small Networks Pay More IPv4 access can look equal on paper.The same registry forms.The same transfer rules.The same provider contracts.The same compliance language.The same Read more IPv4 Renewal Risk: When Weak Accountability Becomes Running-Code Betrayal Who is actually responsible for keeping this IPv4 access alive? Not who sold it.Not who introduced it.Not who issued the Read more .related-post {} .related-post .post-list { text-align: left; } .related-post .post-list .item { margin: 5px; padding: 10px; } .related-post .headline { font-size: 18px !important; color: #999999 !important; } .related-post .post-list .item .post_thumb { max-height: 220px; margin: 10px 0px; padding: 0px; display: block; } .related-post .post-list .item .post_title { font-size: 16px; color: #3f3f3f; margin: 10px 0px; padding: 0px; display: block; text-decoration: none; } .related-post .post-list .item .post_excerpt { font-size: 13px; color: #3f3f3f; margin: 10px 0px; padding: 0px; display: block; text-decoration: none; } @media only screen and (min-width: 1024px) { .related-post .post-list .item { width: 30%; } } @media only screen and (min-width: 768px) and (max-width: 1023px) { .related-post .post-list .item { width: 90%; } } @media only screen and (min-width: 0px) and (max-width: 767px) { .related-post .post-list .item { width: 90%; } }

IPv4 Renewal Risk: When Weak Accountability Becomes Running-Code Betrayal
Who is actually responsible for keeping this IPv4 access alive? Not who sold it.Not who introduced it.Not who issued the invoice.Not who sent the first LOA. Who owns the renewal risk when the relationship becomes stressed, the upstream source changes position, the documentation is questioned, or the provider chain no longer responds? For businesses that depend on IPv4 for hosting, SaaS, VPN, telecom, cloud, security, email delivery, or customerRead more Related Posts مخاطر تجديد بروتوكول IPv4: عندما تتحول المساءلة الضعيفة إلى خيانة في تنفيذ التعليمات البرمجية من المسؤول فعليًا عن إبقاء هذا الوصول إلى IPv4 قائمًا؟ ليس من باعه.وليس من قدّمه لك.وليس من أصدر الفاتورة.وليس من Read more Riesgo de renovación de IPv4: Cuando la falta de rendición de cuentas se convierte en traición al código en ejecución ¿Quién es realmente responsable de mantener vivo este acceso IPv4? No quién lo vendió.No quién lo presentó.No quién emitió la Read more Running-Code Primacy: Why IPv4 Leasing Should Be Judged by Operational Proof IPv4 leasing often begins with a simple question:Can this provider give us the addresses?But for businesses that depend on IPv4 Read more .related-post {} .related-post .post-list { text-align: left; } .related-post .post-list .item { margin: 5px; padding: 10px; } .related-post .headline { font-size: 18px !important; color: #999999 !important; } .related-post .post-list .item .post_thumb { max-height: 220px; margin: 10px 0px; padding: 0px; display: block; } .related-post .post-list .item .post_title { font-size: 16px; color: #3f3f3f; margin: 10px 0px; padding: 0px; display: block; text-decoration: none; } .related-post .post-list .item .post_excerpt { font-size: 13px; color: #3f3f3f; margin: 10px 0px; padding: 0px; display: block; text-decoration: none; } @media only screen and (min-width: 1024px) { .related-post .post-list .item { width: 30%; } } @media only screen and (min-width: 768px) and (max-width: 1023px) { .related-post .post-list .item { width: 90%; } } @media only screen and (min-width: 0px) and (max-width: 767px) { .related-post .post-list .item { width: 90%; } }