Uptimeby Glyph
Amazon DynamoDB SLA
AWS · Databases · promises up to 99.999% · SLA of May 14, 2025 · 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.99% Standard SLA, which applies per region. 1 of 12 months fell below it (credits are claimed per month). The 99.999% Global Tables SLA tier assumes failover to another region, so a one-region outage is not held against it. 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: 4.4 min
Commitments and credits
Standard SLA
Any DynamoDB tables in the region that are not Global Tables
Credit: below 99.99%: 10% · below 99%: 25% · below 95%: 100%
Global Tables SLA
All tables in the region are part of Global Tables for the whole month and the customer makes reasonable attempts to fail over
Credit: below 99.999%: 10% · below 99%: 25% · below 95%: 100%
More in databases
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
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
- Average of 5-minute Availability (share of requests not failing with 500/503) per AWS region
- Credit cap
- Up to 100% of the applicable DynamoDB charges (for Global Tables, including replica table charges in other regions) at the lowest tier; 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 'SLA Credit Request' in the subject line and request logs
- Not covered
- Factors outside AWS's reasonable control; Voluntary customer actions or inactions; Not following DynamoDB Developer Guide best practices; Additional recovery time due to insufficient read/write throughput; Customer equipment, software or other technology; AWS suspension or termination of the right to use DynamoDB
- Status history
- Status history since Sep 23, 2025
- Weighted uptime
- All incidents, weighted: 99.86% · Downtime
Global Tables SLA ... Less than 99.999% but equal to or greater than 99.0% 10% ... Less than 95.0% 100%
Global Tables SLA falls back to the Standard SLA if the customer does not make reasonable attempts to fail over. DynamoDB Accelerator (DAX) has a separate SLA.