RIPE our of IPv4

Sat Nov 30 21:47:36 UTC 2019

User apps prefer IPv6, Netflix stops, users complain

On Sat, Nov 30, 2019 at 1:29 PM Mark Andrews <marka at isc.org> wrote:

> And how did that stop you deploying IPv6?  It’s not like you were turning
> off IPv4.
> --
> Mark Andrews
>
> On 1 Dec 2019, at 04:03, Matthew Kaufman <matthew at matthew.at> wrote:
>
> 
> This is a great example (but just one of many) of how server software
> development works:
>
> IANA IPv4 runout January 2011.
>
> Kubernetes initial release June 2014. Developed by Google engineers.
>
> ARIN IPv4 runout September 2015.
>
> Support for IPv6-only Kubernetes clusters alphas in 1.9, December 2017.
>
> Full support including CoreDNS support in 1.13, December 2018.
>
> Too bad nobody had warned them about IPv4 exhaustion before they started!
>
> On Mon, Nov 25, 2019 at 8:02 AM Andy Ringsmuth <andy at andyring.com> wrote:
>
>>
>>
>> > On Nov 25, 2019, at 8:56 AM, Dmitry Sherman <dmitry at interhost.net>
>> wrote:
>> >
>> > Just received a mail that RIPE is out of IPv4:
>> >
>> > Dear colleagues,
>> >
>> > Today, at 15:35 UTC+1 on 25 November 2019, we made our final /22 IPv4
>> allocation from the last remaining addresses in our available pool. We have
>> now run out of IPv4 addresses.
>>
>> Does this mean we are finally ripe for widespread IPv6 adoption?
>>
>> (Admit it, someone had to say it!)
>>
>> ----
>> Andy Ringsmuth
>> 5609 Harding Drive
>> <https://www.google.com/maps/search/5609+Harding+Drive+%0D%0ALincoln,+NE+68521?entry=gmail&source=g>
>> Lincoln, NE 68521
>> <https://www.google.com/maps/search/5609+Harding+Drive+%0D%0ALincoln,+NE+68521?entry=gmail&source=g>
>> -5831
>> (402) 304-0083
>> andy at andyring.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20191130/b939e7e9/attachment.html>