Uptimeby Glyph
AWS Lambda SLA
AWS · Compute · promises up to 99.95% · SLA of May 5, 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.95% Standard, 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
Standard
All Lambda functions per AWS region
Credit: below 99.95%: 10% · below 99%: 25% · below 95%: 100%
More in compute
Amazon EC2AWS promises 99.99% 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
- Average of 5-minute Availability (share of requests not failing with 500/503) per AWS region
- Credit cap
- Up to 100% of Lambda charges in the affected region at the lowest tier; applied against future Lambda 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 'SLA Credit Request' in the subject line and request logs
- Not covered
- Factors outside AWS's reasonable control; Voluntary customer actions (e.g. custom 500/503 codes, misconfigured VPC/security groups, disabled encryption keys); Not following Lambda User Guide best practices; Customer equipment, software or other technology; AWS suspension or termination of the right to use Lambda
- Status history
- Status history since Sep 23, 2025
- Weighted uptime
- All incidents, weighted: 99.86% · Downtime
AWS will use commercially reasonable efforts to make Lambda available with a Monthly Uptime Percentage for each AWS region, during any monthly billing cycle, of at least 99.95% (the “Service Commitment”).
Custom 500/503 status codes emitted by the customer's function code are not counted as Errors.