Hello Vercel team,
Our custom domain hoteika.ru is intermittently unreachable or only partially renders for users on several Russian residential and mobile networks unless they enable a VPN. From the same affected connections, hotelki-ebon.vercel.app works normally.
Project details: [PROJECT DETAILS REDACTED]
What we verified:
- The domain is verified in Vercel and the production deployment is Ready.
- Nameservers are
ns1.vercel-dns.comandns2.vercel-dns.com. - TLS certificates for
hoteika.ruandwww.hoteika.ruare valid. www.hoteika.ruredirects to the apex correctly.- Depending on resolver/location, the apex resolves to
216.198.79.1,216.198.79.65,64.29.17.1, or64.29.17.65. - One diagnostic from Russia took 23.8 seconds, returned a zero-byte body, and ended with
CURLE_HTTP2_STREAM (92). - At the same time, 20 Globalping probes in Russian eyeball networks returned HTTP 200, so this appears selective by ISP or route rather than a general DNS, TLS, or application issue.
This looks similar to other reports where a custom domain on Vercel shared Anycast ranges fails from a specific region or ISP while the corresponding .vercel.app hostname works.
Could the networking team check whether affected requests reach Vercel and whether there are HTTP/2 or routing issues for these shared Anycast ranges from Russia? If possible, can the domain be moved to another IP pool? Please let us know which traceroute/MTR format and exact timestamps would be most useful; we can collect them from affected users.
Thank you.