Rank, 14 days: 8 on the Vercel sheet
30 people reported
All time, since Aug 1.
Custom domain edge IPs time out
“Because both currently resolved IPs time out, the browser fails to connect after about 21 seconds.”
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/9174/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 domains time out on some Vercel edge IPs from certain ISPs. DNS resolves to edge IPs like 216.198.79.1 and 64.29.17.1 that time out, while vercel.app deployments and other edge IPs respond.
Is this your bug?
File my report- Where
- Custom domains
- Error text
216.198.79.1:443 -> timeout- Versions
- 64.29.17
- Platforms
- iOS, macOS, Windows
- How bad
- Stops work: a core feature can't be used.
Not quite your bug?
- Custom domain response stalls9 people
- Custom domains time out3 people
- Custom domain unreachable on Claro2 people
Original reports31, newest first
- Intermittent custom-domain HTTPS timeouts: .65 IPs fail, .1 works#51576
- Vercel Anycast IPs unreachable from Claro Brazil (AS28573) — HTTPS timeouts#51409
- Custom domains time out on HTTPS, but Vercel deployment works#50671
- Custom domain not working in Morocco — connection timeout#50512
- Custom domain not working in Morocco — connection timeout#50511
- Starlink Brazil: custom domains time out on 216.198.79.1; alternate Vercel IPs work#49960
- Deployment unreachable from one network on specific Vercel IPs#49913
- Regional access to .vercel.app varies by ingress IP from Russia#49777
- Issue: 216.198.79.0/24 unreachable from China Mobile (CMCC, AS9808)#49600
- Intermittent connection timeouts to Vercel custom domain from Morocco#49530
Show all 31Show only the newest 10
- Custom domains inaccessible on Russian mobile networks, but vercel.app works#49469
- Custom domain stalls from Russian networks while vercel.app alias works#49440
- Vercel edge IP 216.198.79.1 unreachable from Myanmar but works through VPN#49025
- experiencing an ISP-specific connectivity problem with my production custom domain#48938
- MTN Rwanda cannot reach Vercel edge IPs 64.29.17.x / 216.198.79.x, while legacy Vercel IPs work#48856
- Custom domain intermittently unreachable: 3 of 4 edge anycast IPs fail raw TCP handshake#48804
- Custom domain unreachable from some Russian ISPs while .vercel.app works#48756
- Multiple Vercel Deployments Unreachable from Rwanda — Possible Regional Routing Issue Category#48509
- Custom domains time out intermittently — Vercel serving dead anycast IPs on port 443#48349
- Custom domains unreachable on Orange Morocco, but Vercel.app URLs work and other networks work#47886
- Vercel custom domains unreachable from Moroccan mobile networks – specific Anycast IPs timeout#47833
- Morocco routing issue to Vercel IPs - tayssirfroid.com#47655
- Custom domain timeout from Morocco while vercel.app works normally#47582
- Orange Poland cannot reach SegmentParty custom domain, vercel.app works#47575
- Vercel custom domain resolves to 4 unreachable Anycast IPs while 4 other Vercel IPs work#47415
- Vercel custom domains unreachable from Morocco – Edge/Anycast routing issue (216.198.79.1)#47412
- NIDPG deployment unreachable without VPN — suspected Vercel edge/network routing issue#47404
- Custom domain www.digistudio.dev times out from Orange Morocco - unreachable#47359
- Selective Vercel Edge IP reachability issue from Morocco / MEDITELECOM#47341
- Partial reachability failure to Vercel custom-domain edge IPs from Morocco#47042
- Custom domain unreachable from Morocco, vercel.app deployment works#46974