I am unable to connect to my domain chief.bot from my local network in Florida (Spectrum/Charter ISP). The connection attempts to all Vercel edge IPs in the eastern US (216.150.1.x and 216.150.16.x ranges) are failing with a TLS protocol version error: ‘LibreSSL/3.3.6: error:1404B42E:SSL routines:ST_CONNECT:tlsv1 alert protocol version’. The domain resolves correctly to Vercel infrastructure, and the connection works perfectly when I use a VPN, which indicates this is specific to my direct network path to Vercel’s eastern US edge. I’ve tested all 8 Vercel edge IPs assigned to chief.bot and they all fail with the same TLS handshake error. Ping latency is normal (27-50ms). The debug output shows consistent TLS failures across 216.150.1.1, 216.150.1.65, 216.150.1.129, 216.150.1.193, 216.150.16.1, 216.150.16.65, 216.150.16.129, and 216.150.16.193.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| ERR_SSL_PROTOCOL_ERROR for specific regions | 1 | 44 | October 9, 2025 | |
| Partial Vercel Edge IP Unreachable from Brazilian ISPs (216.198.79.1) | 1 | 25 | April 30, 2026 | |
| Vercel TLS handshake stall on specific Anycast VIPs from South Korea | 1 | 41 | March 10, 2026 | |
| Intermittent ERR_SSL_PROTOCOL_ERROR and TLS handshake failures on Vercel custom domain | 2 | 47 | February 4, 2026 | |
| Vercel Edge Network hostname routing failure in Sweden and Nordic regions | 7 | 32 | April 16, 2026 |