Custom domains timing out in Brazil while .vercel.app domains work normally

Beested · 2026-05-15 01:25:59.643033+00

``` ``` ``` Hello Vercel team, I’m experiencing an issue where all of my custom domains linked to Vercel projects are timing out, while the default .vercel.app domains continue working normally. Summary of the issue: - Location: Caxias do Sul, Rio Grande do Sul, Brazil - Main affected domain: https://southmindly.com - Default Vercel domain working: https://southmindly.vercel.app - Error: ERR_CONNECTION_TIMED_OUT - The issue happens both on my Wi-Fi network and on mobile data - It also affects other custom domains linked to my Vercel projects, not only southmindly.com What I already checked: - The Vercel dashboard shows the domain as “Valid Configuration” - The default Vercel domain opens correctly - DNS resolution appears correct: southmindly.com resolves to 216.198.79.1 - The root domain has an A record pointing to Vercel - The www domain has a CNAME pointing to Vercel - I already tried flushing the local DNS cache - The issue persists even outside my local network using mobile data From the previous analysis, it seems this may be related to a regional routing issue or something specific to how traffic from my region is reaching Vercel’s edge network. Could you please help investigate this issue or escalate it to the appropriate team? Thank you. ```

1Hello Vercel team,23I’m experiencing an issue where all of my custom domains linked to Vercel projects are timing out, while the default .vercel.app domains continue working normally.45Summary of the issue:67- Location: Caxias do Sul, Rio Grande do Sul, Brazil8- Main affected domain: https://southmindly.com9- Default Vercel domain working: https://southmindly.vercel.app10- Error: ERR_CONNECTION_TIMED_OUT11- The issue happens both on my Wi-Fi network and on mobile data12- It also affects other custom domains linked to my Vercel projects, not only southmindly.com1314What I already checked:1516- The Vercel dashboard shows the domain as “Valid Configuration”17- The default Vercel domain opens correctly18- DNS resolution appears correct:19  southmindly.com resolves to 216.198.79.120- The root domain has an A record pointing to Vercel21- The www domain has a CNAME pointing to Vercel22- I already tried flushing the local DNS cache23- The issue persists even outside my local network using mobile data2425From the previous analysis, it seems this may be related to a regional routing issue or something specific to how traffic from my region is reaching Vercel’s edge network.2627Could you please help investigate this issue or escalate it to the appropriate team?2829Thank you.

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.

https://vercel.com/docs/projects/domains/troubleshooting

You can also use v0 to narrow down the possibilities.

Thanks for the suggestion.

I already checked the main domain configuration items:

The custom domain shows as "Valid Configuration" in the Vercel dashboard
The default Vercel domain works normally: https://southmindly.vercel.app
The custom domain times out: https://southmindly.com
DNS resolves correctly to Vercel: southmindly.com -> 216.198.79.1
The issue happens both on Wi-Fi and mobile data
Other custom domains linked to my Vercel projects are also affected

Because the issue persists on different networks and only affects custom domains, I suspect this may be related to a regional routing issue, ISP routing, or access to Vercel's edge network from my location in southern Brazil.

I'm looking for help to understand what additional diagnostics I should provide or whether this can be escalated for routing investigation.

I'm having the same problem with my projects, did you find any answer/solution?

reply to #3

Estou com o mesmo problema!

I am facing the same issue in Brazil, Mato Grosso.

Affected custom domains:

https://sistema.aaddireito2028.com.br

https://www.aaddireito2028.com.br

Default Vercel domains work normally:

https://painel-aad-2028.vercel.app

https://associacao-direito-2028.vercel.app

Vercel debug script shows the same pattern:

216.198.79.1 timeout / 100% packet loss 64.29.17.1 timeout / 100% packet loss

Other Vercel edge IPs return HTTP/2 200.

ISP: NEOPRINT INTERNET LTDA

Location: Mato Grosso, Brazil

This appears to be the same intermittent routing / Anycast issue affecting custom domains in Brazil.

Leaderboard Winner

Hi Beested, and others seeing this in Brazil,

Since the .vercel.app domains work but multiple custom domains time out, this does not sound like a Next.js/React build issue. I’d narrow it down to DNS vs the network path to Vercel’s custom-domain edge IPs.

A few useful checks from an affected network:

1dig A southmindly.com +short2dig AAAA southmindly.com +short3dig CNAME www.southmindly.com +short45curl -Iv --connect-timeout 10 https://southmindly.com6curl -Iv --connect-timeout 10 --resolve southmindly.com:443:216.198.79.1 https://southmindly.com/7curl -Iv --connect-timeout 10 --resolve southmindly.com:443:64.29.17.1 https://southmindly.com/8

If AAAA returns anything, remove the IPv6 record first. Vercel’s domain troubleshooting docs say third-party custom domains should not point an AAAA record to Vercel:

https://vercel.com/docs/domains/troubleshooting

If DNS is clean and both 216.198.79.1 and 64.29.17.1 time out only from affected Brazilian networks, while the same tests work from another country/network, that is strong evidence for a regional routing/Anycast path problem rather than a domain config problem.

The most useful escalation/debug bundle would be:

1Affected domain:2Working .vercel.app URL:3Affected ISP:4City/state/country:5Timestamp with timezone:6dig A/AAAA output:7curl -Iv output for both edge IPs:8mtr/traceroute to 216.198.79.1 and 64.29.17.1:9Whether it works from another network/VPN:10

That gives Vercel enough signal to tell whether traffic from those ISPs is failing before it reaches the expected edge path.