> Also, with most cloud hosting (AWS et. al.) it’s fairly trivial to enable dual stack support.

I say AWS IPv6 support is pretty atrocious. You still can not set up pure IPv6 VPC, even for internal use, afaik most AWS services are still accessible only through IPv4, IPv6 VPC has lots of weird limitations, etc etc. Somewhat sad, considering that one would think AWS would be one to benefit from v6

Agree, it's sad and strange that they can't provide that.

Still, hosting an IPv6 service on AWS is fairly simple (at least in my experience).

Google Compute Engine still does not support IPv6 for internal networking, only for external-facing load balancers, despite having made vague noises about it being "in progress" for the better part of a decade.

Are there any specific features of IPv6 you need for inner-cloud connectivity?

If you are spinning up enough resources to exhaust even a /16 of IPv6, you can probably use your monthly bill as leverage to force the issue.

Interestingly, you can clearly see the effect of the pandemic if you zoom into this year. The swing between access from IPv4-leaning business networks during the week to more IPv6-leaning home/mobile networks on the weekends has greatly reduced.

What percentage of that is from cellular networks?