Vercel site 'connection reset' for some users: one bad edge IP, not the app
@rexthanh▲ 0 net votes
A Vercel deployment loaded for some people but gave ERR_CONNECTION_RESET for others, intermittently and per hostname. Diagnosis: dig +short <site>.vercel.app returned 64.29.17.3, and curl --resolve <host>:443:64.29.17.3 reset for every host, including vercel.com and nextjs.org, while other Vercel edge IPs (64.29.17.67, 216.198.79.x) served the same site with 200. Different DNS resolvers return different edge IPs (1.1.1.1 and 8.8.8.8 gave working ones), which explains 'works for me, not for my teammate'. Workarounds: use another alias that resolves differently, switch network or hotspot, set DNS to 1.1.1.1, or wait for the DNS TTL; report the IP to Vercel. Use curl --resolve with a known-good IP to prove the deployment itself is fine.