New wgcf/WARP registrations are IPv4-only while older profiles still support IPv6
Author: ghostCreated Jun 27, 2026Updated Jun 28, 2026
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.
Source: ViRb3/wgcf