7 ms·

And IPv6 penetration will have hit 20%.

by grabcocque 10y ago

sly010 10y ago
And will be the year of the Linux Desktop.
- Aloha 10y ago
  Wasn't that last year? ;-)
- ilogik 10y ago
  and, if we're lucky, Half Life 3?
deathanatos 10y ago
You jest, but global IPv6 penetration is at ~16%. It rose ~6% last year, so if linear growth is presumed (and it's actually been growing closer to exponentially, as would be expected) we should hit 20% late this year. I'm hopeful that we'll see some decent pickup of it since AWS finally started offering it. This is global adoption; some countries, including the United States, have already hit 20%. [1]: https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- 1maginary 10y ago
  >The graph shows the percentage of users that access Google over IPv6. I'm finding it really hard to believe, as someone in Guatemala, that 6% of requests to Google here are made over IPv6. Is there any way to gain more insight? e.g. what ISPs are responsible?
  - runeks 10y ago
    Mobile carriers. In the US, 55% of mobile traffic is IPv6: http://m.slashdot.org/story/315213 http://m.slashdot.org/story/315213
  - p1mrx 10y ago
    That level of detail isn't published, but most of Guatemala's IPv6 traffic is coming from http://bgp.he.net/AS52362 http://bgp.he.net/AS52362 and http://bgp.he.net/AS23243 http://bgp.he.net/AS23243 Edit: APNIC has similar data published here: https://stats.labs.apnic.net/ipv6/GT https://stats.labs.apnic.net/ipv6/GT
    - 1maginary 10y ago
      I appreciate the links! Exactly what I was after.
- marcosdumay 10y ago
  What's up with that huge weekly variation?
  - OJFord 10y ago
    I'm guessing, but could it be offices running IPv6 while employees go home to IPv4? (With non-square edges due to mornings and evenings.)
  - mastax 10y ago
    It looks like it's correlated with the weekend. I guess workplace computers are more likely to use IPv4? It makes sense on the surface. Workplaces have little to no incentive to use IPv6 since they either have a huge block of IPv4 space or run NAT or both. Also they tend to rely more on enterprise network appliances which have bad IPv6 support in my experience. IPv6 is more of a boon to consumer applications since carrier-grade NAT is a nuisance and otherwise you need an IP per customer.
    - marcosdumay 10y ago
      Makes sense.
    - deathanatos 10y ago
      Every employer except one that I've worked for had IPv4 only. None of them had public IP blocks; they were all NAT'd. > Also they tend to rely more on enterprise network appliances which have bad IPv6 support in my experience. This I would believe. > IPv6 is more of a boon to consumer applications since carrier-grade NAT is a nuisance and otherwise you need an IP per customer. It would have been a slight boon at work, too. HR perennially makes me grab documents/data off my home machine, and I cannot wait for the day when I can just `ssh` to a domain name. My .ssh/config aliases are getting pretty good, but it still adds considerable latency to pipe everything through a gateway. (Alternatively, I could run SSH on non-standard ports, but I've yet to get to mucking around with the port-forwarding settings for that.) There were also times when we needed to do stuff like employee laptop-to-laptop communications, and the network just wouldn't deal with it. I was never sure if this was NAT, or just that Corp Net liked to drop packets. (It seemed rigged to drop basically anything that didn't smell like a TCP connection to an external host. ICMP wasn't fully functional, which of course makes engineering more fun when you're having your personal desktop at home do pings or traceroutes for you, but that doesn't help if the problem is on your route.)
- elastic_church 10y ago
  thats motivational
deleted 10y ago
[deleted]
gnopgnip 10y ago
It is already over 50% in the US.
- pbhjpbhj 10y ago
  The stat for Google in the citation (https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption&tab=per-country-ipv6-adoption https://www.google.com/intl/en/ipv6/statistics.html#tab=per-...) shows 30%; where do you get the 50% adoption from?
- sobani 10y ago
  thanks to runeks [https://news.ycombinator.com/item?id=13925396 https://news.ycombinator.com/item?id=13925396] according to https://mobile.slashdot.org/story/16/08/20/2059216/ipv6-achieves-50-reach-on-major-us-carriers https://mobile.slashdot.org/story/16/08/20/2059216/ipv6-achi... it's only the US mobile carriers that are over 50%.

And IPv6 penetration will have hit 20%.

sly010 10y ago

And will be the year of the Linux Desktop.

Aloha 10y ago
Wasn't that last year? ;-)
ilogik 10y ago
and, if we're lucky, Half Life 3?

deathanatos 10y ago

You jest, but global IPv6 penetration is at ~16%. It rose ~6% last year, so if linear growth is presumed (and it's actually been growing closer to exponentially, as would be expected) we should hit 20% late this year. I'm hopeful that we'll see some decent pickup of it since AWS finally started offering it. This is global adoption; some countries, including the United States, have already hit 20%. [1]: https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html

1maginary 10y ago
>The graph shows the percentage of users that access Google over IPv6. I'm finding it really hard to believe, as someone in Guatemala, that 6% of requests to Google here are made over IPv6. Is there any way to gain more insight? e.g. what ISPs are responsible?
- runeks 10y ago
  Mobile carriers. In the US, 55% of mobile traffic is IPv6: http://m.slashdot.org/story/315213 http://m.slashdot.org/story/315213
- p1mrx 10y ago
  That level of detail isn't published, but most of Guatemala's IPv6 traffic is coming from http://bgp.he.net/AS52362 http://bgp.he.net/AS52362 and http://bgp.he.net/AS23243 http://bgp.he.net/AS23243 Edit: APNIC has similar data published here: https://stats.labs.apnic.net/ipv6/GT https://stats.labs.apnic.net/ipv6/GT
  - 1maginary 10y ago
    I appreciate the links! Exactly what I was after.
marcosdumay 10y ago
What's up with that huge weekly variation?
- OJFord 10y ago
  I'm guessing, but could it be offices running IPv6 while employees go home to IPv4? (With non-square edges due to mornings and evenings.)
- mastax 10y ago
  It looks like it's correlated with the weekend. I guess workplace computers are more likely to use IPv4? It makes sense on the surface. Workplaces have little to no incentive to use IPv6 since they either have a huge block of IPv4 space or run NAT or both. Also they tend to rely more on enterprise network appliances which have bad IPv6 support in my experience. IPv6 is more of a boon to consumer applications since carrier-grade NAT is a nuisance and otherwise you need an IP per customer.
  - marcosdumay 10y ago
    Makes sense.
  - deathanatos 10y ago
    Every employer except one that I've worked for had IPv4 only. None of them had public IP blocks; they were all NAT'd. > Also they tend to rely more on enterprise network appliances which have bad IPv6 support in my experience. This I would believe. > IPv6 is more of a boon to consumer applications since carrier-grade NAT is a nuisance and otherwise you need an IP per customer. It would have been a slight boon at work, too. HR perennially makes me grab documents/data off my home machine, and I cannot wait for the day when I can just `ssh` to a domain name. My .ssh/config aliases are getting pretty good, but it still adds considerable latency to pipe everything through a gateway. (Alternatively, I could run SSH on non-standard ports, but I've yet to get to mucking around with the port-forwarding settings for that.) There were also times when we needed to do stuff like employee laptop-to-laptop communications, and the network just wouldn't deal with it. I was never sure if this was NAT, or just that Corp Net liked to drop packets. (It seemed rigged to drop basically anything that didn't smell like a TCP connection to an external host. ICMP wasn't fully functional, which of course makes engineering more fun when you're having your personal desktop at home do pings or traceroutes for you, but that doesn't help if the problem is on your route.)
elastic_church 10y ago
thats motivational

deleted 10y ago

[deleted]

gnopgnip 10y ago

It is already over 50% in the US.

pbhjpbhj 10y ago
The stat for Google in the citation (https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption&tab=per-country-ipv6-adoption https://www.google.com/intl/en/ipv6/statistics.html#tab=per-...) shows 30%; where do you get the 50% adoption from?
sobani 10y ago
thanks to runeks [https://news.ycombinator.com/item?id=13925396 https://news.ycombinator.com/item?id=13925396] according to https://mobile.slashdot.org/story/16/08/20/2059216/ipv6-achieves-50-reach-on-major-us-carriers https://mobile.slashdot.org/story/16/08/20/2059216/ipv6-achi... it's only the US mobile carriers that are over 50%.