Uptimeby GlyphAzure SQL Database SLA
Microsoft Azure · Databases · promises up to 99.995% · 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
General Purpose / Business Critical / Premium / Hyperscale, Zone Redundant
Databases configured for Zone Redundant Deployments
Credit: below 99.995%: 10% · below 99%: 25% · below 95%: 100%
Hyperscale / Business Critical / Premium / General Purpose, not zone redundant
Databases not configured for Zone Redundant Deployments
Credit: below 99.99%: 10% · below 99%: 25% · below 95%: 100%
Basic / Standard
Basic or Standard tier databases
Credit: below 99.99%: 10% · below 99%: 25% · below 95%: 100%
More in databases
Amazon DynamoDBAWS promises 99.999% 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
Amazon RDS (Multi-AZ)AWS promises 99.95% 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
Databricks promises 99.99% uptime, with a 5% credit when it misses; its status page has no history this site can read.
DigitalOcean promises 99.95% uptime, with a 10% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
Elastic promises 99.95% uptime, with a 10% credit when it misses; its status page showed 3.1 d of major outage in the last year.
Observed 99.157% over 365 days
Elastic promises 99.95% uptime, with a 10% credit when it misses; its status page showed 3.1 d of major outage in the last year.
Observed 99.157% over 365 days
Google Cloud promises 99.99% 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
MongoDB promises 99.995% uptime, with a 10% credit when it misses; its status page showed 60 min of major outage in the last year.
Observed 99.989% over 365 days
Lakebase PostgresDatabricks promises 99.99% uptime, with a 5% credit when it misses; its status page has no history this site can read.99.99%First credit5%Observed 365dNo feed
Managed DatabasesDigitalOcean promises 99.95% uptime, with a 10% credit when it misses; its status page showed no major outage in the last year.99.95%First credit10%Observed 365d100%All incidents 99.989%
Elastic Cloud Hosted (formerly Elasticsearch Service)Elastic promises 99.95% uptime, with a 10% credit when it misses; its status page showed 3.1 d of major outage in the last year.99.95%First credit10%Observed 365d99.157%All incidents 99.896%
Cloud SQLGoogle Cloud promises 99.99% 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.99%First credit10%Observed 365d99.939%All incidents 99.467%
MongoDB Atlas (database clusters)MongoDB promises 99.995% uptime, with a 10% credit when it misses; its status page showed 60 min of major outage in the last year.99.995%First credit10%Observed 365d99.989%All incidents 99.279%
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. A minute is unavailable if all continuous connection attempts to the database fail.
- Credit 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
applicable to Customer's use of the General Purpose, Business Critical, Premium or Hyperscale tiers of the SQL Database Service configured for Zone Redundant Deployments: ... < 99.995% 10% < 99% 25% < 95% 100%
Business Critical with active geo-replication and a Compliant Secondary also carries an RPO commitment of 5 seconds (10% of the secondary's cost if attainment is below 100%) and an RTO commitment of 30 seconds.