AWS Lambda runs code without servers - and inherits the health of everything underneath it (EC2 capacity, networking, IAM, and the services that trigger it). Lambda incidents usually surface as elevated invocation errors or throttling in one region, or as latency spikes when cold starts pile up.
Elevated invocation error rates (5xx) in one region
Throttling when concurrency limits interact with retry storms
Increased cold-start latency after capacity or runtime events
Event-source lag: SQS/Kinesis triggers delivering late while Lambda itself is healthy
AWS Lambda questions
Is Lambda down right now?+
The live status above reflects our latest check. Lambda failures are often regional and partial - if you see elevated errors, check whether they cluster in one region before assuming a code bug.
Why do my Lambda functions time out during AWS incidents?+
Functions frequently depend on other degraded services (S3, DynamoDB, RDS). During upstream incidents, functions burn their timeout waiting on slow dependencies, which looks like a Lambda problem but is not.
Does Lambda have an SLA?+
Yes - 99.95% monthly uptime. Below that, tiered service credits (10%/25%/100%) apply to the month’s Lambda charges if you file a claim.
Get alerted when AWS Lambda breaks
Instant email the moment we detect an incident - affected services and regions included.
aws