[wp-meta] [Making WordPress.org] #3090: WordPress.org API not accessible over IPv6

Making WordPress.org noreply at wordpress.org
Fri Nov 20 00:37:18 UTC 2020

#3090: WordPress.org API not accessible over IPv6
 Reporter:  deaky        |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:  maybelater
 Keywords:               |

Comment (by dd32):

 Replying to [comment:5 deaky]:
 > Is there any news here?

 No, the network infrastructure we're running still doesn't have any IPv6
 addresses allocated, it's not as simple as requesting/assigning them as we
 have complex load balancing and DDOS implications to take into
 consideration. It's not as high priority right now due to the majority of
 connections having either dual-stack or NAT gateways for the other half of
 the internet that has no native IPv6 routes.

 I'm curious what environments you're running WordPress under that only
 have IPv6 connectivity though, as most instances of IPv6-only servers I've
 come across still have outbound IPv4 connectivity via a NAT interface.

 The other option is to use
 WordPress's built in proxy support], which would replace having to handle
 a NAT64 instance with a potentially simpler non-caching proxy.

 I'm going to continue to leave this ticket closed, as there's no action
 the meta team can do here ourselves, this is up to the systems team to
 enable when they feel comfortable doing so. I do know it's on a long term
 roadmap though.

Ticket URL: <https://meta.trac.wordpress.org/ticket/3090#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list