Custom domain unreachable — TLS handshake hangs, dashboard shows everything as valid - Help

Hi all — hoping someone's run into this before.

My custom domain (orkidiastudio.com / www.orkidiastudio.com, on a Hobby plan) has been completely unreachable for about a day now — from my own browser and from a separate testing environment on a totally different network. Here's what I've already checked and tried:

Symptom: the connection reaches the server, starts the SSL/TLS handshake, and then just hangs and times out — no error, no response, nothing. Domains tab: shows green checkmarks, "Valid Configuration," for both domains. Deployments tab: latest deployment shows "Ready," and it's correctly attached to both domains. Firewall tab: no custom rules, Bot Protection off, nothing unusual. The project's own *.vercel.app URL works perfectly and loads instantly — so hosting/build is fine, it's specific to the custom domain. I already tried: clicking Refresh on both domains, and fully deleting + re-adding both domains (waited over an hour after re-adding — no change). Vercel's own status page shows all systems operational, so it doesn't look like a platform-wide incident. Since this problem area (Domains → SSL Certificates) doesn't have direct support access on the Hobby plan, I'm hoping someone here has seen this exact pattern before, or a staff member can take a look. This is a live business site, so any pointers are much appreciated.

Project: orkidia-studio-web (team: catabeltran-3246's projects)

From outside your network it looks fine right now, so this may have cleared, or be local to your path. Measured a minute ago:

orkidiastudio.com → A 216.198.79.1, no AAAA, Let's Encrypt certificate for orkidiastudio.com, HTTP 308 to www in 0.3s
www.orkidiastudio.com → CNAME d23db439650db9ed.vercel-dns-017.com → 216.198.79.65, 64.29.17.65, Let's Encrypt certificate for www, HTTP 200 in 0.3s

Both are Vercel addresses and both certificates carry the right names, which matches the green dashboard. A handshake that starts and then hangs, from two networks, while the *.vercel.app URL is instant, usually means the TCP connection is landing somewhere other than Vercel for you specifically. Three checks from the machine where it hangs:

curl -v --max-time 10 https://www.orkidiastudio.com/ and read the Connected to ... (IP) line. If the IP is not 216.198.79.x or 64.29.17.x, your resolver is serving a stale or overridden record. Flush DNS, or test with --resolve www.orkidiastudio.com:443:64.29.17.65 to bypass it.
Try it on a phone on mobile data. If that works, the problem is a router, ISP or security product in your path, not the domain.
Check for an IPv6 route: curl -6 -v https://orkidiastudio.com/. There is no AAAA record, so a resolver that synthesises one (DNS64) or a cached old AAAA would produce exactly a hang.

If all three still fail for you now, post the Connected to line and I can look again.

Hi all — hoping someone's run into this before.

Project: orkidia-studio-web (team: catabeltran-3246's projects)

From outside your network it looks fine right now, so this may have cleared, or be local to your path. Measured a minute ago:

orkidiastudio.com → A 216.198.79.1, no AAAA, Let's Encrypt certificate for orkidiastudio.com, HTTP 308 to www in 0.3s
www.orkidiastudio.com → CNAME d23db439650db9ed.vercel-dns-017.com → 216.198.79.65, 64.29.17.65, Let's Encrypt certificate for www, HTTP 200 in 0.3s

curl -v --max-time 10 https://www.orkidiastudio.com/ and read the Connected to ... (IP) line. If the IP is not 216.198.79.x or 64.29.17.x, your resolver is serving a stale or overridden record. Flush DNS, or test with --resolve www.orkidiastudio.com:443:64.29.17.65 to bypass it.
Try it on a phone on mobile data. If that works, the problem is a router, ISP or security product in your path, not the domain.
Check for an IPv6 route: curl -6 -v https://orkidiastudio.com/. There is no AAAA record, so a resolver that synthesises one (DNS64) or a cached old AAAA would produce exactly a hang.

If all three still fail for you now, post the Connected to line and I can look again.