Hi all — hoping a Vercel staff member or someone at the network layer can look at this.

Project: pm-atlas-site Domain: pmatlas.xyz (redirect to www.pmatlas.xyz, 307) Affected network: Ooredoo Oman, AS50010, tested from Muscat

Problem: The apex domain is completely unreachable from this ISP. www works fine. Not a cert or config issue — Vercel dashboard is clean, cert is 5h old, DNS is Vercel-managed.

Ran the vercel-connect-debug tool from an affected machine. Results:

Three of Vercel's anycast IPs drop 100% of ICMP and TCP:443 attempts from AS50010. Traceroute dies at Ooredoo's core (10.129.32.73) and never leaves the ISP:

216.198.79.1 — unreachable 216.198.79.65 — unreachable 64.29.17.65 — unreachable

The other five (216.198.79.129, .193, 64.29.17.1, .129, .193) are reachable and respond correctly with 307 → www.

DNS for pmatlas.xyz from Ooredoo's resolver returns:

pmatlas.xyz. 844 IN A 216.198.79.65 ← unreachable pmatlas.xyz. 844 IN A 64.29.17.65 ← unreachable

Both IPs are in the unreachable set — so 100% of connection attempts fail from this ISP. www.pmatlas.xyz resolves to a different subset that includes reachable IPs, which is why www works.

SSL Labs confirms the same failure across scanners: https://www.ssllabs.com/ssltest/analyze.html?d=pmatlas.xyz — reports "Failed to communicate with the secure server" on 216.198.79.1 and 216.198.79.65.

Ask:

Can someone check BGP reachability for those three specific anycast IPs from AS50010, or the peering paths involved? Is there a reason the DNS record set for the apex vs www would consistently segregate this way for this hostname?

Full vercel-debug.txt output available on request. Also happy to run any additional diagnostic from the affected machine.

Thanks.