[wp-meta] [Making WordPress.org] #3090: WordPress.org API not accessible over IPv6
Making WordPress.org
noreply at wordpress.org
Wed Nov 22 01:27:35 UTC 2023
#3090: WordPress.org API not accessible over IPv6
-------------------------+-------------------------
Reporter: deaky | Owner: (none)
Type: enhancement | Status: closed
Priority: high | Milestone:
Component: API | Resolution: maybelater
Keywords: |
-------------------------+-------------------------
Comment (by bviktor):
Some more comments on the performance "penalty":
> "There has been a growing trend of IPv6 usage on the internet. If we
look at the last month of connections made worldwide by Apple devices, we
see that IPv6 now accounts for 26% of all connections made," Mehta added.
"20% of the time, the connection could have used IPv6, but the server
didn't have it enabled.
> "And when IPv6 is in use, the median connection setup is 1.4 times
faster than IPv4. This is primarily due to reduced NAT usage and improved
routing."
And this report is from 3.5 years ago.
So yeah, you can keep resisting and make life more complicated **and**
slower both for yourselves and your users - I just don't see the point.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3090#comment:14>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list