⌘K
Amy Egan Hey @jennie369. It looks like you've been working with a support engineer on your case. Please continue to follow up with them to get this solved 🙏
Jenniec Hi Amy, thanks for checking in. I have been working with the support engineer, but the case isn’t resolved. They closed it with a 25% goodwill refund ($134.64) and said that’s the maximum. $489.52 is still unrefunded. The issue is consent. My projects were explicitly set to fixed Basic/Standard machines, and the system overwrote that choice the minute I upgraded (isSystemInitiated: true, “because your team’s plan changed”). The upgrade screen said nothing about changing build machines or adding on-demand Build CPU charges. On Oct 3 it also auto-upgraded yinyang-web to 8 CPUs without asking. At best, the changelog wording (“default for new Pro teams” vs. “enable in your team settings”) is ambiguous about upgraded teams. An ambiguous term shouldn’t override a setting I chose explicitly. Budget emails that report usage “already incurred” aren’t consent to a machine I never selected. Could someone on the billing side please take another look at case CSE_01RxdvwtOfqTrLfo? I’d like the remaining $489.52 for the unauthorized Elastic overage refunded. Happy to share details privately.
Parsifal Hi Vercel team, just following up on this request. My Blob store is still suspended, and I'm unable to download the existing files due to 403 errors. I'm not asking for additional quota or continued service — I only need temporary read-only access to export my data and migrate it to my own server. Could someone from the team please take a look or suggest an alternative way to retrieve the files? I'd really appreciate your help, as the store contains data I need to preserve. Thanks!
Parsifal Hi Vercel team, following up again as I still haven't received any response. I understand the Hobby plan limits, and I'm not asking for additional quota or continued service. I only need **one-time access to export my existing data** before migrating away from Vercel Blob. The files are still inaccessible due to 403 errors, and I'm concerned about being unable to recover important data. **Could someone from the Vercel team please help escalate this request or provide an alternative way to export the files?** Even a brief update on whether this is possible would be greatly appreciated. Thank you!
Parsifal Hi @jacobparis, sorry to tag you directly. I noticed you helped another user with a similar Blob suspension issue by temporarily unsuspending their store for data export. I'm facing the same situation and have been unable to recover my existing files. I've already fixed the excessive operations and am migrating away from Vercel Blob. Would you be able to help with a one-time temporary unsuspend for data export, or point me to someone who can? I'd really appreciate your help. Thank you!
Juanclases33 5979 Following up: this evidence question is blocking completion of a read-only technical review. Could a Vercel team member or community moderator help route it to someone who can confirm the supported sources and their limits? To make the request actionable, a separate yes/no/source answer for each group would be very helpful: 1. On Hobby, can an owner obtain complete effective project-access counts, distinguishing direct and inherited access, role categories and overlaps, without disclosing member identities? If the distinctions are not applicable on Hobby, please identify the documented rule and its coverage. 2. For an existing deployment at a past time, are the effective Node.js patch, an immutable digest/manifest of the deployed function artifact, and the source/dependencies/build/deployment/environment/time binding available through a supported read-only record or provider attestation? A source commit or configured Node major alone does not resolve these questions. 3. Is there a retained project-level record establishing a historical configured/default function timeout when the UI field is blank and the project response omits the relevant keys? A deployment configuration snapshot is a different object/time scope. If a record is not exposed, not retained, unavailable on Hobby, or cannot be reconstructed retrospectively, an explicit distinction would be equally useful. If another free official channel is appropriate for this capability question, please point us to it. No upgrades, paid support, production invocations, redeployments or configuration changes are requested. This remains a general question: no project/account identifiers, secrets, logs or attachments. Thank you.
Amy Egan Hobby is a single-user plan with some usage limits. The only person on the team effectively takes the owner role You can review team member actions in the Activity Log Vercel rolls out Node.js minor and patch updates automatically, so only the major version is guaranteed. With Fluid compute, Hobby's default and maximum are both 300s For more info, please go to vercel.com/docs and search or use the Ask AI button
Juanclases33 5979 Thanks, Amy. Your answer clarifies the single-user/Owner model and the automatic Node.js updates. I checked the linked documentation; the remaining questions are narrower: 1. **Hobby access classification.** For a single-user Hobby project, are project-direct, inherited and overlap membership categories applicable? Is the Owner classified as inherited access without a direct project assignment, or should those categories be recorded as not applicable? I do not want to invent zero counts from the absence of a project-role UI. 2. **Historical Node.js patch.** I understand that only the major version is selectable/guaranteed. Separately, does Vercel retain a record of the exact runtime minor/patch used by an existing deployment at a specified past time/region? If available, what supported read-only source exposes it? A new invocation or build would not establish the historical state. 3. **Deployed output and provenance.** Is an immutable digest/manifest of the installed function output available, with a binding to source commit, resolved dependencies, build, deployment, environment and time? A source-file tree or Git SHA alone does not identify the deployed output. If there is no supported customer-facing record, can the team confirm whether a provider attestation is possible? 4. **Historical non-Fluid timeout.** The 300s answer is explicitly for Fluid Compute. For a legacy Hobby project with Fluid disabled, what did a blank project Max Duration field with placeholder 10 mean on 11 October 2026? The Activity Log catalog lists project-function-max-duration and project-functions-fluid-enabled/disabled. Do their retained records include old/new values and enough history to establish that earlier project setting/default, and what are the retention and read-only access limits? A later deployment's duration is a separate observation. For unavailable records, please distinguish "not exposed to customers", "not retained", and "not reconstructible retrospectively". A short answer or the appropriate free technical channel is enough. No account identifiers, private records, changes, redeployments or paid services are requested. Thank you.
Amy Egan Hey @tomrowbo Do you have a support case open? Unfortunately, the community can't issue refunds. That kind of thing is limited to the support team. If you don't have a case yet, please open one at vercel.com/help so the support team can lend a hand.
Amy Egan Just be sure to tell the chat agent that you want to open a support case. That way it'll give you a form to open a case instead of trying to issue a refund on its own if you ran into trouble with that option already
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.
Cristovão A. da S. Neto We have already used vercel.com/abuse many times, and that is exactly why we are posting here. We ask that a member of the Vercel staff review the cases concerning berzerkclub[.]com[.]br and berzerkclub[.]com directly, or escalate them internally to Trust & Safety. Both domains serve the same deployment. Reports already filed through the official channel for this same deployment: - Sep 28, 2026: phishing report for berzerkclub[.]com[.]br, case 01586466 - Oct 2, 2026: phishing and brand impersonation report for berzerkclub[.]com[.]br, case 01597477 - Oct 8, 2026: DMCA notice for berzerkclub[.]com[.]br and berzerkclub[.]com, case th_01M4EMXMTE7NJ6JRJZE8TCVSFJ (receipt TNS_01vuyQQMecjVnJWO) - Oct 9, 2026: phishing report for berzerkclub[.]com We cannot file again: Vercel's own acknowledgment warns that repeated reports about the same URL may lead to the reporter being flagged as spam. The official channel has been used four times in thirty days, the block announced on October 10 was not applied, and the store remains online. All evidence has already been sent to Vercel several times through the official channel and can be resubmitted to whichever staff member takes over. We have used every channel available to us and need urgent action. At this point, Vercel's continued inaction is allowing the fraud to keep running on its infrastructure. Cristovão Amaro da Silva Neto Attorney at Law, OAB/PB 32.269 and OAB/SP 551.843 On behalf of Berzerk Indústria e Comércio Ltda.
Fred That is documented behavior. The first deployment of a new project always counts as production, even if you ask for preview, and it builds with your Production env vars. A failed first deployment still counts as the first one, so your next deploy with the preview target should come out as a real Preview, unless you deleted that deployment. If you want the first build to pass, add the same variables to Production too.
Amy Egan `--skip-domain` lets you create a placeholder production deployment without assigning the domain. I shared more info about that in community.vercel.com/t/vercel-cli-ignores-target-preview-and-creates-production-deployment/46384#post_10 Or you can set Deployment Protection to All Deployments if you want to restrict public access
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. https://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 If the Output doesn't have an index, that explains the 404. Now we need to figure out why the output doesn't match what you expected. Do you have a public repo or minimal reproducible example that you can share so we can help debug? Or a description of the project settings and framework used? The tips linked above can help if you prefer to DIY
