3 ms·
I'm a little concerned about that site: For its test connecting to Google, besides using port 80 (instead of 443), it reports "500 Can't connect to google.com:
by CaliforniaKarl 4y ago
I'm a little concerned about that site: For its test connecting to Google, besides using port 80 (instead of 443), it reports "500 Can't connect to google.com:80 (No route to host)". I just tested to Google IPv6 ports 80, and it works fine for me.
Regardless, Google's chart of IPv6 adoption (https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6...) continues to trend towards IPv6 adoption. I expect that if you looked at a chart of web site IPv6 adoption, it would also be trending upwards (though not at as steep a rate).
If that's true, then it stops being a chicken-and-egg problem, and turns in to a game of chicken: Who starts supporting IPv6 first, you or your competitors?