Vercel support is not responding — urgent intermittent TLS handshake failures on Pro account

Current vs Expected Behavior

A subset of US-based users have been hitting ERR_SSL_PROTOCOL_ERROR, ERR_SSL_PACKET_LENGTH_TOO_LONG, and tlsv1 alert protocol version errors when accessing our production domains hosted on Vercel Pro. Our customers — including paying users on live sales calls — are unable to load the site.

Expected: TLS handshake completes cleanly for all users worldwide. Actual: ~5–10% of US users get TLS errors. Cert chain is valid (Let’s Encrypt R12, issued via Vercel), SSL Labs and Hardenize both show the configuration as clean from external scanners. Issue is region/edge-POP specific, not a config problem on our side.

A support ticket was opened on May 11. As of today (May 15), no meaningful response from Vercel support. This is our highest-priority incident.

Getting the same issues reported from our customers as well.