Vercel Billing Overview bug?

(edited)

Hi, I have some doubts about the current billing cycle.

On one hand it seems that Blob usage is having on-demand usage but not incurring in charges, on the other it seems Edge Requests haven't reach the limit included yet but it's already generating additional charges. I know that for Simple Operations you are getting charged $0.40 per additional 1M, but for Data Transfer is $0.05 per additional 1 GB so it should appear in the the charges, right?

Also I wanted to ask something related to files caching. Is this % cached a normal thing? This images are in my home page so they are consuming making many Edge Requests

Vercel Staff

Looking at your billing overview, there are a few things that could explain what you’re seeing:

For Blob usage showing 0 charges despite on-demand usage:
- You might still be within the free tier limits for Blob storage
- Some Blob operations (like reads) have generous free allowances
- The charges might be very small and rounded down in the display
For Edge Requests showing charges before hitting the limit:
- Edge Requests and Edge Functions are billed separately
- You might be seeing charges for Edge Functions executions, not just requests
- Different request types (static vs dynamic) have different billing structures

To get a clearer picture, I’d recommend:

Check your detailed usage breakdown in the Dashboard
Look at the specific metrics for each service
Verify the exact limits for your plan

If the billing still looks wrong after reviewing these details, please contact Vercel support directly via vercel.com/help with your specific usage numbers.

Hi, I don't really get what you mean by this:

Edge Requests and Edge Functions are billed separately
You might be seeing charges for Edge Functions executions, not just requests
Different request types (static vs dynamic) have different billing structures

As all I'm mainly consuming are Edge Requests.

My PRO Plan includes 10M requests and after that each 1M is $2.00, but as you can see I haven't even reached the 10M limit and the charge is already at $3.58

Vercel Staff

You may see slightly different numbers depending on which date range or billing cycle you have selected. But I'm reaching out to the team to investigate this, since it seems like a possible UI bug

Vercel Staff

Thanks for reporting this! It was a timezone issue in the UI. The team have a solution.

While this should no longer be an issue for you, please keep an eye on your metrics for the current billing cycle and let us know if anything still looks wrong. And be sure to set up spend limits if you want alerts or restrictions for on-demand usage

Yea, I have seen that in the invoice the quantity of Edge Requests were 12.151.002 in total, so the charges made sense. But I hope this is fixed for the current billing cycle, because if there aren't any extra charges, the only way you have to know about your usage it's checking the display.

Also, what happened with the Usage Overview? It's only showing this now and I have everything selected:

This topic is closed. It no longer accepts new replies.

Looking at your billing overview, there are a few things that could explain what you’re seeing:

For Blob usage showing 0 charges despite on-demand usage:
- You might still be within the free tier limits for Blob storage
- Some Blob operations (like reads) have generous free allowances
- The charges might be very small and rounded down in the display
For Edge Requests showing charges before hitting the limit:
- Edge Requests and Edge Functions are billed separately
- You might be seeing charges for Edge Functions executions, not just requests
- Different request types (static vs dynamic) have different billing structures

To get a clearer picture, I’d recommend:

Check your detailed usage breakdown in the Dashboard
Look at the specific metrics for each service
Verify the exact limits for your plan

If the billing still looks wrong after reviewing these details, please contact Vercel support directly via vercel.com/help with your specific usage numbers.