Uptimeby Glyph
Amazon EC2 SLA
AWS · Compute · promises up to 99.99% · SLA of May 25, 2022 · 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% Region-Level, 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: 4.4 min
Commitments and credits
Region-Level
All running instances deployed concurrently across two or more AZs in the same region (or two regions if the region has one AZ)
Credit: below 99.99%: 10% · below 99%: 30% · below 95%: 100%
Instance-Level
Each individual EC2 instance (Single EC2 Instance)
Credit: below 99.5%: 10% · below 99%: 30% · below 95%: 100%
SLA changes
Amazon EC2
Amazon Compute SLA narrowed to EC2 only; the May 5, 2022 version listed EC2, EBS, ECS and Fargate as Included Services under one SLA. Percentages unchanged (99.99% region, 99.5% instance).
4 years agoSource
Amazon EC2
Instance-Level SLA of 99.5% monthly with 10/30/100% credits introduced, replacing the July 22, 2020 'Hourly Commitment' (Single EC2 Instance Hourly Uptime Percentage of at least 90% per clock hour, otherwise that instance hour is not charged).
4 years agoSource
Amazon EC2
Third credit tier added: below 95.0% now earns a 100% credit (February 12, 2018 version topped out at 30% for 'Less than 99.0%').
7 years agoSource
Amazon EC2
Region-level EC2 (and EBS) commitment raised from 99.95% to 99.99%. June 1, 2013 version: 'Monthly Uptime Percentage ... of at least 99.95%'; November 15, 2017 version: 'of at least 99.99%'. Credit tiers stayed 10% / 30%.
8 years agoSource
More in compute
AWS LambdaAWS 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
Cloudflare promises 99.99% uptime, with a 10% credit when it misses; its status page showed 7.6 h of major outage in the 71 days on file.
Observed 99.552% over 365 days
Confluent promises 99.99% uptime, with a 5% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
Confluent promises 99.9% uptime, with a 5% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
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
DigitalOcean promises 99.99% uptime, with a 100% credit when it misses; its status page showed no major outage in the last year.
Observed 100% 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.95% uptime, with a 10% credit when it misses; its status page has no history this site can read.
Cloudflare WorkersCloudflare promises 99.99% uptime, with a 10% credit when it misses; its status page showed 7.6 h of major outage in the 71 days on file.99.99%First credit10%Observed 365d99.552%All incidents 99.951%
Confluent Cloud for Apache FlinkConfluent promises 99.99% uptime, with a 5% credit when it misses; its status page showed no major outage in the last year.99.99%First credit5%Observed 365d100%All incidents 97.635%
DigitalOcean Kubernetes (DOKS) HA control planeDigitalOcean 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%
Compute EngineGoogle 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 FunctionsMicrosoft Azure promises 99.95% uptime, with a 10% credit when it misses; its status page has no history this site can read.99.95%First credit10%Observed 365dNo feed
Terms, exclusions and sources
- Measured
- Region-Level: Monthly Uptime Percentage per AWS region (minutes all multi-AZ instances concurrently lack external connectivity). Instance-Level: per single instance per month.
- Credit cap
- Up to 100% of the monthly bill for EC2 in the affected region (or for the affected instance) at the lowest tier; credits apply only against future EC2 payments and are 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 Compute SLA Credit Request - Region-Level Claim' or '- Instance-Level Claim', plus resource IDs and request logs
- Not covered
- Factors outside AWS's reasonable control, including force majeure and Internet problems beyond the EC2 demarcation point; Customer actions or inactions, including failure to acknowledge a recovery volume or respond to resource health concerns; Customer equipment, software or other technology; AWS suspension or termination of the customer's right to use EC2
- Status history
- Status history since Sep 23, 2025
- Weighted uptime
- All incidents, weighted: 99.86% · Downtime
AWS will use commercially reasonable efforts to make Amazon EC2 available for each AWS region with a Monthly Uptime Percentage of at least 99.99%, in each case during any monthly billing cycle (the “Region-Level SLA”).
Region-Level and Instance-Level claims cannot be combined or stacked for the same instance. Separately, AWS automatically does not charge for a Single EC2 Instance unavailable for more than six minutes of a clock hour. Since May 25, 2022 this SLA covers EC2 only (EBS, ECS and Fargate were previously in the same Compute SLA).