⌘K
NextBlock™ CMS Just submitted our application for **NextBlock CMS**! 🚀 NextBlock is an open-source, full-stack CMS framework built natively for **Next.js 16 (App Router + RSC)** and **Supabase (PostgreSQL JSONB)**. We’ve focused on: * **Zero-Config 1-Click Deploy:** Automated Supabase database migrations on build. * **100/100 Lighthouse Defaults:** Tiptap visual editor renders PostgreSQL JSONB directly into React Server Components, eliminating client hydration overhead and HTML sanitization taxes. * **Cortex AI & Native MCP:** Model Context Protocol server support (`/api/mcp`) for deterministic, schema-constrained block synthesis. * **GitHub:** https://github.com/nextblock-cms/nextblock * **Live Sandbox:** https://cms.nextblock.dev Looking forward to the review process and collaborating with the Vercel DX team! 🧱
Axyl1410 Hi! I applied for the Summer 2026 Vercel OSS Program, but I’m not sure whether my application was successfully submitted. I also didn’t receive a confirmation email. Is there any way for applicants to verify whether their application was received, or is there normally no confirmation email after submitting the form? I’d like to avoid submitting a duplicate application if my original submission went through. Thanks!
Amy Egan If you reached the final page that says, "Thank you," then your application was received :) You'll get an email about a week after applications close letting your know whether or not your project was accepted
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. https://vercel.com/docs/domains/troubleshooting
disabled-acc @system i don't have access
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. https://vercel.com/docs/domains/troubleshooting
Grumpyice **Hi Vercel team, just following up on this issue.** I’m still unable to verify **ijedelcda.lg.gov.ng**, and Vercel continues to show **“This domain is linked to another Vercel account.”** The requested TXT verification record has already been added to the domain’s DNS through Go54, but the status remains **Verification Required**. Could someone please advise whether the domain association needs to be released or verified on Vercel’s side? I’d appreciate any guidance. Thank you
Flowfeed Same issue here
Flowfeed For anyone else experiencing this issue: submit a support case. I submitted a support case, and the issue has been resolved. Below is the response from the Vercel support team: ``` We apologize for any inconvenience. Access to Claude Opus 5 and Claude Fable 5 may be temporarily limited for some accounts as part of safeguards that protect service reliability. When this happens, requests return a 429 response. Your account has been verified, and the rate limit should be lifted. Please try again and feel free to let us know if you have any questions! ```
David same here on team aib-ois, been like this since the 26th. maybe 1 in 15 calls gets thru, the rest come back 429 high demand with providerAttemptCount 0 so it never even touches the provider. our rate is tiny, about 1 call a minute. bought credits today thinking the free tier was the issue, nope, paid tier does the exact same thing. the support bot said the gateway health check has typesafe marked unhealthy so it just fast fails everything, but the endpoints api shows 100 percent uptime so somthing doesnt add up. hobby plan cant open a case so posting here instead. one of todays rejected ids if it helps, gen_01M3JF68E219411054WMFD52GH. is this per team or is everyone cooked rn
Pulec Same here. Team on Hobby with paid AI Gateway credits (bought 28 Sep 2026), typesafe-ai/jev via /typesafe/v1/systemone. I measured exactly one accepted call roughly every 300 s; every call in between returns 429 "upstream provider is currently experiencing high demand", regardless of payload size. It has been consistent all day (Sydney time). It would be great to hear from Vercel whether this is per-team throttling, what the limit is, and whether Pro changes it.
Borysuslik 4009 We are seeing the same issue on a Hobby team with purchased AI Gateway credits. Other models work with the same key, but a minimal typesafe-ai/jev request returns HTTP 429 with totalProviderAttemptCount: 0. Pinning providerOptions.gateway.only to ["typesafe-ai"] also returned 429. Minimal reproduction: POST https://ai-gateway.vercel.sh/v1/evaluate {"model":"typesafe-ai/jev","state":"The circle is red.","questions":{"red":{"type":"boolean","instructions":"Is the circle red?"}}} Error: "The upstream provider is currently experiencing high demand. Please retry shortly." Vercel's support assistant prepared a case, but the case form says Hobby accounts must use the community for AI Gateway support, so we are adding this report here. Could Vercel staff clarify whether this is a known Jev routing or provider-health issue, a paid-tier activation issue, or a documented per-team restriction? What action is needed to restore access? We can provide a generation ID privately to staff for investigation.
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0
Andre 1912 Bump! this is currently blocking my testing to choose a way forward for production
Steven Noxious Same issue here on a Hobby team. I reproduced it independently and isolated the failure to Jev / Evaluation API. Working on the same team and API key: - GET /v1/models → HTTP 200 - GET /v1/credits → balance $5 - POST /v1/chat/completions with openai/gpt-4.1-nano → HTTP 200 and billed successfully - typesafe-ai/jev is present in the model catalog Failing: - POST /v1/evaluate, model typesafe-ai/jev → HTTP 403 - POST /typesafe/v1/systemone, model jev-latest → HTTP 403 I also verified: - Provider Allowlist is disabled - Zero Data Retention is disabled - vercel ai-gateway rules ls returns No routing rules found Both failures reproduce with direct PowerShell HTTP requests, without SDK/application code. This therefore appears to be a Jev / Evaluation API entitlement or provisioning issue on Hobby teams rather than an authentication, billing, routing-rule, or application problem. Could Vercel staff check the Jev/Evaluation entitlement for affected Hobby teams?
Stickmedia007 8373 Hi, I'm experiencing the same issue and have carried out some additional troubleshooting that may help narrow it down. My setup is Windows PowerShell with Vercel CLI 60.1.3. I've confirmed the following: - Jev (`typesafe-ai/jev`) appears in the Gateway model catalogue. - My API key successfully authenticates against `/v1/credits`. - My account has $5 available credit and an active payment method. - A standard request using `openai/gpt-4o-mini` succeeds with the same API key. - Requests to `/v1/evaluate` using Jev consistently return HTTP 403, with no additional error details. - One subsequent retry returned HTTP 429. Given that standard AI Gateway requests work correctly, and another user has reproduced the same Jev issue with a freshly generated API key, this appears potentially related to Jev-specific access, Evaluation API provisioning, or a service-side issue. Could Vercel confirm whether this is a known issue or whether additional permissions are required for the Evaluation API? Thanks!
Samssharma 7158 Hi - I don’t think this thread is getting much traction, so I’m going to escalate it on Twitter and other forums. I’d suggest you do the same. Also, don’t forget to add your comments to this post. The creator of the post is Amy from Vercel. https://community.vercel.com/t/build-for-meta-vr-devices-the-way-you-already-build-for-the-web/49685#post_5
Colwalkurtz 7852 I believe your decision to remove direct code editing in v0 is extremely short-sighted and blatantly profit-driven. To update simple details on a page, I now have to go through the chat and consume credits, unless I rely on external tools like GitHub or VS Code. This does not keep users within v0; it pushes them to become independent of it. What was the rationale behind this? Until now, I used v0 with great satisfaction and willingly spent a significant amount because the service was excellent. Forcing me out of the v0 environment makes my workflow far more cumbersome, which will only lead to frustration and drive me away. At that point, using GitHub alongside any other AI tool, I can easily make changes on my own. In the end, I believe this change will decrease your revenue rather than increase it. Please reconsider this step and let us work inside v0 as we did before. Thank you for your time and attention.
Greguarr v0 without manual, basic code editing and without file management has become useless and forces conscious users to look for an alternative and escape from the platform. sad
Vizkiel Come on, man. I’ve already got a million things going on with the website, and I was seriously considering buying domains for several of my sites because I thought Vercel was actually gonna be useful. And then I find out you guys disabled manual code editing? Like, seriously, who thought that was a good idea? Whoever came up with that decision deserves a fuc*ing promotion… somewhere else. Because there’s no way this was the best idea anyone in the room had.
Colwalkurtz 7852 I believe your decision to remove direct code editing in v0 is extremely short-sighted and blatantly profit-driven. To update simple details on a page, I now have to go through the chat and consume credits, unless I rely on external tools like GitHub or VS Code. This does not keep users within v0; it pushes them to become independent of it. What was the rationale behind this? Until now, I used v0 with great satisfaction and willingly spent a significant amount because the service was excellent. Forcing me out of the v0 environment makes my workflow far more cumbersome, which will only lead to frustration and drive me away. At that point, using GitHub alongside any other AI tool, I can easily make changes on my own. In the end, I believe this change will decrease your revenue rather than increase it. Please reconsider this step and let us work inside v0 as we did before. Thank you for your time and attention.
Greguarr v0 Vercel without code/files/folder edit - It's a huge downgrade for this tool - which, up to now, has been getting better and better. I hope this is just a temporary flare-up stemming from some licensing issues regarding the use of VS Code.
