Ryu Hi Rodrigo, This is a strong repro. Since the .65 hosts in the same ranges work, the legacy IPs work, but the .1 hosts fail for both ICMP and TCP/443 from AS28668, I would not treat this as an app/build issue or normal DNS propagation. It looks more like a route/filtering problem for those specific Vercel anycast endpoints from that ISP path. If you can, I’d add TCP-based traces too, since ICMP can be filtered differently from HTTPS traffic: And a direct HTTPS comparison: The useful summary is: I’d also send the same evidence to the ISP if possible. From the community side, this is probably en
Badreladraoui1 Same issue from Morocco (AS36925 Meditel), full details here: community.vercel.com/t/new-edge-ranges-216-198-79-0-24-64-29-17-0-24-unreachable-from-morocco-as36925-legacy-works/46736
system 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. vercel.com/docs/domains/troubleshooting
Ryu Hi Dustin, Given what you’ve already checked, I’d avoid more remove/re-add cycles for now. If the dashboard shows Valid Configuration, the CNAME resolves to Vercel, and openssl with the correct SNI still gets no peer certificate, then this is past the usual app-code or route-debugging layer. I’d capture one clean set while the domain is still failing: The important parts to include are: If HTTP reaches Vercel but HTTPS resets before any certificate is served, that strongly suggests the request is failing at TLS/certificate serving before it ever reaches your deployment. I would also avoid post
Dustin Luther Thanks so much for the feedback. About a day after I posted this, the SSL certificate seems to have regenerated itself and everything has been working fine with the app since. I don't know if someone at vercel reset something or the system reset itself after a while, but the issue is now resolved.
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Ryu Hi Radit, The part I’d double-check is whether the URL you’re testing is the deployment’s unique generated URL from the deployment details page, not only project/branch aliases. A platform 404: NOT_FOUND on an alias can be an alias/routing issue. A platform 404: NOT_FOUND on the unique deployment URL is a stronger signal that the deployment is not being served correctly at the edge even though the dashboard says Ready. I’d capture all three side by side: If the unique deployment URL also returns Vercel’s platform NOT_FOUND, then I would not focus on Next.js routes, custom not-found.tsx, or run
system 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. vercel.com/docs/domains/troubleshooting
Oynickj Hi Jake – huge apologies for the delay, and we hear you. We're working our way through the caseload – we have a small (but growing) specialist team that can help (account compromises require careful ownership verification) and are building system improvements to make it faster across the board. In the meantime, mind sharing your case number with me? Thanks so much...
system 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. vercel.com/docs/domains/troubleshooting
Bahadurkhan10 I am experiencing the same problem for one of US location. Have you found any solution for this issue of yours, that will be very helpful to me. community.vercel.com/t/custom-domain-inaccessible-from-one-us-isp-location-while-vercel-app-url-works/46326?u=bahadurkhan10
system 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. vercel.com/docs/domains/troubleshooting
Ryu Hi Joyce, That message usually means you’re looking at the old account-level Domains area. For a project domain, I’d ignore that page for now and check the domain from the project itself: Project → Settings → Domains Then compare the DNS records at your registrar with the exact values shown on that domain card. For example: For the root/apex domain, Vercel normally expects an A record. For www or another subdomain, it normally expects a CNAME. If there is an old AAAA record, duplicate A record, or a value copied from a different Vercel project, the dashboard can still show Invalid Configuratio
Joycesee1 8817 Hello Thank you for getting back to me. Domain A 216.198.79.1 and CNAME e36ec626888c93e9.vercel-dns-017.com I hope this matter can be resolved. When I type www.jmosesbooks.com it redirects to jmosesbooks.com. Therefore my understanding is www.jmosesbooks does not work and jmosesbooks.com works sometimes. I hope you can let me know which to use as I want to give my website details on my books for people to buy but right now I am stuck not sure which website details to give please help me if there is any information you need please let me know thanks Joyce
system 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. vercel.com/docs/domains/troubleshooting
Ryu Hi copeyeu17-1068, Your evidence does seem to narrow this down past normal DNS/app debugging. The strongest part is that HTTP reaches Vercel and returns the normal redirect, while the TLS handshake fails before a certificate is served for the cardinalleads.xyz SNI. I’d package the escalation around the smallest reproducible case, not the full history: If the same Vercel edge IP serves another Vercel hostname but returns alert 49 only for this zone/SNI, that is a much more actionable signal than “SSL is broken.” I’d also include the fresh subdomain test you did, because tlsprobe.cardinalleads.x
unpacify Thanks @Ryu — agreed on all points, especially that vercel certs ls only proves issuance, not that the terminator will select/serve the cert for the SNI. Here is your exact command list, re-run fresh today (19 Jul 2026), as the minimal reproducible case: DNS (all resolving through Vercel's own nameservers): TLS — the deny, reproduced via DNS and pinned to a single edge IP: Same edge IP, seconds apart: my other domain on the same team completes a TLSv1.3 handshake with a verified cert; cardinalleads.xyz gets a fatal in-session access_denied before any certificate is presented. HTTP router knows
system 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. vercel.com/docs/domains/troubleshooting
Ryu Hi Gana4225, I don’t think the TXT record at: will satisfy verification if Vercel is specifically asking for: That usually means Vercel is treating work.gd as the ownership boundary, and stream.gana.work.gd as a subdomain under it. Since you do not control work.gd, you would not be able to complete that verification yourself. I’d first confirm the public DNS is correct for the records you can control: If those are correct but Vercel still asks for _vercel.work.gd, then this probably is not a normal DNS propagation problem. It sounds more like the shared registry boundary for work.gd is not bei
system 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. vercel.com/docs/domains/troubleshooting
Criandogames This guide didn't solve my issue. I followed all the troubleshooting steps and re-added the required TXT records at _vercel.tatamemaster.com.br exactly as instructed in the Vercel dashboard, but both domains (prof.tatamemaster.com.br) are still showing "Verification Needed" / "This domain is linked to another Vercel account." I've confirmed the TXT records are published and visible via public DNS lookup. I've also refreshed the domain status in the dashboard multiple times over the past 24 hours with no change. Could a human take a look at this? I need help either completing the domain transfe
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Chiinchaa451 8597 Thank you. I followed the 404 debugging guide and verified the relevant items. Additional results: Canonical domain configuration status: Alias is assigned to the current/latest Ready Production deployment. No duplicate, wrong-project, pending, or invalid marker was found. Canonical dynamic routes still return Vercel platform NOT_FOUND. Trusted IPs or access-group restriction affecting this domain: None detected / not applicable on the Hobby plan. Standard Deployment Protection affects the generated deployment URL, not the canonical Production domain. Blue 404 information box: Code: NOT_FOUND
Chiinchaa451 8597 I found several recent Community reports with the same behavior, including: “Production aliases return 404, while the underlying deployment serves fine on its hashed URL” “Edge 404 (NOT_FOUND) despite valid alias — possible control plane / edge routing desync” “Custom domain returns 404 NOT_FOUND on fra1 edge despite fully valid configuration” “Custom domain 404 after moving to a new project via API” The matching pattern is: Deployment is Ready Hashed deployment URL works or reaches Deployment Protection Canonical .vercel.app and/or custom aliases return platform NOT_FOUND Alias metadata corre
system 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. vercel.com/docs/domains/troubleshooting
Offdutythoughts We have already tried all of the possible changes. We are able to verify A records and CNAME, are just missing TXT verification for the domain to work. What we have done so far is verifying the TXT record _vercel.vetic.co.site, which is publicly resolvable and returns with an expected verification value. Additionally, we checked the registry status of the domain and confirmed that it is not under serverHold or clientHold. We kindly request if you could verify the following: Re-run the domain verification for vetic.co.site. Refresh any cached verification state for the domain. Verify that their
system 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. vercel.com/docs/domains/troubleshooting
Starberryza This did not help
system 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. vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
Amy Egan is-a.dev is a recognized public suffix. You just need to add the requested TXT record to verify the domain. community.vercel.com/t/is-a-dev-domain-issue/923/18?u=amyegan