Hello Vercel Community,
Could Vercel help investigate address-specific TCP/443 reachability for www.iptvcursor.com?
During bounded checks on 30 October 2026 (approximately 21:47-21:54 UTC) from one verification network, we observed:
| Destination IPv4 address | Result for the same custom hostname |
|---|---|
216.198.79.1 | TCP connected, TLS validated successfully, and /api/health returned HTTP 200. |
64.29.17.65 | TCP timeout before TLS. |
64.29.17.1 | TCP timeout before TLS. |
216.198.79.65 | TCP timeout before TLS. |
The per-address probes preserved the custom hostname for TLS SNI/hostname validation. The failing probes did not establish a TCP connection within a 7-second bound; a separate curl check to 64.29.17.65 also timed out before TLS. TLS validation was not bypassed.
Vercel deployment aliases work. At the latest checks, standard DNS-based requests to both / and /api/health on the custom domain also returned HTTP 200. Domain assignment/verification and TLS certificate validation succeeded.
We could not obtain usable independent external-network TCP/HTTPS testing, so these observations do not establish a global outage or identify whether the cause is local-network, regional, transit-related or Vercel-side.
Could Vercel clarify:
- Are all four addresses expected active ingress addresses for this custom domain?
- Can the relevant team investigate potential regional routing or address-specific reachability for this observation window?
- Is there any supported DNS guidance we should review before considering changes?
No root cause is confirmed, and no DNS, firewall or certificate changes have been made as a workaround. We are seeking investigation and advice, not requesting automatic configuration changes. Thank you.