Hello,
I am experiencing a persistent routing/reachability issue with my Vercel custom domain.
Domain:
Country: Morocco
ISP / ASN: AS36925 MEDITELECOM
The issue has been reproducible since approximately July 30, 2026.
I ran the official Vercel Connect Debug Script from an affected Wi-Fi connection.
The script tested the Vercel IP range for my domain.
UNREACHABLE from this connection:
216.198.79.1 -> TCP 443 timeout / 100% packet loss 216.198.79.65 -> TCP 443 timeout / 100% packet loss 64.29.17.1 -> TCP 443 timeout / 100% packet loss 64.29.17.65 -> TCP 443 timeout / 100% packet loss
REACHABLE from the exact same connection:
216.198.79.129 -> HTTP 200 OK 216.198.79.193 -> HTTP 200 OK 64.29.17.129 -> HTTP 200 OK 64.29.17.193 -> HTTP 200 OK
All reachable addresses successfully serve mrarbitre.com with:
Server: Vercel X-Powered-By: Next.js HTTP/1.1 200 OK
The critical part is that DNS currently resolves mrarbitre.com to unreachable addresses.
Local resolver: 216.198.79.1 216.198.79.65
Google DNS: 216.198.79.65 64.29.17.1
Therefore browsers receive IP addresses that cannot be reached from this ISP and the domain times out.
The Vercel deployment URL works from the same connection, and the custom domain works over mobile networks.
The domain uses Vercel DNS, Vercel CDN and valid Vercel-managed TLS certificates.
This appears to be a selective Anycast / BGP / peering reachability issue between MEDITELECOM in Morocco and specific Vercel edge addresses.
I have attached the complete output generated by the official Vercel Connect Debug Script.
Could a Vercel team member please escalate this to the Edge Network / Infrastructure team?
Thank you.
