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

vercel.com

Troubleshooting domains

Learn about common reasons for domain misconfigurations and how to troubleshoot your domain on Vercel.

You can also use v0 to narrow down the possibilities.

This seems to be working for me now, connecting from Toronto and confirming the www redirects to the root domain

I'll check internally to see if we have any other reports of slow DNS but DNS is one of those things that requires the whole world to orchestrate correctly and sometimes propagation takes longer

Thank you! I understand that, guess I am just spoiled because it would usually work within < 30 minutes. I checked it on https://www.locabrowser.com/ there were no responses from 6 different countries, so I assumed something was wrong.

I'll just have to wait I guess.

yeah I remember ~10 years ago it was standard to wait 24 hours for full propagation, had to do full blue/green deployment setups with both settings running in parallel just to ensure zero downtime

the fact that 30 minutes is now an expectation is such a huge win for the industry

Hey! It's been two days now since I updated the CNAME settings - still not working for me in Spain. Also the weird thing is that the DNS propagation checkers always display different values, so one day it's propagated in 4 US states, next day it's not. I feel like there's an issue somewhere.

Also tested it using https://geotargetly.com/geo-browse and three another countries could open it. Any idea what's going on?

Thanks

I figured it out. For anyone that might have a similar issue:

There was a leftover DNSSEC record from namecheap and they didn't sync it properly. Support removed it and it works as expected.

Thanks for sharing your solution here @foobarfoobar