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.

https://vercel.com/docs/domains/troubleshooting

vercel.com

Troubleshooting domains

Learn about common reasons for domain misconfigurations and how to troubleshoot your domain on Vercel.

Hi aheedbn,

Given your tests, I would not spend much more time on app code, SSL, or basic DNS. If the custom domain works outside Oman, the .vercel.app domain works from Oman, and only specific 216.198.79.x destinations fail from the same networks, this looks much more like reachability/routing to that anycast edge path.

I’d capture TCP 443 evidence rather than relying on ping alone, since ICMP can be filtered:

1
dig A certifiedexporters.com +short
2
curl -4Iv --connect-timeout 10 https://certifiedexporters.com/
3
mtr -4 -T -P 443 -c 20 216.198.79.1
4
mtr -4 -T -P 443 -c 20 216.198.79.129
5

If .1 fails and .129 succeeds from the same Oman connection, that is a strong signal that the deployment and domain config are probably fine, and the failure is specific to the route toward the IP currently used by the apex record.

I would not change the apex A record to another random Vercel IP unless the Vercel domain card explicitly tells you to use it. The alternate IP test is useful as a diagnostic, not necessarily as a supported fix.

One workaround to test is whether www.certifiedexporters.com resolves to a reachable Vercel target from Oman. If it does, you could temporarily make www the canonical hostname while the apex route is investigated.

Thanks for the suggestions, Ryu.

I ran additional TCP 443 tests from the same Omanconnection.

Working:

1
https://certified-exporters.vercel.app
2

Resolves to:

1
216.198.79.3
2
64.29.17.3
3

curl -4Iv --connect-timeout 10 returns:

1
HTTP/1.1 200 OK
2

Failing:

1
https://certifiedexporters.com
2

Resolves to:

1
216.198.79.1
2

curl times out before the TLS handshake.

Also:

1
https://www.certifiedexporters.com
2

Resolves to:

1
216.198.79.65
2
64.29.17.65
3

and curl also times out.

So from the same Oman connection:

• ✅ 216.198.79.3 / 64.29.17.3 are reachable (vercel.app)

• ❌ 216.198.79.1 (apex)

• ❌ 216.198.79.65 / 64.29.17.65 (www)

Vercel Support also reviewed the connectivity report generated by their debug script and confirmed it appears to be a partial routing/BGP issue affecting specific IPs in the 216.198.79.0/24 range. They've escalated the case to their Infrastructure Team for investigation.

Thanks again for pointing me toward TCP-based testing—it provided much clearer evidence than ping or traceroute alone.

Adding another confirmed, independently-diagnosed data point — this looks like a broader pattern, not an isolated case.

My setup:

• Domain: phoenixftoman.com
• Vercel project: phoenix-globnet-site
• Location: Muscat, Oman
• ISP: OmanTel (AS28885)

What I found, using the official vercel-connect-debug script against my project's assigned edge IPs:

So 7 of 8 assigned addresses work fine — only 216.198.79.195 is blocked from my specific network. My custom domain's originally-assigned A record, 216.198.79.1, also times out from this same connection (a different address in the same /24, same symptom).

Full diagnostic output: [paste your pastebin link here]

This appears to be the same underlying issue reported across several other threads, each affecting a different specific IP within the same new ranges:

• Custom domain unreachable from Oman — regional routing issue with 216.198.79.0/24 — Oman, OmanTel AS28885

Vercel Community

Custom domain unreachable from Oman - Regional routing issue with 216.198.79.0/24

Issue Summary My custom domain certifiedexporters.com is completely unreachable from Oman (ERR_TIMED_OUT), while the default Vercel domain...

• TLS timeouts to Vercel edge IPs from Oman (AS204170) — Oman, different ISP (Awasr)
• Site unreachable from Oman — 3 of 8 assigned edge IPs are blackholed — Oman
• New edge ranges 216.198.79.0/24 + 64.29.17.0/24 unreachable from Morocco (AS36925) — Morocco, same ranges

Given how many independent reports this now has, across multiple ISPs and at least two countries, this looks like a genuine Vercel Anycast/edge routing issue specific to the newer 216.198.79.0/24 and 64.29.17.0/24 ranges — not something any of us can fix on our end. Each affected user seems to have a different specific IP blocked within these ranges, which suggests inconsistent regional routing/peering to parts of this new pool rather than a single blanket block.

Current workaround: I've set up GoDaddy domain forwarding to my .vercel.app URL, which works since it happens to resolve to a working address. Would like to move back to a direct custom domain setup once this is resolved.

I also raised this via Vercel support chat — the agent confirmed it as a real routing issue and attempted to escalate to a support case, but case creation for "Domains > DNS Configuration" is gated behind a paid plan, so posting the full evidence here instead, where the other confirmed reports live.

We’re experiencing the same issue with a Vercel-hosted production custom domain from Oman. The custom domain was unreachable, while the corresponding .vercel.app deployment remained accessible.

Switching the custom domain to Vercel's 76.76.21.21 / cname.vercel-dns.com routing has restored connectivity from our side, and Vercel Support Agent confirmed that this configuration is safe to retain.

Adding another affected case here in case it helps Vercel investigate the Oman regional routing issue.