Project: optmebelug-new
Working deployment: https://optmebelug-new.vercel.app
Problematic custom domain: https://www.optmebelug.ru
We are seeing a reproducible issue where the custom domain returns HTTP 200 successfully, but the response body stalls after only a few KB and then times out.
The same deployment and the same static asset work normally through the vercel.app hostname.
Example asset:
Content-Length:
179098 bytes
Latest failing test from macOS:
curl -v --max-time 20 -o /dev/null https://www.optmebelug.ru/images/1.webp
Result:
HTTP/2 200 server: Vercel content-length: 179098 x-vercel-id: fra1::bp7dq-1790026496918-de6424b07109
Only 10134 out of 179098 bytes were received before timeout:
Operation timed out after 20001 milliseconds with 10134 out of 179098 bytes received curl: (28) Operation timed out
The same asset downloads completely through:
We also reproduced the issue by forcing different Vercel edge IPs with curl --resolve.
Failing request IDs: fra1::qqvx6-1789996059249-3c7137d1a0a0 fra1::gr7td-1790024732979-0258f6264ae3 fra1::9m94v-1790026242526-3bafc85a0bb6 fra1::bp7dq-1790026496918-de6424b07109
Working request ID: fra1::ppqsn-1789995775856-d0eecb4b6e4a
TLS certificate for www.optmebelug.ru verifies correctly.
Vercel Dashboard shows: www.optmebelug.ru → Production → Valid Configuration
DNS is currently configured with the project-specific CNAME:
www.optmebelug.ru CNAME → 9c1c2d6deba8479b.vercel-dns-017.com
The issue still reproduces even when forcing the new Vercel IP directly, so this does not appear to be a DNS propagation issue.
Expected behavior: The custom domain should deliver the same deployment and static assets normally, just like optmebelug-new.vercel.app.
Actual behavior: The custom domain returns HTTP 200 and correct Content-Length, but the response body stalls after a few KB and eventually times out.
Could Vercel staff please investigate custom-domain edge delivery/routing for www.optmebelug.ru?
I can provide additional curl logs, screenshots, and request IDs if needed.
