Rank, 14 days: 17 on the Vercel sheet
9 people reported
All time, since Aug 4.
Custom domain response stalls
“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.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/vercel/issues/9016/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Custom domain response body stalls after HTTP 200. Transfer stops after a few KB and times out, while the same asset downloads completely through the vercel.app hostname.
Is this your bug?
File my report- Where
- custom domains
- Error text
curl: (28) Operation timed out- Versions
- 01.25.53
- Platforms
- macOS, Web, Windows
Not quite your bug?
- Custom domain edge IPs time out30 people
- Custom domain TLS handshake fails6 people
- Edge IP TLS handshake fails2 people
Original reports9, newest first
- Custom domains bazatela.ru / www stall via arn1 while vercel.app completes via fra1#51525
- Custom domain times out while vercel.app works: the IP is not the difference#50939
- [Networking/CDN] Custom domain stalls after HTTP 200, while .vercel.app works on the same IP#50737
- Static JS response stalls after ~20.8 KB on ARN edge (HTTP 200 / HIT)#50214
- Custom domain stalls after HTTP 200 while vercel.app works normally#49526
- Custom domain response bodies stall in Russia, while vercel.app works on the same IPs#49387
- Intermittent ERR_CONNECTION_CLOSED on custom domain while vercel.app works#49355
- Custom domain tpark.ru stalls during response transfer, while vercel.app works normally#48404
- Custom domain returns HTTP 200 but HTML response body is empty (vercel.app works)#47159