My custom domain aymwvn.me is configured on Vercel and shows:
Valid Configuration
Production
SSL valid
The .vercel.app deployment also works.
I am having a connectivity problem specifically with the Vercel Anycast IPs returned by DNS.
Current DNS:
aymwvn.me → 216.198.79.65
aymwvn.me → 216.198.79.1
Both IPs time out on TCP/443.
I ran Vercel’s official connectivity debug script, which tested all IPs associated with my domain.
Results:
216.198.79.1 → TCP timeout / 100% packet loss
216.198.79.65 → TCP timeout / 100% packet loss
216.198.79.129 → HTTP 200 OK / ping works
216.198.79.193 → HTTP 200 OK / ping works
64.29.17.1 → TCP timeout / 100% packet loss
64.29.17.65 → TCP timeout / 100% packet loss
64.29.17.129 → HTTP 200 OK / ping works
64.29.17.193 → HTTP 200 OK / ping works
The successful responses contain:
Server: Vercel
HTTP/1.1 200 OK
Host: aymwvn.me
I also confirmed the DNS response using Google’s public resolver:
nslookup aymwvn.me 8.8.8.8
216.198.79.65
216.198.79.1
The issue occurs on both my home Internet connection and a separate mobile-data connection.
Therefore:
- The Vercel deployment works.
- The custom domain is configured as Valid Configuration.
- SSL works.
- DNS resolves successfully.
- Four Vercel Anycast IPs work.
- Four other Vercel Anycast IPs consistently timeout.
- The IPs returned by normal DNS are currently the unreachable ones.
This appears to be an issue with the Vercel Anycast edge IP assignment/routing for my domain rather than my application or DNS configuration.
Could a Vercel engineer investigate why aymwvn.me is currently being returned to clients with the unreachable Anycast addresses 216.198.79.1 and 216.198.79.65?
I can provide the full vercel-debug.txt if needed.