May we count your visit with Google Analytics? It uses cookies and sends visit data to Google. You can change this any time under Cookie choices. Privacy

Backup Storage Prices
Menu

Guide

What a durability number promises, and what an SLA actually pays out

Durability and SLA terms checked · Lock modes checked

12 of 18 vendors publish a durability figure (11 you can compare; OVHcloud Object Storage's contradicts itself) and 12 put an availability SLA in writing; every one of those SLAs pays out in credits or vouchers on the bill, never in lost data restored. What keeps a backup recoverable, not merely stored, is a copy nobody can delete early: 13 of the 18 document a lock that no user, the account's owner included, can lift before its date. Every figure is the vendor's own published claim; we test none.

Vendor Durability it publishesAvailability SLAWhat a missed SLA paysLock modes
Amazon S3 11 nines, designed for S3 Standard 99.0% to 99.9%, by class 10%, 25% or 100% credit on future bills Compliance and governance
Azure Blob Storage 11 nines (LRS) to 16 nines (GRS, GZRS) 99.0% to 99.99%, by tier and redundancy 10% or 25% credit Locked policies nobody can shorten or delete; unlocked policies for testing
Google Cloud Storage 11 nines, every class 99.0% to 99.95%, by class and location 10%, 25% or 50% credit on future bills Compliance and governance
Cloudflare R2 11 nines, designed 99.9%, Enterprise customers only 10%, 25% or 50% credit on future usage Rules a bucket admin can remove
Backblaze B2 11 nines, calculated 99.9% service-level objective 5% or 10% credit on the next payment Compliance and governance
Wasabi 11 nines, designed No current terms on its SLA page; 99.9% availability advertised Not published on the current page Compliance and governance
IDrive e2 11 nines, three copies 99.9% 5% or 10% credit, normally on future invoices Compliance and governance
DigitalOcean Spaces Not published 99.9% Standard, 99.5% Cold Credit for future use; data loss excluded Not documented
Scaleway Object Storage 11 nines, Multi-AZ 99.9% Multi-AZ; 99.0% One Zone and Glacier 10%, 25% or 50% voucher Compliance and governance
OVHcloud Object Storage Its page disagrees with itself: 99.99999999999% called 11 nines 99.9% (1-AZ) or 99.99% (3-AZ) Service compensation; 100% if its data-resilience commitment is missed Compliance and governance
Hetzner Object Storage Not published; survives up to three storage-server failures None published None published Compliance and governance
Akamai Cloud Object Storage 11 nines, E2 and E3 endpoints 99.9% Pro-rata credit for the month Compliance and governance
Vultr Object Storage Not published None published None published Not documented
Storj 11 nines, every tier 99.95% for storage 5% or 10% credit on future fees Compliance and governance
Oracle OCI Object Storage 11 nines, designed Its pages disagree: 99.0% to 99.9% 10%, 25% or 100% credit Locked rules nobody can shorten or delete, after a 14-day delay; unlocked rules
Tigris Not published None public; 99.99% uptime advertised None published Not documented
Filebase Not published None public; Enterprise by contract None published No lock
Telnyx Cloud Storage Not published; copies in several data centers None: provided as is None; Telnyx disclaims responsibility for lost data Compliance and governance (US, APAC and CA buckets only)

What each vendor publishes about durability, availability and its remedy, beside the lock modes its documentation names.

Put your own numbers through the calculator to see what this charge does to a normal month and to the month you restore.

A durability claim is not an availability SLA

Durability estimates the chance that stored objects survive over time. Availability measures whether the service can answer eligible requests. A vendor can publish eleven nines of designed durability and a 99.9% availability SLA without contradiction because the two percentages measure different failure modes. [1] [2]

We did not test any vendor's annual durability. The figures below are the vendors' own published design claims, carried with their wording and retrieval dates. A durability percentage should not be read as independent validation, a recovery-time promise, or a guarantee that deleted or corrupted customer data will be restored. [5] [6]

An availability SLA is also narrower than an uptime headline. Eligibility, excluded events, claim deadlines, affected-resource calculations, and plan restrictions determine whether a credit is owed. The usual remedy is a credit against service fees, not data reconstruction, operational recovery, or compensation for business loss. [3] [4]

Published propertyWhat it measuresUsual remedySource
Durability A vendor's calculated or designed annual probability of retaining objects No remedy follows from the percentage unless contract terms separately create one [1]
Availability Successful access or requests during the SLA measurement period conditional service credits after a qualifying breach and approved claim [2] [3]
Service credit A percentage of eligible fees for the affected service or resource Future bill relief in most checked SLAs, not recovery of the backup [3] [4]
Data loss or corruption A different failure from service unavailability Often excluded from the availability calculation or expressly left to the customer's independent backup plan [5] [6]

Published claims and contractual remedies differ across 18 vendors

All 18 vendors are listed. not published means the vendor's official page did not publish the requested number or remedy; it never means zero. conditional means plan, class, region, or contract restrictions apply. If we find only a previous official term, we label it out of date and do not present it as current. not comparable means official sources disagree, so we show the disagreement instead of choosing one value.

The durability column repeats vendor claims only. Where a vendor describes its architecture without giving a percentage, we do not turn that into a number. The availability column distinguishes formal SLA commitments from marketing uptime, and the remedy column states what an approved claim buys rather than implying that a credit restores data.

Show the table (18 vendors)
ProviderPublished durabilityAvailability SLAWhat the SLA remediesSource
Amazon S3 99.999999999% annual durability, described as 11 nines and designed for S3 Standard [7] conditional by class: 99.9% for Standard, Express One Zone, Glacier Flexible Retrieval, and Glacier Deep Archive; 99.0% for Intelligent-Tiering, Standard-IA, One Zone-IA, and Glacier Instant Retrieval [3] 10%, 25%, or 100% service credit by breach band, generally against future S3 payments; sole and exclusive availability remedy, not data recovery [3] [7] [3]
Azure Blob Storage At least 99.999999999% annual durability for LRS, 99.9999999999% for ZRS, and 99.99999999999999% for GRS or GZRS [8] conditional by tier, redundancy, and request direction: 99.9% for hot-tier writes and most hot reads, 99.99% for eligible RA-GRS or RA-GZRS hot reads, 99.0% for cool, cold, or archive writes, and 99.9% for eligible cool, cold, or archive reads [4] 10% or 25% service credit by applicable threshold. Credits are the sole and exclusive performance or availability remedy and do not compensate other loss [4] [8] [4]
Google Cloud Storage At least 99.999999999% annual durability for all storage classes and location types [9] conditional by class and location: commitments span 99.0%, 99.9%, and 99.95%, with separately listed regional exceptions [10] 10%, 25%, or 50% financial credit against future bills after an eligible claim; no data-recovery remedy is stated [10] [9] [10]
Cloudflare R2 99.999999999% annual durability, described as 11 nines and designed rather than independently measured here [1] conditional: 99.9% monthly uptime for Enterprise customers covered by the R2 SLA [2] 10%, 25%, or 50% service credit against future R2 usage; sole and exclusive remedy for SLA failure, not restoration of data [2] [1] [2]
Backblaze B2 99.999999999% annual durability calculated for the published vault architecture [11] 99.9% monthly service-level objective for B2 Cloud Storage [12] 5% credit from 99.0% to below 99.9%, or 10% below 99.0%, applied to the next payment; sole and exclusive remedy, not data recovery [12] [11] [12]
Wasabi 99.999999999% annual durability, described as designed 11 nines [13] Published system availability is 99.9% for a single region and 99.99% across two regions. The current legal SLA page we checked did not show its operative text, so the contractual schedule is not published from that page [14] [15] Wasabi's current page links a February 2024 PDF marked reference only (10% and 25% credits capped at 50%, applied to future service), so we do not show its credits as current. Current remedy terms are not published on the live page we checked [15] [16] [13] [14] [15] [16]
IDrive e2 99.999999999% durability, described as eleven nines with three copies of data [17] At least 99.9% monthly uptime for paid IDrive services including IDrive e2 [18] 5% credit from 99.0% to below 99.9%, or 10% below 99.0%, normally against future invoices with a discretionary refund option; sole and exclusive remedy, not data recovery [18] [17] [18]
DigitalOcean Spaces not published: official feature documentation describes Ceph redundancy and says Cold has the same durability as Standard, but gives no numeric durability figure [19] conditional by product: 99.9% for Spaces Standard and 99.5% for Spaces Cold Storage [5] [20] Standard credits are 10%, 25%, or 100%; Cold credits are 5%, 10%, 25%, or 100%. Both are future-use credits, data loss is excluded, and the service is not intended as the sole backup [5] [20] [19] [5] [20]
Scaleway Object Storage 99.999999999% durability for Multi-AZ Object Storage [21] conditional by deployment: 99.9% for Standard Multi-AZ and 99.0% for One Zone Infrequent Access or Glacier [22] 10%, 25%, or 50% compensation voucher, capped at 50% of the affected month's fees; the voucher is the all-inclusive remedy and does not recover data [22] [21] [22]
OVHcloud Object Storage not comparable: the same official sentence prints 99.99999999999% and labels it 11 nines. Those forms are mathematically inconsistent, so we report both and do not pick one [23] conditional by deployment: 99.9% in 1-AZ and Local Zones, and 99.99% in 3-AZ regions [23] Service compensation rather than recovery: 0.5% of affected monthly consumption per minute of access failure, capped at 100%; missing the separate 100% monthly data-resilience commitment compensates 100% of affected consumption [24] [23] [24]
Hetzner Object Storage not published: Hetzner documents erasure coding that tolerates up to three storage-server failures, but no numeric durability percentage [25] not published: no Object Storage availability SLA was found in the checked official Object Storage documentation [25] not published: no Object Storage service-credit schedule was found; the documentation says Object Storage should be only part of a backup strategy [25] [25]
Akamai Cloud Object Storage 99.999999999% annual durability for E2 and E3 endpoints, with documented limits for disasters, fire, and human error [26] 99.9% monthly uptime for Object Storage under the current Non-Compute Service Level Addendum [27] Pro-rata service credit for an affected monthly billing period after an eligible claim; the SLA provides billing credit, not reconstruction of objects [27] [26] [27]
Vultr Object Storage not published: current product documentation calls the service durable and highly available but does not publish a numeric durability percentage [28] not published: no numeric Object Storage availability SLA was found in the checked current Object Storage documentation [28] [29] not published: no Object Storage service-credit remedy was found in those sources [28] [29] [28] [29]
Storj 99.999999999% durability, described as 11 nines for all published pricing tiers [30] 99.95% monthly availability for Storage Services; Edge Services have a separate 99.9% commitment [31] 5% credit below 99.95% and above 99.0%, or 10% below 99.0%, capped at 10% and applied to future fees; sole and exclusive remedy, while retrievability is not guaranteed [31] [30] [31]
Oracle OCI Object Storage 99.999999999% annual durability, described as eleven nines and designed for OCI Object Storage [32] not comparable across current official sources: the tier guide lists 99.9% for Standard, 99.0% for Infrequent Access, and no numeric Archive value, while the March 2026 pillar covers Object Storage and Archive Storage SKUs with a 99.9% API-uptime commitment [33] [34] 10%, 25%, or 100% service credit for eligible Object Storage availability breaches; a billing credit does not recover deleted or overwritten data [34] [32] [32] [33] [34]
Tigris not published: Tigris says it offers the same durability guarantees as large clouds but publishes no numeric durability figure on the checked page [35] not published as a public SLA: the site markets 99.99% uptime, while pricing says larger workloads can customize a service contract [35] [36] not published: no public credit schedule was found, and a customized enterprise contract is conditional on negotiation [36] [35] [36]
Filebase not published: Filebase describes its object storage as durable but does not publish a numeric durability percentage on the checked product page [37] conditional: public self-service plans have no published numeric SLA; Enterprise advertises a dedicated SLA without public terms [38] not published: the public pricing page gives no credit percentage or data-recovery remedy for the Enterprise SLA [38] [37] [38]
Telnyx Cloud Storage not published: the product page says data is duplicated across multiple datacenters with no single point of failure, but gives no numeric durability percentage [39] not published: the current terms provide Storage Services as is and as available rather than publishing an availability commitment [6] does not apply under the public terms: Telnyx disclaims storage warranties and responsibility for loss, misuse, deletion, or failure to store, and assigns backup responsibility to the customer [6] [39] [6]

Egress still decides the restore bill

Durability and SLA complete the risk picture, but egress remains the cost variable that can dominate a backup restore. The rules below come from the 66 offers across 18 vendors and their cited vendor sources; they are not recalculated from storage rates. [40] [41] [42]

In this comparison, a restore is read-only. The charges it can trigger are retrieval, API requests, temporary-copy storage, and egress. It never triggers early deletion, which applies only when an object is deleted, overwritten, moved, or transitioned before its minimum. [43] [44] [45]

Vendor or actionOn a restoreCharge statusSource
Backblaze B2 Internet egress is free up to 3 times average monthly storage, then $0.01/GB depends on use [40]
Cloudflare R2 Internet egress has no charge, but Class A and Class B operations are billed, so a restore is not automatically a zero-cost event not charged for egress; conditional for requests [41]
Wasabi No egress fee at any volume. Monthly downloads up to the amount stored fit Wasabi's free-egress guideline; regularly downloading more can get the account limited or suspended conditional; no fee above the guideline [42]
Read-only restore Retrieval, requests, temporary-copy storage, and egress can apply; no delete, overwrite, move, or transition occurs Early deletion: does not apply [43] [44] [45]

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 45 sources
  1. 1 Cloudflare R2 docs: Durability developers.cloudflare.com · checked 26 July 2026
  2. 2 Cloudflare: Enterprise subscription SLA (R2) www.cloudflare.com · checked 26 July 2026
  3. 3 AWS: Amazon S3 service level agreement aws.amazon.com · checked 26 July 2026
  4. 4 Microsoft SLA for Online Services (Word document) www.microsoft.com · checked 26 July 2026
  5. 5 DigitalOcean Spaces SLA www.digitalocean.com · checked 26 July 2026
  6. 6 Telnyx: Terms and conditions of service telnyx.com · checked 26 July 2026
  7. 7 AWS: Amazon S3 FAQs aws.amazon.com · checked 26 July 2026
  8. 8 Azure docs: Azure Storage redundancy learn.microsoft.com · checked 26 July 2026
  9. 9 Google Cloud Storage docs: Data availability and durability cloud.google.com · checked 26 July 2026
  10. 10 Google Cloud Storage SLA cloud.google.com · checked 26 July 2026
  11. 11 Backblaze help: B2 resiliency, durability and availability help.backblaze.com · checked 26 July 2026
  12. 12 Backblaze service level agreement www.backblaze.com · checked 26 July 2026
  13. 13 Wasabi docs: Durability, security, and reliability docs.wasabi.com · checked 26 July 2026
  14. 14 Wasabi docs: System availability docs.wasabi.com · checked 26 July 2026
  15. 15 Wasabi service level agreement wasabi.com · checked 26 July 2026
  16. 16 Wasabi SLA, February 2024 (PDF, marked reference only) cdn.brandfolder.io · checked 26 July 2026
  17. 17 IDrive e2 developer guide: Getting started www.idrive.com · checked 26 July 2026
  18. 18 IDrive service level agreement www.idrive.com · checked 26 July 2026
  19. 19 DigitalOcean docs: Spaces features docs.digitalocean.com · checked 26 July 2026
  20. 20 DigitalOcean Spaces Cold Storage SLA www.digitalocean.com · checked 26 July 2026
  21. 21 Scaleway: Object Storage www.scaleway.com · checked 26 July 2026
  22. 22 Scaleway: Object Storage SLA www.scaleway.com · checked 26 July 2026
  23. 23 OVHcloud: Object Storage classes www.ovhcloud.com · checked 26 July 2026
  24. 24 OVHcloud: Public Cloud FAQ www.ovhcloud.com · checked 26 July 2026
  25. 25 Hetzner Object Storage FAQ: General docs.hetzner.com · checked 26 July 2026
  26. 26 Akamai docs: Data durability techdocs.akamai.com · checked 26 July 2026
  27. 27 Akamai SLA (non-compute) www.akamai.com · checked 26 July 2026
  28. 28 Vultr docs: Object Storage docs.vultr.com · checked 26 July 2026
  29. 29 Vultr docs: Object Storage subscription limits docs.vultr.com · checked 26 July 2026
  30. 30 Storj pricing www.storj.io · checked 26 July 2026
  31. 31 Storj terms of service www.storj.io · checked 26 July 2026
  32. 32 Oracle: Object Storage FAQ www.oracle.com · checked 26 July 2026
  33. 33 Oracle docs: Object Storage storage tiers docs.oracle.com · checked 26 July 2026
  34. 34 Oracle PaaS and IaaS Public Cloud Services pillar document (PDF) www.oracle.com · checked 26 July 2026
  35. 35 Tigris home page www.tigrisdata.com · checked 26 July 2026
  36. 36 Tigris pricing www.tigrisdata.com · checked 26 July 2026
  37. 37 Filebase: Object Storage filebase.com · checked 26 July 2026
  38. 38 Filebase pricing filebase.com · checked 26 July 2026
  39. 39 Telnyx: Cloud Storage telnyx.com · checked 26 July 2026
  40. 40 Backblaze: B2 API pricing (Class A, B, C, D) www.backblaze.com · checked 26 July 2026
  41. 41 Cloudflare R2 docs: Pricing developers.cloudflare.com · checked 26 July 2026
  42. 42 Wasabi: Pay as you go pricing FAQs wasabi.com · checked 12 October 2026
  43. 43 Amazon S3 docs: Restoring an archived object docs.aws.amazon.com · checked 26 July 2026
  44. 44 AWS: Amazon S3 pricing aws.amazon.com · checked 26 July 2026
  45. 45 Google Cloud Storage pricing cloud.google.com · checked 26 July 2026