Custom domain timeout from Morocco while vercel.app works normally

Help
,
1

Title:
Custom domain timeout from Morocco while vercel.app works normally

Hello,

I am experiencing a routing/connectivity issue with my custom domain:

The deployment itself works normally on:

The official Vercel diagnostic shows the following from Morocco / AS36925 MEDITELECOM:

Unreachable:
216.198.79.1:443 → timeout
64.29.17.1:443 → timeout

Reachable:
216.198.79.129 → HTTP 200, ~31 ms
216.198.79.193 → HTTP 200, ~31 ms
64.29.17.129 → HTTP 200, ~30 ms
64.29.17.193 → HTTP 200, ~31 ms

DNS for www.cryogenemaroc.com resolves only to:
216.198.79.1
64.29.17.1

Because both currently resolved IPs time out, the browser fails to connect after about 21 seconds.

The issue is reproducible from multiple devices and internet connections in Morocco.

The Vercel deployment is healthy, with:
HTTP 200
Server: Vercel
X-Vercel-Cache: HIT

I also ran the official vercel-connect-debug tool and can provide the full vercel-debug.txt output.

Could someone from the Vercel network/edge team please review the BGP/Anycast routing to 216.198.79.1 and 64.29.17.1 from Morocco / AS36925 MEDITELECOM?

2

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

3

Additional test:
I tested www.cryogenemaroc.com using a Maroc Telecom (IAM) internet connection in Morocco, and the website loads quickly and normally.

The timeout therefore appears to be specific to Orange Maroc / MEDITELECOM (AS36925), rather than a general Morocco-wide DNS or Vercel deployment issue.

On Orange/Meditelecom, the official Vercel diagnostic shows timeouts to 216.198.79.1 and 64.29.17.1, while the same custom domain works normally over IAM.

4

Thanks for reporting this. A related conversation is happening in another thread, so I’m going to close this one. Please join us there :folded_hands: