Usage, freshness and corrections

Open Billing → Images to review delivery usage and the allowances included in your active packages. Images access requires an enabled subscription or other explicitly granted access. Usage reporting does not create metered overage charges or automatically upgrade your subscription.

What counts

Authorized GET/HEAD 200, 206 and 304 responses each count as one operation. An authorized missing-variant 404 counts as one operation and zero allowance bytes. Rejected access, 429 and server errors do not consume the allowance. Resolve, batch and polling do not consume either delivery meter, although API traffic limits still apply.

A cached response can still consume delivery allowance: caching avoids preparing or fetching the image again, but the response still reaches a viewer. Transfer usage can differ from the image file size.

Shared allowances and restrictions

Projects belonging to the same Customer share that Customer's Images delivery allowances. Creating another Project or binding does not create another allowance. See Billing for the applicable package, period and accepted policy.

For the asynchronous delivery policy, quota enforcement targets restriction at 110% of either pooled delivery allowance. This is a restriction target, not an exact global cutoff or a guaranteed maximum overshoot. Usage arrives after delivery, so requests may continue while observations and restrictions are processed. Delivery may also be restricted when usage evidence becomes too old or protective limits are reached. Images is not unlimited.

An allowance restriction can be resolved by a qualifying allowance increase, period renewal or reviewed usage correction. Check Billing for the current restriction and available action; repeatedly retrying image URLs does not restore access. Commercial access expiry and protective suspensions are separate from quota restrictions.

Reading report freshness

Reports are refreshed when opened or when you select Refresh usage. This requests the latest available report; it does not make recently delivered traffic appear immediately. Check the report's observed-through time and evidence state. There is no guaranteed five-minute reporting interval.

Confirmed empty usage appears as 0 operations and 0 GB. Missing or incomplete evidence is unavailable or provisional, never assumed to be zero. A report can be ready for the evidence received so far while additional observations are still delayed.

Late observations and reviewed corrections can change a previous period's totals. Reprocessing the same observation does not count it twice. Usage remains associated with the Customer, Project and applicable period at delivery time; a later binding change does not move that history.

See Limits and errors for delivery failures and Caching and browser delivery for integration guidance.