Project: xmarketgames. Domains affected: xmarketgames.store and www.xmarketgames.store.

This is a network-level edge routing/anycast problem, not a DNS or config issue. DNS records at the registrar (Namecheap) match exactly what Vercel expects (A @ -> 216.198.79.1, CNAME www -> a-per-domain-hash.vercel-dns-017.com), both domains show "Valid Configuration" in the dashboard, and both SSL certificates are valid and auto-renewing.

The domain currently resolves via DNS to two IPs (216.198.79.1 and 64.29.17.1), but Vercel's edge network also appears to serve this domain on at least two additional anycast addresses that some clients get routed to: 216.198.79.65 and 64.29.17.65.

Of these four IPs, only 216.198.79.1 is actually reachable. The other three (64.29.17.1, 216.198.79.65, 64.29.17.65) fail at the raw TCP level -- the SYN is never acknowledged, no TLS or HTTP error, just no response.

This was verified with curl --resolve, pinning the domain to each IP individually and bypassing DNS entirely, from three independent networks (a home connection, a mobile carrier, and a separate cloud server). All three networks failed identically on the same three IPs and succeeded on the same one IP, which rules out DNS misconfig, SSL/cert issues, and anything client/browser-specific (plain curl reproduces it with no browser involved).

Could someone check whether Vercel's edge network is correctly announcing/routing the prefixes for 64.29.17.1, 216.198.79.65, and 64.29.17.65 for this domain/account? This is on the Hobby plan, so the in-dashboard support case flow routed me here since Hobby doesn't get dedicated CDN/Edge Network support.