Vercel Edge Network hostname routing failure in Sweden and Nordic regions

Help
, ,
1

Hi everyone,

I’m experiencing a regional outage for my domain taxreliefapp.io (registered with Vercel).
The website works globally, but fails only in Sweden/Nordic region, both on Wi‑Fi and 5G mobile data.

This is not a configuration issue — I’ve run the full Vercel connectivity debug script and performed extensive diagnostics. Everything points to an internal hostname → project routing issue on Vercel’s edge network.

What works

1. All Vercel edge IPs are reachable
From Sweden (AS206774 Internetnord AB), all of these respond normally:

  • 216.198.79.1

  • 216.198.79.65

  • 216.198.79.129

  • 216.198.79.193

  • 64.29.17.1

  • 64.29.17.65

  • 64.29.17.129

  • 64.29.17.193

  • Ping: 0% packet loss, 4–12 ms latency

  • TLS: Successful

  • HTTP/2: Successful

  • Redirect: 307 → https://www.taxreliefapp.io/

2. DNS is correct

  • Using Vercel nameservers
  • A-records resolve correctly
  • No DNSSEC issues
  • Google DNS and Cloudflare DNS both resolve properly

3. SSL certificate is valid
Let’s Encrypt certificate for *.taxreliefapp.io is valid and served correctly.

What fails

Hostname-based requests fail ONLY in Sweden/Nordics

  • https://www.taxreliefapp.io → unreachable
  • https://taxreliefapp.io/scan → unreachable
  • Happens on Wi‑Fi and 5G
  • Happens across devices
  • Happens across browsers

Direct IP access works
If I curl the IP directly, the Vercel edge responds correctly and redirects to the hostname.

This strongly suggests:

The hostname → project mapping is broken or stale on the Nordic edge nodes. :right_arrow:

Debug evidence

I ran the official Vercel debug script:

curl -s https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.sh | bash | tee vercel-debug.txt

Key findings:

  • All edge IPs reachable
  • TLS handshake OK
  • HTTP/2 OK
  • Redirect OK
  • DNS OK
  • SSL OK
  • Hostname unreachable only in this region

I can attach the full vercel-debug.txt if needed.

Why I’m posting here

I attempted to submit a support case, but the form is blocked on the Hobby plan — even though this is clearly an infrastructure-level issue affecting a paid domain.

This outage is impacting my users in the Nordic region, and I’m running a global campaign this week, so I’d appreciate any help or visibility from the Vercel team.

Request

Could someone from the Vercel engineering team please investigate the edge routing / hostname mapping for:

  • taxreliefapp.io
  • www.taxreliefapp.io

Specifically on the Nordic edge nodes?

Happy to provide:

  • full debug logs
  • traceroutes
  • timestamps
  • reproduction steps

Thank you in advance — and thank you to anyone in the community who can help confirm whether they see the same issue from Sweden/Nordics.

1 Like
2

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

You can also use v0 to narrow down the possibilities.

7

Can you go through this post?

1 Like
8

Thanks Pauline — I read the IP blocking guide, but my debug results don’t match that pattern.

In my case:

• All Vercel edge IPs respond normally
• 0% packet loss
• TLS handshake succeeds
• HTTP/2 works
• Redirect works
• DNS resolves correctly
• SSL is valid
• No connection refused
• No timeouts
• No ISP filtering patterns

However, the hostname www.taxreliefapp.io is unreachable globally (confirmed from Sweden and Spain). Direct IP access works, but hostname-based requests fail everywhere.

This suggests the issue is not ISP blocking, but a hostname → project routing issue on Vercel’s side.

Could you help investigate the hostname mapping for:

• taxreliefapp.io
• www.taxreliefapp.io

Happy to provide the full debug file if needed.

9

Hi team, just a quick update: The issue is fully resolved on my side. It turned out to be a missing www CNAME record, and once added, the domain propagated correctly. Everything is working now, so no further changes are needed from your end. Thanks for the help and please leave the current configuration as it is.

10

Great to hear! Thanks for sharing what worked for you.

11

Solution summary

To resolve this, ensure that all required DNS records, specifically the www CNAME record, are correctly configured in the Vercel project settings or with your external DNS provider. In this case, adding the missing www CNAME record allowed the hostname-to-project mapping to propagate correctly across all Vercel Edge Network nodes.