Domain: testbuddy.dev / www.testbuddy.dev — apex A `216.198.79.193`, www CNAME `e6da48d782e39d30.vercel-dns-017.com` (matches the domain card, configuration shows valid).

Multiple US-based visitors on corporate networks repeatedly get `ERR_SSL_PROTOCOL_ERROR` on both hostnames, in regular and incognito windows. From the EU and from general US networks the site is healthy — certificates are valid and the handshake completes from Los Angeles / Dallas / Atlanta probes: https://check-host.net/check-report/489a7b2fkd26

The pattern (multiple distinct corporate networks, recurring over months, connection reset during the TLS handshake) points to security appliances blocking the `216.198.79.x` / `64.29.17.x` ranges, likely due to missing reputation/categorization on the newer IP pools. Asking every affected visitor's IT department to allowlist these isn't sustainable.

Could this project be reassigned to an edge IP pool with established reputation (e.g. `76.76.21.21` / `cname.vercel-dns.com`), or is there another mitigation on Vercel's side? Happy to provide traceroutes and timestamps from affected visitors if useful.