Custom domain times out while native vercel.app domain works

Help
,
1

Current versus Expected behavior

I need help with a custom domain connectivity issue on Vercel.

My native Vercel domain works correctly:

However, my custom domain times out from Brazil:

Browser error:

ERR_CONNECTION_TIMED_OUT

Expected behavior:

The custom domain should load the same app as the native Vercel domain.

Current behavior:

The native Vercel domain loads correctly, but the custom domain times out.

Code, configuration, and steps that reproduce this issue

Project:

plantacheck

Custom domains:

  • plantacheck.com.br
  • www.plantacheck.com.br

Both domains show “Valid Configuration” in the Vercel dashboard.

DNS resolution works correctly:

www.plantacheck.com.br resolves to:

de9a00df76099372.vercel-dns-017.com

64.29.17.1
216.198.79.1

plantacheck.com.br resolves to:

216.198.79.1

Connection tests from Windows / Brazil:

Test-NetConnection www.plantacheck.com.br -Port 443

Result:

TcpTestSucceeded: False

Test-NetConnection 216.198.79.1 -Port 443

Result:

TcpTestSucceeded: False

Test-NetConnection plantacheck.vercel.app -Port 443

Result:

TcpTestSucceeded: True

Traceroute to 216.198.79.1 times out after the ISP route, while plantacheck.vercel.app reaches a Vercel IP successfully.

The Vercel debug script was run with:

www.plantacheck.com.br

But it stopped at:

Range lookup failed - No response from API

The generated vercel-debug.txt only contains that error.

Project information

Framework:

Next.js

Hosting:

Vercel

Domain registrar / DNS:

Registro.br

DNS records currently configured:

A record:

plantacheck.com.br → 216.198.79.1

CNAME:

www.plantacheck.com.br → de9a00df76099372.vercel-dns-017.com

The Vercel dashboard shows both custom domains as Valid Configuration.

Could someone help confirm whether this is a routing, anycast, CDN, edge network, or custom domain endpoint issue with 216.198.79.1?

I do not want to change DNS records blindly because Vercel shows the domain configuration as valid.

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.

3

Update:

I tested the custom domain using a VPN.

Without VPN:
https://www.plantacheck.com.br returns ERR_CONNECTION_TIMED_OUT.

With VPN enabled:
https://www.plantacheck.com.br opens correctly and loads the application.

The native Vercel domain continues to work normally:

This confirms that the custom domain and Vercel deployment are working, but the route/reachability to the Vercel custom domain endpoint from my normal Brazilian network is failing.

The affected endpoint appears to be:
216.198.79.1

This seems consistent with other community reports about custom domains timing out in Brazil while .vercel.app domains work normally.

4

Hi,

If the .vercel.app domain works but the custom domain times out, I’d focus on DNS and routing before looking at the application itself.

A few checks that usually narrow it down quickly:

dig A your-domain.com +short
dig CNAME www.your-domain.com +short
dig NS your-domain.com +short

The important thing is that the public DNS results match what Vercel expects for the domain configuration. I’d also test from a few networks (mobile data, home internet, etc.) because partial DNS propagation can sometimes look like an application outage.

If the apex and www records look correct, can you share the domain status shown in the Vercel Domains tab and the output of those dig commands with any unrelated details removed?

5

Hi Ryu,

Thanks for the guidance.

That makes sense. After waiting and testing again, the custom domain is now reachable normally from different networks, including home Wi-Fi, mobile data, 4G/5G, browser and PWA.

The .vercel.app domain kept working during the issue, so it really looks like this was related to DNS propagation or routing to Vercel’s custom domain endpoint, not the application or Supabase itself.

For now, the issue seems to be resolved. I’ll keep monitoring it, and if it happens again I’ll collect the outputs from:

dig A plantacheck.com.br +short
dig CNAME www.plantacheck.com.br +short
dig NS plantacheck.com.br +short

Thanks again for pointing me in the right direction.

6

Hi Giovane,

Glad it’s working now, and thanks for sharing the follow-up.

Your conclusion sounds reasonable to me. Since the app worked on plantacheck.vercel.app, and the custom domain worked through VPN but not through the normal Brazilian network, it does sound more like a temporary DNS/routing reachability issue than an app or Supabase problem.

If it happens again, I’d capture the checks while the issue is actively happening, because once it recovers the useful evidence disappears pretty quickly:

dig A plantacheck.com.br +short
dig CNAME www.plantacheck.com.br +short
dig NS plantacheck.com.br +short
traceroute plantacheck.com.br
traceroute 216.198.79.1

I’d also keep the “with VPN works / without VPN times out” detail, since that helps separate a domain configuration issue from a regional network path issue.

Really glad it resolved, and nice job testing from multiple networks before changing DNS blindly.