Price history
What has changed in object storage pricing, and when we saw it
Prices checked
Recorded storage prices
101 saved price checks from 26 July 2026 to 6 November 2026: 2 of 18 vendors' recorded storage prices changed in that time: Hetzner Object Storage, Akamai Cloud Object Storage.
One class and region per vendor: its storage price per GB or GiB a month in each saved check, with any monthly fee and the storage that fee or a free allowance includes. These are dated observations, not current quotes; a gap means no numeric rate was recorded that day.
Follow new changes in a feed reader: RSS feed or JSON feed. Each entry is a change a check recorded, with the old and new price and what keeping 10 TB cost before and after.
Prices that changed
Each date is the day a check first recorded the new price, not the day the vendor changed it.
Hetzner Object Storage
Object Storage · Falkenstein · US dollars a month
- : was $5.99 a month with 1,000 GB included, then $0.00576 per GB; became $7.99 a month at most, billed by the hour, with 1 TB included, then $0.0123 per TB-hour beyond it. Keeping 10 TB went from $57.83 to $87.69 a month (storage only).
Every check and its price
| Checked | Storage price a month |
|---|---|
| $5.99 a month with 1,000 GB included, then $0.00576 per GB | |
| $7.99 a month at most, billed by the hour, with 1 TB included, then $0.0123 per TB-hour beyond it | |
| $7.99 a month at most, billed by the hour, with 1 TB included, then $0.0123 per TB-hour beyond it | |
| $7.99 a month at most, billed by the hour, with 1 TB included, then $0.0123 per TB-hour beyond it | |
| $7.99 a month at most, billed by the hour, with 1 TB included, then $0.0123 per TB-hour beyond it |
Akamai Cloud Object Storage
Object Storage · US East · US dollars a month
- : was $5 a month with 250 GB included, then $0.02 per GB; became $0.02 per GB, no monthly fee. Keeping 10 TB cost $200.00 a month either way.
- : was $0.02 per GB; became $5 a month with 250 GB included, then $0.02 per GB. Keeping 10 TB cost $200.00 a month either way.
The 27 September 2026 check read only Akamai's price table and missed its $5 flat rate with 250 GB included, which Akamai's pricing page still states: Akamai's price did not change. Corrected on 23 October 2026.
Every check and its price
| Checked | Storage price a month |
|---|---|
| $5 a month with 250 GB included, then $0.02 per GB | |
| $5 a month with 250 GB included, then $0.02 per GB | |
| $0.02 per GB | |
| $5 a month with 250 GB included, then $0.02 per GB |
Prices that held
| Vendor | Class and region | Storage price a month | Recorded |
|---|---|---|---|
| Amazon S3 | S3 Standard, US East (N. Virginia) | $0.023 per GB | to |
| Azure Blob Storage | Hot LRS, East US | $0.0208 per GB | to |
| Google Cloud Storage | Standard, South Carolina | $0.02 per GiB | to |
| Cloudflare R2 | Standard, Global | $0.015 per GB | to |
| Backblaze B2 | B2 Cloud Storage, US West | First 10 GB free, then $0.00695 per GB | to |
| Wasabi | Hot Cloud Storage, US East 1 | $0.007803 per GB | to |
| IDrive e2 | IDrive e2, Virginia | $0.006 per GB | to |
| DigitalOcean Spaces | Spaces Standard Storage, New York 3 | $5 a month with 250 GiB included, then $0.02 per GiB | to |
| Scaleway Object Storage | Standard Multi-AZ, Paris | €0.01606 per GB | to |
| OVHcloud Object Storage | Standard 3-AZ, France (Paris) | $0.01571 per GiB | to |
| Vultr Object Storage | Standard, New Jersey | $18 a month with 1,000 GB included, then $0.018 per GB | to |
| Storj | Standard, Globally distributed | $0.007 per GB, at least $5 a month | to |
| Oracle OCI Object Storage | Standard, US East (Ashburn) | First 10 GB free, then $0.0255 per GB | to |
| Tigris | Standard, Global | $0.02 per GiB | to |
| Filebase | Object Storage, Global | $7.50 a month with 500 GiB included, then $0.015 per GiB | to |
| Telnyx Cloud Storage | Regular Storage, US East | First 10 GiB free, then $0.006 per GiB | to |
A dated history of changes to storage, retrieval, request, constraint, and egress rules. Our price history starts on 26 July 2026. Earlier changes are cited from vendor announcements and are never presented as changes we saw ourselves.
Put your own numbers through the calculator to see what this charge does to a normal month and to the month you restore.
Our price history starts on 26 July 2026
We first saved every vendor's prices at 00:35 UTC on 26 July 2026: 61 region-specific offers across 18 vendors. That save is where our price history begins. [1]
A second save at 01:52 UTC, compared against the first, found zero changes across the 12 price details we track. Zero is the number of changes we saw in that interval, not a claim that prices never changed before we began checking. [2]
The Wasabi and Backblaze moves shown below predate our first save. They are included because each vendor published the old value, new value, and effective date. Each rests on the vendor's own announcement rather than on a price we saw ourselves, so there is no first-seen date to state, and we cannot say how they affect a standard-workload winner. [3] [4] [1]
| Where this comes from | Date | What the date proves | What it does not prove | Source |
|---|---|---|---|---|
| Our own saved prices | 2026-07-26T00:35:07Z | We held the prices of all 61 offers at this time | Any value before this time | [1] |
| Our own saved prices | 2026-07-26T01:52:49Z | No tracked price detail changed between the two saves | That no vendor changed prices before our history began | [2] |
| Vendor announcement | 2026-07-01 | Wasabi applied its announced Pay as You Go pricing change on or after this date | That we saw the change happen | [3] |
| Vendor announcement | 2026-05-01 | Backblaze applied its announced B2 price and API changes on this date | That we saw the change happen | [4] |
Twelve price details are checked for every offer
Price history compares 12 billing details on each of the 66 checked offers. These are the details most likely to move a bill, not a claim that a complete bill contains only 12 concepts. [5] [6]
Each dated offer keeps its storage class and region together. AWS, Azure, and Telnyx reuse class names across regions, so dropping the region could overwrite one price with another and hide a real change. [5] [6]
Each detail matters because a bill can change without the headline storage rate moving. An allowance, request schedule, retrieval choice, billing floor, or fixed fee can move the bill and the ranking on its own. [6]
Show the table (12 price details)
| Price detail | What is compared | What a change means for a reader | Source |
|---|---|---|---|
| Storage price bands | The full storage tier schedule | Stored-capacity cost can move, including graduated bands | [5] [6] |
| Minimum billed object size | The billable size floor for each object | Repositories with many small objects can be billed for more capacity than they contain | [5] [6] |
| Minimum storage period | The minimum age before a qualifying delete, overwrite, move, or transition | Delete, overwrite, move, or transition timing can change the bill | [5] [6] |
| Early-deletion calculation | How the remaining minimum-duration charge is calculated | The same early delete or overwrite can produce a different remainder charge | [5] [6] |
| Minimum billed capacity | The account, plan, or offer capacity floor | A small repository can still receive the full floor charge | [5] [6] |
| Free transfer allowance | The fixed, proportional, bundled, or unlimited transfer allowance | The point where downloaded bytes become paid or policy-limited can move | [5] [6] |
| Internet transfer price bands | The public-internet transfer schedule, or that it is not published | A restore can become more expensive, remain free, or lose its complete published total | [5] [6] |
| Retrieval price | The representative retrieval rate | Reading cold or infrequent data can change independently of egress | [5] [6] |
| Retrieval choices and timing | Named retrieval speeds, latencies, request prices, and byte rates | A faster or slower recovery path can change both time and price | [5] [6] |
| Class A requests | Write, list, multipart, and other Class A rules | Write-heavy backup activity can move the monthly total | [5] [6] |
| Class B requests | Read, metadata, and other Class B rules | Restore, verification, and integrity-check traffic can move the monthly total | [5] [6] |
| Fixed fees | Monthly, account, or bundled-plan fees | A base fee can change the winner even when usage rates do not | [5] [6] |
What each recorded price change shows
Each change keeps the provider, storage class, region, charge that moved, prior value, new value, first date seen, vendor source, and vendor effective date when one is published. Both values preserve the complete charge, including price bands and conditions, instead of reducing a rule to one headline number. [5]
First seen answers when this site observed the value. Effective date answers when the vendor says the rule took effect. Those dates can differ, and the page keeps both rather than moving an observation backward to match an announcement. [5]
When a vendor does not publish a rate, we say so. Not published does not mean free, a missing rate is never counted as zero, and a blank is not an acceptable answer. [7]
| Change detail | Meaning | Reader use | Source |
|---|---|---|---|
| Provider, class, and region | The exact regional offer that changed | Prevents one region from being mistaken for another | [5] |
| Charge or rule | The charge or rule that moved | Separates a storage change from egress, retrieval, request, floor, or fee changes | [5] |
| Previous value | The complete value in the previous saved check | Shows the rule that an earlier estimate used | [5] |
| New value | The complete value in the newer saved check | Shows the rule a current estimate uses | [5] |
| First seen | The UTC time at which we first saw the new value | Marks the limit of what we can claim to have observed | [5] |
| Vendor effective date | The vendor-published effective date, or not published | Distinguishes billing effect from collection time | [5] [7] |
| Vendor source | The vendor page or feed attached to the changed offer | Lets the reader check the change against the vendor's own pages | [5] |
Two recent price changes, from vendor announcements
Wasabi's May 2026 pricing FAQ identifies the prior $6.99 per TB-month Pay as You Go plan, gives the new $7.99 per TB-month price, and says current customers see the change on the first billing cycle on or after 2026-07-01. The announcement also says free egress and API request policies were unchanged. [3]
Backblaze announced that B2 Pay as You Go storage would move from $6.00 to $6.95 per TB-month on 2026-05-01. It made standard API calls free on the same date and left its 3x free-egress rule unchanged. [4] [8]
We did not see either change ourselves, because both effective dates precede 2026-07-26. They remain useful context, but we cannot say how they affect the standard-workload winner because we never saved the earlier complete rates and rules. [1] [3] [4]
| Offer | Charge | Old value | New value | Effective date | Seen in our own checks | Source |
|---|---|---|---|---|---|---|
| Wasabi Hot Cloud Storage, us-east-1 | Storage price tiers | $6.99 per TB-month | $7.99 per TB-month | 2026-07-01 | Not seen by us; the vendor announcement predates our price history | [3] |
| Backblaze B2 Cloud Storage, us-west-004 | Storage price tiers | $6.00 per TB-month | $6.95 per TB-month | 2026-05-01 | Not seen by us; the vendor announcement predates our price history | [4] |
A storage move does not decide the winner by itself
Egress is the decision variable because moving stored data back to a user can outweigh the storage line. Backblaze includes public-internet egress up to 3x average monthly storage and then charges $0.01/GB, while Cloudflare R2 charges no egress but meters Class A and Class B operations. [8] [9] [10]
Wasabi charges no metered transfer at any volume. Monthly outbound traffic within the stored volume fits its guideline; for repeated excess, Wasabi reserves the right to limit or suspend the service. So the calculator here prices that excess at $0, as Wasabi bills it, with the policy beside it. [11]
A restore is read-only. Retrieval, restore and read requests, temporary-copy storage, and egress can apply, but reading does not create an early-deletion charge. Early deletion applies only when a separate action deletes, overwrites, moves, or transitions an object before its minimum duration. [12] [13] [11]
| Changed rule | What it means for you | What still has to be checked | Source |
|---|---|---|---|
| Storage rate or tier | The stored-capacity line changes | Capacity floors, free storage, egress, retrieval, requests, fixed fees, and region | [6] |
| Free-egress allowance | The point where transfer becomes paid or policy-limited moves | Whether the allowance uses average or active storage, its destination, and any overage rate | [8] [11] |
| Class A or Class B schedule | Backup writes, listings, reads, or checks can become cheaper or more expensive | Actual request counts and class mapping | [10] [4] |
| Retrieval rate or tier | The cost or time to make cold data readable changes | Egress, request count, destination, and temporary-copy duration | [12] [13] |
| Minimum duration or early-deletion method | An early delete, overwrite, move, or transition can change the remainder charge | Object age and whether the workflow deletes, overwrites, moves, or transitions | [13] [11] |
Where vendor pages disagree
The current Backblaze pricing page and its 2026 announcement agree on $6.95 per TB-month, but the transaction-pricing page still says storage after the first 10 GB is $0.005/GB-month. We treat that storage note as out of date and do not use it for current storage pricing; the transaction page remains the source for the 3x egress allowance and $0.01/GB overage. [8] [4] [9]
Our July 25 check of Wasabi's prices did not include a minimum billed object size, while the current official FAQ says objects smaller than 4 KB are billed as 4 KB, and our current price table uses that 4 KB minimum. We leave the dated July observation as it was. [6] [11]
The May 2026 Wasabi announcement describes 20 percent of 1 TB as 100 GB in prose but uses 200 GB in its formula. We do not rely on that transfer example because it contradicts itself. The price-change claim does not depend on that example because the same announcement separately names the old plan, new price, and effective billing date. [3]
| Property | Our price table or chosen source | Conflicting source | What we did | Source |
|---|---|---|---|---|
| Backblaze B2 storage rate | $6.95 per TB-month | $0.005/GB-month note on the transaction page | Use the current pricing page and dated 2026 announcement; treat the transaction-page storage note as out of date | [8] [4] [9] |
| Wasabi minimum billed object size | No figure in our July 25 check | 4 KB on the current official FAQ | Use the 4 KB minimum now and keep the dated July observation intact | [6] [11] |
| Wasabi announcement transfer example | Old and new storage prices are stated separately | The example labels 100 GB as 20 percent of 1 TB but calculates with 200 GB | Do not use the transfer arithmetic; keep only the separately stated price move | [3] |
Sources
Every figure above comes from one of these pages, on the date shown. Each numbered reference in the text links to its entry here. Vendors change prices; if a date looks old, check the source. Three vendors publish a downloadable price feed and the rest are re-checked by hand, which is why the dates are not uniform.
Source pages checked 13 sources
- 1 Our price history backupstorageprices.com · checked 26 July 2026
- 2 Our price history backupstorageprices.com · checked 26 July 2026
- 3 Wasabi docs: May 2026 pricing FAQs docs.wasabi.com · checked 26 July 2026
- 4 Backblaze blog: Pricing and product updates www.backblaze.com · checked 26 July 2026
- 5 Our price history backupstorageprices.com · checked 26 July 2026
- 6 Our price table (all vendors) backupstorageprices.com · checked 26 July 2026
- 7 How we work out the bills backupstorageprices.com · checked 26 July 2026
- 8 Backblaze: B2 Cloud Storage pricing www.backblaze.com · checked 26 July 2026
- 9 Backblaze: B2 API pricing (Class A, B, C, D) www.backblaze.com · checked 26 July 2026
- 10 Cloudflare R2 docs: Pricing developers.cloudflare.com · checked 26 July 2026
- 11 Wasabi: Pay as you go pricing FAQs wasabi.com · checked 12 October 2026
- 12 Amazon S3 docs: Working with archived objects docs.aws.amazon.com · checked 26 July 2026
- 13 AWS: Amazon S3 pricing aws.amazon.com · checked 26 July 2026