Observed usage is not a live request log
A provider snapshot reports what that source observed for an allocation at a time. It may arrive late or omit request-level detail. Missing usage is unknown, not zero. Do not infer request count, geography, latency or inbound/outbound bytes from a single aggregate.
Units and periods matter
Bytes, decimal GB, binary GiB, requests, sessions and IP-months are not interchangeable. Compare the declared unit and billing period. Calendar-month supplier thresholds may differ from a customer billing cycle. A reset or allocation change is not negative consumption.
Confirm commercial limits
Read included usage, overage price, tax, currency, concurrency and cutoff behavior in the confirmed offer and native checkout. The current public catalog carries native prices and readiness but not a complete per-customer allowance contract. No public calculator here invents those missing fields.
Estimate from a controlled pilot
Measure your application’s permitted workload including failures, retries and response assets. Add a documented safety margin rather than treating one successful small request as a monthly forecast. A spending estimate is not an enforced budget cap; confirm technical stopping behavior separately.