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:
| IP | Result |
|---|---|
| 216.198.79.3 |  HTTP 200, ~12ms |
| 216.198.79.67 | HTTP 200, ~9ms |
| 216.198.79.131 | HTTP 200, ~8ms |
| 216.198.79.195 |  Connection timed out after 3s (ping succeeds — so it’s a filtered/dropped connection, not a routing failure) |
| 64.29.17.3 | HTTP 200, ~9ms |
| 64.29.17.67 | HTTP 200, ~11ms |
| 64.29.17.131 | HTTP 200, ~8ms |
| 64.29.17.195 | HTTP 200, ~8ms |
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
- 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.