New wgcf/WARP registrations are IPv4-only while older profiles still support IPv6

Just sharing an observation: newly registered wgcf/WARP profiles appear to be IPv4-only, while older profiles still work with both IPv4 and IPv6 on the same WireGuard client, network, and setup. I tested multiple keys and profiles, and it does not look like a local config or routing issue. It seems likely to be related to a Cloudflare-side provisioning or API change affecting new registrations.

[MashaDo]

ipv6 or not, i can attest that last night's multiple setups aren't working.. sometimes they all stop and come back - the ipv6 ones at least, so i left them "in-use" - still didn't come up..

[MashaDo]

also there's this little matter of wgcf trace returning 'warp=off' among other values.. i am not sure, can this be changed from my side somehow? i would like warp to be 'on' =)