Amazon RDS (Multi-AZ) SLAAWS · Databases · AWS · Databases
Promise vs reality
Downtime used against the allowance
3 d of major incidents, 16.4x the allowance4.4 h allowed in 365 days
3 major and 0 minor incidents; worst region me-central-1. 0 min degraded (not counted).
Major incident minutes per month
Allowed per month: 22 min
- Promised
- 99.95%
- Observed, 365d
- 99.178%
- Major incident time
- 3 d
- Credit on first breach
- 10%
Commitments and credits
- Multi-AZ DB Instance / Multi-AZ DB ClusterRDS for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, Db2 with Multi-AZ deployment option99.95%
Monthly uptime below, credit of the bill
- Below 99.95%10%
- Below 99%25%
- Below 95%100%
- Single-DB InstanceRDS database instances with the Single-DB Instance deployment option99.5%
Monthly uptime below, credit of the bill
- Below 99.5%10%
- Below 99%25%
- Below 95%100%
Terms
- 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
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).
Evidence: incidents, last 365 days
Other databases SLAs
ServiceDowntime vs allowed
Amazon DynamoDBAWS99.999% / 99.178%
Azure SQL DatabaseMicrosoft Azure99.995% / n/a
MongoDB Atlas (database clusters)MongoDB99.995% / 99.989%
Lakebase PostgresDatabricks99.99% / n/a
Cloud SQLGoogle Cloud99.99% / 99.927%
Managed DatabasesDigitalOcean99.95% / 100%
Elastic Cloud Hosted (formerly Elasticsearch Service)Elastic99.95% / 99.146%
Promised in the SLAObserved on the vendor's status pagePartial historyShortfall
Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.