(edited)
Hello Vercel team,
I am experiencing a connectivity issue with custom domains from Russian networks.
Project:
- Production domain: https://aryapaw.dev
- Preview domain: https://preview.aryapaw.dev
- Working Vercel alias: https://aryapaw-website-aryapaws-projects.vercel.app
The issue:
The same deployment works correctly through the Vercel vercel.app alias, but custom domains fail from Russian mobile networks.
Affected:
Working:
Verified:
- Both custom domains show "Valid Configuration" in Vercel Dashboard.
- DNS configuration is correct.
- TLS handshake succeeds.
- Valid certificates are presented.
- The application itself works because the same deployment loads through the
vercel.appalias from the same network.
Observed behavior from Russian mobile networks:
- DNS resolution works.
- TCP connection succeeds.
- TLS handshake succeeds.
- HTTP response headers are received.
- Response body transfer stalls and the connection eventually resets or times out.
Example:
- Request to
/succeeds. - Vercel returns:
HTTP/1.1 307 Temporary Redirect Location: /ru
- Request to
/rustarts. - Response body transfer stops and the connection is reset or times out.
Independent measurements from multiple Russian locations:
- https://geopinger.net/result/ycv4ttuxzlqgviy7x2mk5zwt
- https://geopinger.net/result/6txhxuqrzxqguewsbye6ucrz
- https://geopinger.net/result/updzq3baz3qgutd5zvc5eqzh
This appears similar to other reports where custom domains fail from Russian networks while the corresponding vercel.app deployment works.
Could you please check whether there are any known connectivity issues affecting custom domains from these regions or edge paths?
Thank you.
