Skip to content

RIPE ran out of IPv4 again

Networking by Richard7 7 replies 544 views
5 #1

Back in 2009, I got my first /22 from RIPE without any waitlist drama. They don't make them like that anymore. Just saw the announcement — RIPE's finally drained the last recoverable pool.

I remember when IPv6 was "two years away" in 2011. Then 2014. Then 2017. The timeline keeps slipping like a bad RAID rebuild.

Still running some of those original allocations on ancient Cisco gear. The hardware outlived the address space policy.

SPARCstation 20, still serving HTTP
#2

RFC 6177 (IPv6 Address Assignment to End Sites) said /48 minimum. Nobody listened. Now we have NAT444 and carrier-grade misery.

AS numbers are still available at least. My prefix at AS64512 is safe. Anyone without an ASN complaining about the waitlist — what did you expect? The writing was on the RFC wall since 2011.

Diagram of IPv4 exhaustion: https://www.ripe.net
[RIPE pool] ====X==== [empty]
|
[waitlist] ~~~~ [you are here]

#3

Gg no re

My boxes been v6 ready since 2019 yall noobs sleeping on this pwned yourselves

Yikes that waitlist tho

#4

Bro this is wild!!! Im position 8473 in the wiatlist and I signed up in JANUARY!!! Hostign my game server on a /32 nat behind nat behind nat now bro this is not sustainable!!!

Might just grab a v6 only from Hetzner and call it a day bro!!!

#5

Server hosting in 2026 be like.

  • ipv4? Never heard of her.
  • V6 or bust.
  • Gg ripe u played yourself.

My box on HostHatch still v4 only tho yikes!

#6

Waitlist position 12041. Ticket open. Waiting.

V6 tunnel from CloudCone. Goes down again. Ticket open. Waiting.

436 days. reboot is surrender.
#7

Ancient cisco still passing traffic in 2024?

#8

Same issue with v6 tunnels always dying on me

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft