Uptimeby Glyph
Amazon RDS (Multi-AZ) SLA
AWS · Databases · promises up to 99.95% · SLA of Jan 22, 2024 · checked 47d ago
2 major outages in the last 365 days, each in one region (me-south-1 and me-central-1).
Worst region me-central-1: 72 h counted, 99.178% observed against the 99.95% Multi-AZ DB Instance / Multi-AZ DB Cluster, which applies per region. 1 of 12 months fell below it (credits are claimed per month). 2 incidents ran past 72 hours; each counts for 72 hours at most (see the method).
Last 90 days: no major outage.
Incidents, last 365 days
Major outage time per month
Allowed per month: 22 min
Commitments and credits
Multi-AZ DB Instance / Multi-AZ DB Cluster
RDS for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, Db2 with Multi-AZ deployment option
Credit: below 99.95%: 10% · below 99%: 25% · below 95%: 100%
Single-DB Instance
RDS database instances with the Single-DB Instance deployment option
Credit: below 99.5%: 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
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
Microsoft Azure promises 99.995% uptime, with a 10% credit when it misses; its status page has no history this site can read.
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%
Azure SQL DatabaseMicrosoft Azure promises 99.995% uptime, with a 10% credit when it misses; its status page has no history this site can read.99.995%First credit10%Observed 365dNo feed
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
- Percentage of 1-minute intervals in the billing cycle in which all connection requests fail, per DB instance/cluster
- Credit cap
- Up to 100% of charges for the affected instances/clusters at the lowest tier; applied against future RDS payments; issued only if over $1
- Claim window
- By the end of the second billing cycle after which the incident occurred
- How to claim
- Open a case in the AWS Support Center with subject 'Amazon RDS SLA Credit Request - Multi-AZ Claim' (or Single-DB Claim), DB instance IDs and request logs
- Not covered
- Factors outside AWS's reasonable control; Voluntary customer actions or inactions; Micro DB instance class or similarly resource-limited classes; Not following the RDS User Guide operational guidelines (e.g. overloading an instance); Database engine software causing repeated crashes; Long recovery due to insufficient IO capacity
- Status history
- Status history since Sep 23, 2025
- Weighted uptime
- All incidents, weighted: 99.86% · Downtime
Multi-AZ DB Instance and Multi-AZ DB Cluster SLA ... Less than 99.95% but equal to or greater than 99.0% 10% ... Less than 95.0% 100%
Multi-AZ and Single-DB claims cannot be combined or stacked. Aurora has its own separate SLA (not covered here).