Uptimeby GlyphAzure Blob Storage (Storage Accounts) SLA
Microsoft Azure · Storage · promises up to 99.99% · SLA of Sep 1, 2026 · checked 13d ago
Incidents, last 365 days
Azure publishes post-incident reviews as web pages only, with no machine-readable history, so observed uptime is not computed.
Commitments and credits
Hot / Transaction Optimized, LRS/ZRS/GRS/GZRS (reads and writes), RA-GRS/RA-GZRS writes
Storage accounts in the Hot access tier
Credit: below 99.9%: 10% · below 99%: 25%
Hot / Transaction Optimized, RA-GRS and RA-GZRS read requests
Read requests to read-access geo-redundant accounts (with retry against the secondary region)
Credit: below 99.99%: 10% · below 99%: 25%
Cool / Cold / Archive, write requests (all redundancy types)
Storage in the Cool, Cold and Archive access tiers
Credit: below 99%: 10% · below 98%: 25%
More in storage
Amazon S3 (Standard)AWS promises 99.9% uptime, with a 10% credit when it misses; its status page showed 3 d of major outage in the last year.
Observed 99.178% over 365 days
Apple publishes no SLA for it; its status page has no history this site can read.
Cloudflare promises 99.9% uptime, with a 10% credit when it misses; its status page showed no major outage in the 71 days on file.
Observed 100% over 365 days
DigitalOcean promises 99.9% uptime, with a 10% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
DigitalOcean promises 99.99% uptime, with a 100% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
Google Cloud promises 99.95% uptime, with a 10% credit when it misses; its status page showed 3.7 h of major outage in the 252 days on file.
Observed 99.939% over 365 days
Oracle Cloud Infrastructure promises 99.9% uptime, with a 10% credit when it misses; its status page has no history this site can read.
iCloud and CloudKit for developersApple publishes no SLA for it; its status page has no history this site can read.NoneFirst creditn/aObserved 365dNo feed
Cloudflare R2Cloudflare promises 99.9% uptime, with a 10% credit when it misses; its status page showed no major outage in the 71 days on file.99.9%First credit10%Observed 365d100%All incidents 99.951%
Spaces Object StorageDigitalOcean promises 99.9% uptime, with a 10% credit when it misses; its status page showed no major outage in the last year.99.9%First credit10%Observed 365d100%All incidents 99.989%
Cloud StorageGoogle Cloud promises 99.95% uptime, with a 10% credit when it misses; its status page showed 3.7 h of major outage in the 252 days on file.99.95%First credit10%Observed 365d99.939%All incidents 99.467%
OCI Object StorageOracle Cloud Infrastructure promises 99.9% uptime, with a 10% credit when it misses; its status page has no history this site can read.99.9%First credit10%Observed 365dNo feed
Terms, exclusions and sources
- Measured
- Uptime Percentage per 'Applicable Period': for metered pay-as-you-go services, the 30 days prior to and including the first day of the Incident; for other services, the calendar month. Uptime = 100% minus Average Error Rate (hourly Failed Storage Transactions / Total Storage Transactions).
- Credit cap
- Maximum published credit is 25% for storage; overall cap: Service Credits in any billing month will not exceed the monthly service fees for that Service or Service Resource in the Applicable Period
- Claim window
- Within 60 days of the Incident (Azure)
- How to claim
- Submit the claim to Microsoft customer support with incident description, time and duration of downtime, affected resource names, number/location of affected users and error descriptions
- Not covered
- Factors outside Microsoft's reasonable control (natural disaster, war, government action, network failures outside Microsoft data centers); Services, hardware or software not provided by Microsoft; Preview, pre-release, beta or trial versions, or purchases made with subscription credits; Customer failure to follow required/supported configurations or published guidance; Exceeding reasonable use or quotas, or throttling of suspected abuse; Scheduled Downtime (at least 5 days' notice) and customer-initiated restart/stop/failover/scale operations
- Status history
- Azure publishes post-incident reviews as web pages only, with no machine-readable history, so observed uptime is not computed.
- Weighted uptime
Service Credit –RA-GRS and RA-GZRS (read requests) for Hot, and Transaction Optimized Access Tiers Uptime Percentage Service Credit < 99.99% 10% < 99% 25%
Maximum credit for Storage Accounts is 25% (no 100% tier). As printed in the September 2026 edition, Cool/Cold/Archive read requests show '< 99.9% 10%, < 98% 25%' for both RA-GRS/RA-GZRS and LRS/ZRS/GRS/GZRS. Failed transactions are defined by maximum processing times (e.g. 2 seconds per MB for PutBlob/GetBlob).