Sources
Data sources and access
A price without provenance is not useful here. The ledger keeps the vendor's figure, unit, source URL, retrieval time and any condition that prevents a clean comparison.
Last materially reviewed
Public access
The current dataset is published without an account or email gate. Human-readable pages link each figure to its source. Read-only machine surfaces include BackupStoragePrices: Api, BackupStoragePrices: Health and BackupStoragePrices: Object storage prices.
The latest endpoint exposes the full current snapshot. The health endpoint exposes data age, not a substitute price. The CSV is a narrower storage-rate export with a rate state, source URL and retrieval time. An unpriced rate is an empty amount paired with not published, never a numeric zero.
What is republished
BackupStoragePrices restates discrete public price figures with attribution, a link to the vendor's page and a retrieval timestamp. It does not republish a whole catalog, marketing copy, artwork or branding as its own.
Manual observation of a current public figure is not treated as blanket permission for automated scraping, caching or historical redistribution. The source record states whether the observation came from an official API, an official machine-readable document or a public page checked manually. Source handling policy reviewed 2026-07-26.
How a figure is attributed
Each price observation names the vendor, product, storage class, region, currency, meter and unit. It also carries the direct public source URL and the time the source was retrieved. The displayed unit remains visible when a conversion is made.
Attribution does not mean the vendor endorses this site or its calculations. A source link lets the reader inspect the vendor's wording, scope and exceptions. If two official pages disagree, the site shows the conflict instead of quietly choosing the more convenient number.
Machine access policy
The published JSON, health and CSV surfaces are read-only. They carry observations and explicit states, not a promise that every vendor exposes every meter. Consumers must treat unknown, stale, conditional, allowance_only, published_non_usd and not published as data, not as zero.
Honor HTTP caching and stop on error responses. Do not bypass access controls or rate limits. No uptime or backwards-compatibility guarantee is offered for bulk integrations; contact the operator before building a dependency that requires one.
Corrections and reuse questions
Send corrections, provenance questions or repeated-access requests to data@backupstorageprices.com. Include the provider, product, region, meter, source URL, observed value and retrieval date so the claim can be checked.
A screenshot without its page URL and observation date is useful as a lead, not as final evidence. The ledger changes only when the corrected value and its scope can be verified.