That's a hurdle to moving clients from dual-stack to IPv6-only, but it's not a hurdle to moving clients from IPv4-only to dual-stack, which a lot of ISPs still haven't done yet.
I know the Azure Application Gateway is meant to be getting ipv6 support later this year, it is certainly the reason why my services are ipv4 currently.
I’d expect GitHub to have moved to Azure since the buyout.
The IPv6 adoption seems more tied to Azure/AWS/GCP support than anything else.
Comments
GitHub not being available via IPv6 is the biggest hurdle because so much depends on it.
That's a hurdle to moving clients from dual-stack to IPv6-only, but it's not a hurdle to moving clients from IPv4-only to dual-stack, which a lot of ISPs still haven't done yet.
I know the Azure Application Gateway is meant to be getting ipv6 support later this year, it is certainly the reason why my services are ipv4 currently.
I’d expect GitHub to have moved to Azure since the buyout.
The IPv6 adoption seems more tied to Azure/AWS/GCP support than anything else.