⌘K
Amy Egan First, I want to make sure you're getting the help you need. Do you have a support ticket yet? If not, you can open one at vercel.com/help Appreciate you sharing feedback about your experience. It sounds like there's still some room for improvement here, but I just want to clarify a couple of things to help it make more sense > These emails were receipts issued after the charges had already been incurred. They were not advance spending alerts that gave me an opportunity to prevent the charges. Receiving a partial invoice earlier than your normal billing cycle is actually part of the early warning system to help you avoid runaway usage. There's not really a way to predict the future and warn _before_ usage is incurred, so the next best thing is to let people know when a usage pattern has gotten unusual before a metric gets wildly high. The system recognizes the unusual usage pattern and sends a notification with an invoice for only the amount that's already been used. At that point, you can change build machine settings, manually pause projects, or do whatever is needed to keep usage in budget. > I did not receive an advance Spend, Usage, Budget, Threshold, or unusual-usage email alert before the charges accumulated. In particular, I did not receive an advance email warning between the first receipt and the additional USD 300.83 charge five days later. You should definitely have received an alert 50%, 75%, and 100% of your set budget ($200 by default) unless you've disabled notifications, so I'm going to flag this with the team to figure out what went wrong. A bug in the alert system would be a high priority issue. If you let me know your case number, I can make sure the engineering team knows about it.
airstairjp Hi Amy, Thanks for the quick and helpful reply. I've opened a support case: CSE_019cTeCgidqFnPaM I haven't knowingly turned off any notifications, so I'd really appreciate it if you could flag it to the engineering team to check why no budget alerts were sent. I also asked in the case for the refund request to go to a Billing specialist for manual review. Thanks again!
Mathieucrcs You're clearly not the only ones... https://community.vercel.com/t/unexpected-build-cpu-charges-without-advance-spending-alerts/50206#post_1
airstairjp I’m the author of the related post linked above. My Build CPU charges also spiked in September: USD 0.58 in May, USD 28.66 in June, USD 1.93 in July, USD 8.19 in August, and USD 402.18 in September (before credits). I haven’t established that unwanted branch builds caused my charges, but I also received no advance warning before they accumulated. I hope Vercel reviews the builds you tried to prevent and gives both cases a path to manual billing review.
Pixelfoundry yeah, we are using vercel since 2023.... once upon a time the story was different.... and we tried to disable the automatic builds, then it kicked back in again... this is very frustrating
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.
Truenone This isn't a security vulnerability report. It's a request to review and unpause my Hobby project, which was paused due to a one-day usage spike from unwanted traffic. Could someone from the support team take a look? Thanks.
Amy Egan Hey, James. Appreciate you reaching out about this. The team shipped an update yesterday so your dashboard now reflects each day's deployment storage amount instead of the billing period maximum. I'm linking some Deployment Storage optimization tips in case you still need help reducing the amount of storage used https://vercel.com/docs/deployment-storage/optimize
James Singleton Hi Amy. Yea after doing some Googling I was able to find stuff about it. It's a little concerning that this was pushed out without an email letting users know. All of a sudden I was getting emails saying that I was using 40 GB of the 10 GB of deployment storage with a single deployment taking up like 30 GB. I started to panic! One issue I ran into is that retention policies were defaulted to 30 days for everything. Even after setting some to 1 week and in some cases 1 day, I wasn't seeing deployments being removed. I had to go through and manually delete deployments. I basically had to delete all by 6 deployments for my major project with 5 of those being production deploys and one being a preview. I am down to 11 GB now out of 10... I was below 10 earlier today but then opening a PR to a repo pushed me up to 11 GB. So I have gone through and done what the docs say to do, yet it seemed that Vercel was not going and removing the old deploys after I saved the changes, even days after updating.
James Singleton To add to this, there are projects where the retention is 30 days and I have deployments from January still in my Deployments tab. This project was defaulted to 30 days and I have deployments from Jan-May still there.
Swarnava Sengupta The deployment storage resets every 30 days, at the start of the next period. This means your new usage will not be reflected immediately.
Amy Egan Update: The team shipped an update yesterday so your dashboard now reflects each day's deployment storage amount more quickly. If you still see high storage use at this point, there are some optimization steps that can make a big difference. Linking those below. https://vercel.com/docs/deployment-storage/optimize
Swarnava Sengupta The deployment storage resets every 30 days, at the start of the next period. This means your new usage will not be reflected immediately.
Amy Egan The team shipped an update yesterday so your dashboard now reflects each day's deployment storage amount more quickly. If you still need help reducing the amount of storage used, there are some optimization steps that can make a big difference. Linking those below. https://vercel.com/docs/deployment-storage/optimize
