Fededelrincon Fixed! The problem is network reachability between Claro Argentina and part of Vercel's IP range. I tested from Claro (home and mobile) during an outage: 216.198.79.1 and 216.198.79.65 → connection timeout (ports 443 and 80) 64.29.17.1 and 76.76.21.21 → OK (200) My domain uses Vercel DNS, which was returning only the 216.198.79.x addresses, so Claro users couldn't reach the site at all. Workaround: I added manual A records in Vercel DNS (@ and www → 76.76.21.21). Vercel serves those instead of the automatic ones, and once DNS caches expired (~30 min), the site worked again for Claro users with

system Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team. Please submit your report here: vercel.com/abuse Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.

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.

Pasha Thank you for the reference. I checked the suggested article, but I believe our issue is different from a typical deployment or website routing 404. The error occurs when the existing Vercel Connector calls the Vercel REST API: GET api.vercel.com/v2/user Response: 404 / not_found / User not found I have independently verified in the Vercel Dashboard that my account is an Owner of the relevant Team. The issue appears to involve the Connector's authorization principal or identity mapping, rather than a missing website page or deployment route. Could a Vercel Connect engineer or maintainer please

Melbourn74 Dev One addition: if it helps free up storage, please feel free to remove all of our older deployments, including those in Recently Deleted. Please keep only the current production deployment and the latest staging deployment. We don't need to restore or roll back to any older deployments.

system Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team. Please submit your report here: vercel.com/abuse Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.

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.

galb Same request here, from Lookout (lookoutstats.com), a cross-project dashboard for Vercel Web Analytics. We see exactly what you describe: our integration token gets 200 on /v10/projects but 404 "Web Analytics not found." on every /v1/query/web-analytics/visits/* query, and the App permissions editor offers only OpenID scopes. Support also sent us to Community rather than opening a case. We'd like the same two private-beta permissions for our Sign in with Vercel app: Web Analytics: Read Only and Projects: Read Only. Today our users have to paste a personal access token, which is worse for their

Amy Egan You can choose another free *.vercel.app from those currently available or purchase a custom domain if you want more control. Custom domains are available through vercel.com/domains or third-party registrars. Your custom domain can be used with your project either way vercel.com/docs/domains/working-with-domains/add-a-domain

Amy Egan You can use the filter in your Deployments list to find it 😃

Amy Egan You can set a team-wide Deployment Protection default. If you pick All Deployments, every new project is protected from the moment it's created. Without a team default, new projects start on Standard Protection, which covers previews but not production domains. Vercel Authentication, All Deployments, and Protection Bypass for Automation are included on every plan WAF custom rules can match on method, path, hostname, header and more, and can deny or challenge matching requests. Changes go live without a redeploy. But it sounds like Deployment Protection with All Deployments is the better option

Amy Egan Please refer to the documentation for more details. There is an Ask AI feature available to help you vercel.com/docs

Juanclases33 5979 Thanks, Amy. I followed your suggestion: I read the relevant documentation and asked the docs' Ask AI about each unresolved point. Its answers did not identify a documented source that settles the distinctions below. I am not treating an AI answer as an official confirmation of unavailability. Could a Vercel team member answer these six numbered questions, or route the runtime/history questions to the relevant product team? The current single-human Owner role/count is already resolved. 1. Direct versus inherited access on Hobby The Hobby comparison lists RBAC as N/A, and project-level roles ar

Juanclases33 5979 Urgent: final consolidated follow-up — six unresolved evidence questions Hi Amy and Vercel team, I have followed the documentation and Ask AI guidance, as detailed in post 3. Those sources did not settle the six distinctions below. The single-human Owner role/count is already resolved; I am not asking to reopen it. I need a concrete response as soon as possible to finish the affected conclusions of a technical review. Please prioritize a point-by-point answer today if possible. If that is not possible, please identify the responsible team and a specific date for a substantive update, or state