Production outage: Vercel edge TLS failures on wildcard domains

Help
1

Project: boost-dashtboard

Team: gaderteam

Domains:

*.gader.net

*.daneh.co

Vercel dashboard shows:

“Proxy Status Unknown - Failed to check whether a proxy is in front of this domain”

DNS is correct:

ns1.vercel-dns.com

ns2.vercel-dns.com

Investigation shows TLS handshake failures on specific Vercel edge IPs:

216.198.79.1

216.198.79.65

64.29.17.65

Working IPs:

64.29.17.1

76.76.21.21

Failure occurs across both old and new domains, so it is not domain-specific.

Could Vercel team investigate affected edge nodes/IP pool?

2

FINAL CLEAN MOBILE HOTSPOT VERIFICATION

We performed another clean verification from Oman using a mobile hotspot with VPN fully disabled.

Network:

  • Interface: en0
    • Gateway: 172.20.10.1

      • Public IP: 188.140.136.4

        • No VPN/tunnel used

      • Forced-IP tests against https://gader.net:**

        64.29.17.65 → curl error 28: SSL connection timeout

      • 216.198.79.1 → curl error 28: SSL connection timeout

      • 216.198.79.65 → curl error 28: SSL connection timeout

      • 64.29.17.1 → HTTP/2 308, x-vercel-id indicates bom1 (Mumbai)

    • This reproduces the exact same behavior observed during:
      1. Original Oman mobile hotspot test
        1. Oman Wi-Fi test
          1. Second Oman Wi-Fi test several hours later
            1. Final clean Oman mobile hotspot verification with VPN disabled
          3. The same three IPs fail TLS consistently from Oman: 64.29.17.65, 216.198.79.1, 216.198.79.65. 64.29.17.1 consistently works.
        3. IMPORTANT CONTROL TEST:
      3. When the same Mac was connected through a European VPN, traffic was served through fra1 (Frankfurt), and ALL FOUR IPs — including the three failing IPs above — completed TLS and returned valid Vercel responses. Therefore the IPs themselves are not globally unavailable.
    • Additional investigation showed 64.29.17.1 and 64.29.17.65 are even within the same announced /24, so this does not look like a simple whole-prefix BGP failure.
  • The evidence points to a regional Vercel edge/accelerator/backend path problem affecting Oman-sourced traffic reaching the Mumbai/bom1 path.

This affects BOTH domain families:

  • gader.net / *.gader.net
  • So this is not specific to the Gader rebrand, DNS configuration, application deployment, or Supabase.

Please investigate the bom1/Mumbai edge path for Oman-sourced traffic, particularly the backend/accelerator handling of 64.29.17.65, 216.198.79.1, 216.198.79.65, and compare it with the healthy behavior of 64.29.17.1.

This is production-impacting and causes intermittent or complete site unavailability for users in Oman depending on the Vercel edge IP/path selected.