Our production URL is https://karukidz.vercel.app/. On 3 Nov 2026 at about 11:30 Asia/Dhaka, Chrome on Windows showed ERR_CONNECTION_TIMED_OUT. The site then started working again without a deployment or code change. The owner reports similar roughly 10-minute failures on a mobile browser, including while using mobile data. I directly reproduced the IP-dependent failure on Windows and a Redmi Note 4 over the same Wi-Fi; the mobile-data report has not yet been independently traced.
Vercel’s ip-ranges.vercel.support diagnostic endpoint returned eight IPv4 ingress addresses for this hostname. I pinned the hostname and TLS SNI to each with curl --resolve from the affected Windows network:
64.29.17.3,216.198.79.3: HTTP 200 in under 0.2 s.64.29.17.67,216.198.79.67: HTTP 200 in under 0.3 s.64.29.17.131,216.198.79.131: TCP connect timeout, HTTP 000.64.29.17.195,216.198.79.195: HTTP 200 in under 0.5 s.
The Redmi on Wi-Fi returned HTTP 200 for both .67 addresses and TCP connect timeout for both .131 addresses. On Windows, ports 80 and 443 both connect to 64.29.17.67; neither connects to 64.29.17.131. Six ordinary requests while DNS returned a .195 address all succeeded. DNS answers rotate across these address pairs, matching the intermittent symptom. Changing recursive DNS alone is not a verified permanent fix: a public resolver also returned the inaccessible .131 pair.
Reproduction from an affected network:
curl -I --connect-timeout 3 --max-time 5 --resolve karukidz.vercel.app:443:64.29.17.67 https://karukidz.vercel.app/curl -I --connect-timeout 3 --max-time 5 --resolve karukidz.vercel.app:443:64.29.17.131 https://karukidz.vercel.app/The failing requests never reach HTTP, the deployment, or the backend. Vercel’s public status page currently says CDN and DNS are operational. Could Vercel’s network team check whether these two .131 ingress addresses have a routing, peering, or edge issue from Bangladesh, and advise how to restore reliable access while retaining this vercel.app URL? If this is upstream ISP routing, please identify path or ASN evidence that we can give the ISP. I can provide more diagnostics privately; public client IPs and account details are omitted here.