Multi-peer setup partially failing

[Qhilm]

I have one peer to my home router, one peer to cloudflare WARP (for internet traffic). Home router access over VPN works fine, WARP does not work. If I remove the peer for my home router, then WARP works. It feels like only the first peer works, but that can't be it.

Any idea what the issue could be? There is a slight overlap in allowed IPv6, but I expected the more specific route to always prevail. Or is that a wrong assumption? It's just that making a list of IPv6 subnets that do not include my home /56 will be quite long.

[Interface]
PrivateKey = <redacted>
Address = 172.16.0.2/32, 2606:4700:120:85b8:b194:f291:6120:7427/128
DNS = 94.140.14.14, 94.140.15.15, 2a10:50c0::ad1:ff, 2a10:50c0::ad2:ff

[Peer]
PublicKey = <redacted>
Endpoint = home.router.domain.com:55555
AllowedIPs = 10.46.0.0/16, 10.47.0.0/24, 2a02:8006:65:8400::/56
PersistentKeepalive = 25

[Peer]
PublicKey = <redacted>
Endpoint = engage.cloudflarewarp.com:2408
AllowedIPs = 2000::/3, 1.0.0.0/8, 2.0.0.0/7, 4.0.0.0/6, 8.0.0.0/7, 11.0.0.0/8, 12.0.0.0/6, 16.0.0.0/4, 32.0.0.0/3, 64.0.0.0/2, 128.0.0.0/3, 160.0.0.0/5, 168.0.0.0/8, 169.0.0.0/9, 169.128.0.0/10, 169.192.0.0/11, 169.224.0.0/12, 169.240.0.0/13, 169.248.0.0/14, 169.252.0.0/15, 169.255.0.0/16, 170.0.0.0/7, 172.0.0.0/12, 172.32.0.0/11, 172.64.0.0/10, 172.128.0.0/9, 173.0.0.0/8, 174.0.0.0/7, 176.0.0.0/4, 192.0.0.0/9, 192.128.0.0/11, 192.160.0.0/13, 192.169.0.0/16, 192.170.0.0/15, 192.172.0.0/14, 192.176.0.0/12, 192.192.0.0/10, 193.0.0.0/8, 194.0.0.0/7, 196.0.0.0/6, 200.0.0.0/5, 208.0.0.0/4, 224.0.0.0/3
PersistentKeepalive = 25

[keeshux]

I would do a traceroute to the WARP host to see what route is being picked, or try to invert the peer order.

[Qhilm]

Problem solved, it appears that there was a routing issue on the first peer and that caused some issue on the client, but I'm not sure, I couldn't 100% reproduce it.