Consumption Breakdown
Usage data can be up to 1 hour old.
Agent may make mistakes. Verify all outputs.
Usage data can be up to 1 hour old.
Agent may make mistakes. Verify all outputs.
The amount of data that your Deployments have received or sent. Learn More
The number of requests your Deployments have received. Learn More
The data transfer between Vercel's CDN and your sites' end users. Learn More
The data transfer between Vercel's CDN to Vercel Compute. Learn More
The number of cached and uncached requests that your deployments have received. Learn More
The number of Read Units used to access ISR data. Learn More
The number of read units to the Vercel Data Cache. Learn More
The number of times your Vercel Functions received a request (does not include Cache Hits). Learn More
The number of times your Edge Functions received requests. Included in Compute Infrastructure: Function Invocations. Learn More
The number of times your Edge Middleware received a request. Learn More
The amount of time that your Deployments have spent being queued or building. Learn More
The time saved by using local or remote cached artifacts. Learn More
The amount of storage used by deployments. Learn More
The volume of logs and events generated by your projects. Learn More
The number of times your team applied flag overrides. Learn More
The number of Span Units used by Vercel Tracing. Learn More
The number of checkBotId() calls that ran Deep Analysis. Basic validation and requests that do not call checkBotId() are not charged. Learn More
The number of Write Units used to store new ISR data. Learn More
The number of write units to the Vercel Data Cache. Learn More
The total execution time of your Vercel Functions not running on Fluid. Learn More
The number of times that a request to your Vercel Functions could not be served because the concurrency limit was hit. Learn More
The total provisioned memory duration of your Vercel Functions running on Fluid. Learn More
The total CPU time of your Vercel Functions running on Fluid. Learn More
Billing units for Edge Functions: blocks of 50ms of CPU time. Learn More
The average time your Edge Functions have spent computing responses to requests. Learn More
The average time your Edge Middleware has spent computing responses to requests. Learn More
How many times a build was issued for one of your Deployments. Learn More
The number of build slots consumed by on-demand builds. Learn More
The number of billable build minutes consumed. Learn More
The number of build CPU minutes consumed. Learn More
The number of downloaded and uploaded artifacts. Learn More
The total size of all successfully downloaded and uploaded artifacts. Learn More
The amount of storage used by Vercel Functions of your deployments. Learn More
The number of AI Gateway trace events delivered to your drains. Learn More
The number of times your Edge Functions received requests. Included in Compute Infrastructure: Function Invocations. Learn More
Something went wrong
We couldn’t load the data for your selection
Billing units for Edge Functions: blocks of 50ms of CPU time. Learn More
Something went wrong
We couldn’t load the data for your selection
The average time your Edge Functions have spent computing responses to requests. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of times your Edge Middleware received a request. Learn More
Something went wrong
We couldn’t load the data for your selection
The average time your Edge Middleware has spent computing responses to requests. Learn More
Something went wrong
We couldn’t load the data for your selection
The time saved by using local or remote cached artifacts. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of downloaded and uploaded artifacts. Learn More
Something went wrong
We couldn’t load the data for your selection
The total size of all successfully downloaded and uploaded artifacts. Learn More
Something went wrong
We couldn’t load the data for your selection
The amount of time that your Deployments have spent being queued or building. Learn More
Something went wrong
We couldn’t load the data for your selection
How many times a build was issued for one of your Deployments. Learn More
Something went wrong
We couldn’t load the data for your selection
The amount of data that your Deployments have received or sent. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of requests your Deployments have received. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of times that a request to your Vercel Functions could not be served because the concurrency limit was hit. Learn More
Something went wrong
We couldn’t load the data for your selection
The amount of storage used by deployments. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of Read Units used to access ISR data. Learn More
Something went wrong
We couldn’t load the data for your selection
The volume of logs and events generated by your projects. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of times your team applied flag overrides. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of Span Units used by Vercel Tracing. Learn More
Something went wrong
We couldn’t load the data for your selection
The total execution time of your Vercel Functions not running on Fluid. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of billable build minutes consumed. Learn More
Something went wrong
We couldn’t load the data for your selection
The amount of storage used by Vercel Functions of your deployments. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of AI Gateway trace events delivered to your drains. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of read units to the Vercel Data Cache. Learn More
Something went wrong
We couldn’t load the data for your selection
The data transfer between Vercel's CDN to Vercel Compute. Learn More
Something went wrong
We couldn’t load the data for your selection
Something went wrong
We couldn’t load the data for your selection
The number of times your Vercel Functions received a request (does not include Cache Hits). Learn More
Something went wrong
We couldn’t load the data for your selection
The number of Write Units used to store new ISR data. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of cached and uncached requests that your deployments have received. Learn More
Something went wrong
We couldn’t load the data for your selection
The data transfer between Vercel's CDN and your sites' end users. Learn More
Something went wrong
We couldn’t load the data for your selection
The total CPU time of your Vercel Functions running on Fluid. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of write units to the Vercel Data Cache. Learn More
Something went wrong
We couldn’t load the data for your selection
The total provisioned memory duration of your Vercel Functions running on Fluid. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of build slots consumed by on-demand builds. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of build CPU minutes consumed. Learn More
Something went wrong
We couldn’t load the data for your selection
The number of checkBotId() calls that ran Deep Analysis. Basic validation and requests that do not call checkBotId() are not charged. Learn More
Something went wrong
We couldn’t load the data for your selection