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
Suheb This looks like a useful approach, especially keeping the QR generation fully client-side. Using Next.js 16 should also make it easier to keep the toolkit fast and lightweight. The focus on privacy is a nice touch since users don't need to upload their QR data to a server.
Kris Dev Thanks! That was exactly the goal. I wanted the core QR workflow to stay fully client-side so users can generate, style, and export their QR codes without sending the payload to a backend. It also keeps the architecture simple and lightweight, which fits well with the kind of utility I want QR Forge to be. Appreciate the feedback!
Swarnava Sengupta You need to wait 30 days to free up the storage until the next billing cycle. The storage won't free up immediately.
Goldsh69 I understand the 30-day rolling window, but since I have already deleted previous deployments, my current active usage is under 1 GB while the system retains ~10 GB of orphaned storage. Because of this, my account is completely blocked from new deployments. Since creating a workaround like migrating to a new account shouldn't be necessary, could you please manually purge the orphaned cache for this team?
system Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: 1. Go to vercel.com/login 2. Choose to sign in using the email + one-time password (OTP) option. 3. Select Use another sign-in method 4. Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account 5. Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yourself. You can also use recovery codes if you've stored those in a safe place that you can still access. If you are unable to access your account using the steps above, you can open a support case using the Start 2FA recovery option on the Two-Factor Authentication login screen. **Please do not publicly post account details, like your email address, that could help an attacker gain access to your account in the future.** There's no need to open an additional case if you already have one open. Thanks for your patience while the team works to resolve all cases as quickly as possible while keeping everyone’s accounts safe and secure. A human should be here soon to help.
Yscqx Update (August 3, 2026): The restriction is still active and the dashboard continues to say that the team has been flagged for abuse. Since the original post, I have: * retried the official blocked-account recovery form in both signed-in and signed-out sessions; * tried the alternative “Access a business account, team, or project” recovery path; * attempted to create a case through the signed-in Support Center; and * emailed the legacy registration address. Both recovery paths still return “We had an issue processing your appeal. Try again later.” The signed-in support request was also denied, and registration@vercel.com immediately replied that the inbox is no longer monitored and pointed back to the same failing recovery form. The affected AI Gateway credential is still shown as Active with 0 requests and $0 spend, so there is still no visible abusive usage to identify or remediate. I have also sent the details privately to the Vercel staff contact provided in the related form-defect thread. Could a human Vercel staff member please help create or escalate a case to Account Recovery / Trust & Safety? I can provide the verified account email, ownership evidence, credential ID, and any payment verification privately. I am intentionally not posting those details publicly. Thank you.
Yscqx Update — September 21, 2026 @amyegan @oynickj Could a Vercel staff member please help check the submission problem reported in this existing thread, or point me to a working private support channel? Today I completed the required fields in the dashboard-linked Account Recovery and Appeals form and submitted twice. Both attempts returned: “We had an issue processing your appeal. Try again later.” Neither produced a success confirmation or a case number. I also used the general recovery form's “Other” option to transparently report the broken submission workflow, explicitly identifying the underlying team restriction. That technical-failure report returned the same error. The dashboard continues to direct me to the appeal form, while the signed-in Support assistant says it cannot register or escalate an appeal. Could a human please clarify whether the form failure is a technical issue and how I can receive an authoritative response through a working private channel? I have an existing related support case and can provide its reference and any necessary account verification privately. I can still sign in; this is not a login or 2FA recovery request. Thank you.
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
Newthiery 5459 Additional evidence: - The deployment works immediately when I use WARP/VPN. - The same issue occurs from both my PC and phone on the normal MTN Rwanda connection. - vercel.com itself is reachable from the same MTN connection. - Traceroutes to the affected Vercel edge IPs reach MTN/upstream network hops and then time out. - Direct HTTPS testing times out before TLS on the newer edge IPs. - The legacy Vercel IPs 76.76.21.21 and 66.33.60.130 successfully return HTTP 200 for the same deployment. This appears to be a network routing / Anycast / BGP / peering issue affecting connectivity from MTN Rwanda (AS36890) to Vercel's newer edge ranges. Could someone from Vercel Network/Infrastructure investigate the connectivity from AS36890 to 64.29.17.0/24 and 216.198.79.0/24? I can provide the full Vercel Network Debug output and traceroutes if required.
Mattoney93 7295 I’m seeing the same failure from T-Mobile 5G Business Internet in the United States. Affected deployment: https://five-circa-dashboard.vercel.app/ Evidence from the affected connection: - DNS resolves normally to Vercel edge addresses in 64.29.17.0/24 and 216.198.79.0/24. - TCP/443 fails before TLS. curl reports connection failure and the browser reports ERR_ADDRESS_UNREACHABLE. - ping and traceroute to 64.29.17.3 return ‘No route to host’ immediately. - An unrelated vercel.app deployment and vercel.com are also unreachable from the same connection. - Google and other non-Vercel destinations remain reachable. - The deployment loads immediately after switching the same Mac to a phone hotspot. This appears to be an outbound routing/peering issue between T-Mobile Business Internet and Vercel’s newer 64.29.17.0/24 and 216.198.79.0/24 edge ranges, rather than a deployment or DNS problem. Could Vercel Network/Infrastructure investigate and coordinate with T-Mobile? I can provide further traceroute or network-debug output if useful.
PIM S.A. Update, September 20. Support replied on September 17 and pointed to an activity-log entry dated April 1, 2026: "updated team default build machine from Standard to Turbo", attributed to my account. I did not make that change myself; at that time an employee was using an AI coding agent with access to my Vercel token, and the setting can be changed through the REST API with an owner token. I have asked support for the timestamp, channel (API, CLI or dashboard) and IP of that event, and I have corrected my request accordingly: this is not a "Turbo default" case, it is a team-level setting with a 7.5x cost impact that was changed by a token without any confirmation or notification to the owners, and then discovered five months later on a $1,883 invoice line. No reply from support since September 17. The request remains a re-rating at Standard pricing (about $1,630). Case #01BTdgkqgjXDKcBG.
Swarnava Sengupta Our team will revert to you via support ticket.
Shawn Wu ridiculous
Amy Egan Hi Shawn. This is a community forum. As such, the vast majority of people here do not have any ability to issue a refund. In many cases you can get an instant refund by visiting vercel.com/help and asking for a refund in the support chat. You can also ask the agent for help understanding why you saw those error codes and open a support case if needed.
Mogifiedmoments 9653 I'm experiencing the same type of Deployment Storage discrepancy on the Hobby plan. My project is mogified-moments. Usage Overview shows 11.88 GB / 10 GB Deployment Storage. I deleted the old deployments, leaving only my current production deployment. The deleted deployments are now under Recently Deleted. However, Deployment Storage → Projects has already dropped to approximately 4.8 GB, while the main Usage Overview still shows 11.88 GB. Could you please check whether the Deployment Storage usage on my team needs to be reconciled/purged? I have screenshots showing both values.
Swarnava Sengupta Have you considered counting all the previous deployment for same project?
Mogifiedmoments 9653 i deleted all previous deployments
Amy Egan The support agent can help
https://community.vercel.com/t/what-to-do-when-your-team-is-paused-or-blocked/45069
Axismedbydaxis Mam i tried that but the agent replied that it cant unblock the project. Can you please help me with this. For last 2 months my traffic was very less than the mentioned limit.