AWS Lambda SLA
AWS · Compute · promises up to 99.95% · SLA of May 5, 2022 · checked 23h ago
3 major outages in the last 365 days, each in one region (me-south-1, me-central-1 and us-east-1).
Worst region me-central-1: 72 h counted, 99.178% observed against the 99.95% Standard, which applies per region. 2 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
TierUptimeCredit of the monthly bill
- StandardAll Lambda functions per AWS region99.95%below 99.95%: 10% · below 99%: 25% · below 95%: 100%
More in compute
ServicePromisedFirst creditObserved 365dDowntime
Amazon EC2AWS · Compute · Region-Level99.99%First credit10%Observed 365d99.178%All incidents 99.852%
Cloudflare WorkersCloudflare · Compute · Enterprise99.99%First credit10%Observed 365d100%All incidents 99.984%
Confluent Cloud for Apache FlinkConfluent · Compute · Flink (per region)99.99%First credit5%Observed 365d99.628%All incidents 97.169%
DigitalOcean Kubernetes (DOKS) HA control planeDigitalOcean · Compute · HA control plane99.95%First credit10%Observed 365d100%All incidents 99.992%
Compute EngineGoogle Cloud · Compute · Instances in Multiple Zones (Premium Tier)99.99%First credit10%Observed 365d99.927%All incidents 99.488%
Azure FunctionsMicrosoft Azure · Compute · Consumption plan99.95%First credit10%Observed 365dNo feedAll incidents 100%
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.852% · 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.
Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.