Hi Vercel team,
I'm experiencing a network connectivity issue when accessing a Vercel-hosted application from Myanmar.
My custom domain is configured through Cloudflare DNS with the Vercel-provided CNAME target:
CNAME → 502c10584a1a36db.vercel-dns-017.com
The Vercel DNS target currently resolves to:
64.29.17.1 216.198.79.1 From Myanmar directly
The two IPs behave differently:
64.29.17.1:443 → TCP connection succeeds → Vercel responds normally
216.198.79.1:443 → TCP connection times out
For example:
curl.exe -4 --resolve :443:64.29.17.1 -I https:///
returns:
HTTP/1.1 200 OK Server: Vercel X-Vercel-Id: sin1::...
While:
curl.exe -4 --resolve :443:216.198.79.1 -I https:///
returns:
curl: (28) Failed to connect ... after ~20 seconds
I also confirmed this using Test-NetConnection:
216.198.79.1:443 TcpTestSucceeded : False
64.29.17.1:443 TcpTestSucceeded : True
Interestingly, 216.198.79.1 is reachable by ping and traceroute from Myanmar, but TCP/443 does not succeed.
VPN comparison
The most interesting part is that the exact same Vercel IP becomes reachable when using a VPN.
With the VPN enabled:
curl.exe -4 --resolve :443:216.198.79.1 -I https:///
returns:
HTTP/1.1 200 OK Server: Vercel X-Vercel-Id: sin1::...
So the behavior is:
Direct Myanmar VPN64.29.17.1:443 ✅ ✅ 216.198.79.1:443 ❌ ✅
I have reproduced the issue across multiple Myanmar Internet connections, including a mobile connection.
Question
Could the Vercel networking/infrastructure team confirm whether there is currently a routing, peering, or regional edge connectivity issue affecting traffic from Myanmar to 216.198.79.0/24?
I'm particularly interested in whether there is a Vercel-supported DNS or routing configuration that can avoid the affected edge path.
This is for a production application, so I'd like to understand whether there is a reliable solution rather than relying on VPN connectivity or the client receiving a particular Vercel edge IP.
Thanks!