Azure SQL Database SLA
Microsoft Azure · Databases · promises up to 99.995% · SLA of Sep 1, 2026 · checked 25h 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
TierUptimeCredit of the monthly bill
- General Purpose / Business Critical / Premium / Hyperscale, Zone RedundantDatabases configured for Zone Redundant Deployments99.995%below 99.995%: 10% · below 99%: 25% · below 95%: 100%
- Hyperscale / Business Critical / Premium / General Purpose, not zone redundantDatabases not configured for Zone Redundant Deployments99.99%below 99.99%: 10% · below 99%: 25% · below 95%: 100%
- Basic / StandardBasic or Standard tier databases99.99%below 99.99%: 10% · below 99%: 25% · below 95%: 100%
More in databases
ServicePromisedFirst creditObserved 365dDowntime
Amazon DynamoDBAWS · Databases · Global Tables SLA99.999%First credit10%Observed 365d99.178%All incidents 99.852%
Lakebase PostgresDatabricks · Databases · High Availability endpoint99.99%First credit5%Observed 365dNo feedAll incidents 100%
Managed DatabasesDigitalOcean · Databases · Cluster with Standby Nodes99.95%First credit10%Observed 365d100%All incidents 99.992%
Elastic Cloud Hosted (formerly Elasticsearch Service)Elastic · Databases · Platinum or Enterprise, High Availability deployment99.95%First credit10%Observed 365d99.146%All incidents 99.896%
Cloud SQLGoogle Cloud · Databases · Enterprise Plus edition with HA (or read pool with 2+ nodes)99.99%First credit10%Observed 365d99.927%All incidents 99.488%
MongoDB Atlas (database clusters)MongoDB · Databases · Dedicated clusters M10 and above99.995%First credit10%Observed 365d99.989%All incidents 99.215%
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
- All incidents, weighted: 100% · Downtime
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.
Sources: each vendor's own SLA page (re-read monthly) and status page feed (read every Friday). A summary, not the contract: the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.