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.

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

Muthumohammed810 5526 Hello Vercel Team, I am facing an issue while trying to upgrade my existing Production Blob Store to OIDC. Whenever I click the "Upgrade to OIDC" option, I immediately receive the error: "An unexpected internal error occurred" I have already refreshed the page and tried again, but the issue persists. My live website is currently working with the existing Blob read-write token authentication. Could you please investigate this issue and guide me on how to safely enable OIDC without affecting my live website or existing Blob data? Thank you for your help.

starrdev Issue is resolved. Disregard

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 If you're having trouble deploying an Express app, this guide can help. vercel.com/guides/using-express-with-vercel You can also ask v0 for suggestions tailored to your own project setup.

Group-IB DRP Dear Vercel Support, Can we get your urgent assistance for the reported phishing on: alert-me.vercel.app Your urgent support is highly appreciated.

Group-IB DRP @anshumanb @pawlean can you please support in this report. We have submitted multiple reports on the abuse form.

Anshuman Bhardwaj Hi Julian, if I understand it correctly, your GitHub account was made with an Apple Private Relay email? But, you no longer have access to that email to login. If your GitHub is linked with another account and you want to relink it to this one, you can remove it from the Authentication Settings in the 1st account and then connect it to this one (given you can log into both of them).

Julian B I have access to the Apple Private relay email, the issue is that once I re-connected Github to another vercel made account. It disconnected the authenticated account that i originally made, so when I went to reauthenticate via the Github option. Vercel wants to verify via a code which sends to that Apple Private Relay email. Apple requires 'Sign in with Apple' apps to be given permission upon registering to become approved. Then you are able to forward emails to another account, for example. Incoming Apple Private Relay Email (Vercel Confirmation code) - Forward to - another personal email So

Julian B I also think that when my Vercel account was created via the Github option. It obviously registers the email address with Vercel, so Vercel is expecting that email to be able to login. If i change it on the Github side, It just causes more problems and disconnects the ability to receive any email whatsoever to authenticate the login.

Anshuman Bhardwaj Hi there, we're sorry, but there's no way to find the historical value of an environment variable.

8008makoto 9443 I am seeing the same error on my Ortus Lab Hobby team as of 4 October 2026. A single connection-only request to POST /v1/evaluate, using typesafe-ai/jev with providerOptions.gateway.only = ["typesafe-ai"], returned HTTP 403 / no_providers_available. No retries were made. Gateway generation: gen_01M42Z5VSGVE2NZHP2PFH7B9JS Request ID: kix1::cle1::xxhnt-1791101169365-b47ac4afa936 Timestamp: 2026-10-04 08:06:09.456 UTC The authenticated dashboard shows provider allowlist, model allowlist and ZDR disabled. The request log shows TypeSafe AI / Jev and no reported usage. Provider reachability and the

Gabi Norrman Hi Vercel team, I'm experiencing the same issue with typesafe-ai/jev-1.14.0 on my Hobby team. POST /v1/evaluate returns HTTP 403. The AI Gateway key is recognised. The model page says the TypeSafe AI provider is unavailable to my team. Zero Data Retention is disabled. The request reaches TypeSafe AI but reports no token usage. AI Gateway Logs confirm $0 charged. Observed on 3 November 2026. Could you confirm whether this is a provider availability, account entitlement or provisioning issue, and whether access can be restored on Hobby? I can provide the Gateway request ID privately if needed. T

Anshuman Bhardwaj Hi everyone, as per our pricing page (vercel.com/ai-gateway/models/jev), you cannot use free credits for Jev models on either TypeSafe or DigitalOcean providers. Let me know if you have another question.

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.

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.