[wp-meta] [Making WordPress.org] #3090: WordPress.org API not accessible over IPv6
Making WordPress.org
noreply at wordpress.org
Mon Aug 14 13:26:10 UTC 2023
#3090: WordPress.org API not accessible over IPv6
-------------------------+-----------------------
Reporter: deaky | Owner: (none)
Type: enhancement | Status: reopened
Priority: high | Milestone:
Component: API | Resolution:
Keywords: |
-------------------------+-----------------------
Changes (by johnjonestaggle):
* priority: normal => high
* status: closed => reopened
* resolution: maybelater =>
Comment:
since the hosting provider has for some time provided IPv6 transit +
the load balancing and DDOS implications are null(if they are not present
do tell which vendor)
this is 2023 most mobile providers are IPv6 native and there is at least
15% degradation not using IPv6
since this is happening across the industry
https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-
public-ip-insights/
since singlehop and internap are both ipv6 enabled I dont see any
reason...
who is going to stand up and do the hard work ?
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3090#comment:11>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list