Vendor record
AWS Lambda
Checked
Front door check counts and AWS Lambda’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented AWS Lambda endpoint and count the checks that got the answer it is documented to give.
No clear answer in 24 hours. These counts are from before this check went quiet.
Front door reachable in 2,623 of 2,623 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- lambda.ap-southeast-2.amazonaws.com
- Scope
- lambdaap-southeast-2
- First check in this window
- Latest clear answer
No clear answer in 24 hours. These counts are from before this check went quiet.
Front door reachable in 2,623 of 2,623 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- lambda.eu-west-1.amazonaws.com
- Scope
- lambdaeu-west-1
- First check in this window
- Latest clear answer
No clear answer in 24 hours. These counts are from before this check went quiet.
Front door reachable in 2,623 of 2,623 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- lambda.us-east-1.amazonaws.com
- Scope
- lambdaus-east-1
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every AWS Lambda product, region or your app worked.
How we count front door checksShorter disruptions
Our checks are 15 minutes apart, so they miss disruptions shorter than that. Datadog runs a separate outage tracker that may show disruptions our checks cannot see.
Independent outage detection for AWS Lambda: Datadog’s Updog(opens in a new tab)CheckUpstream is not affiliated with Datadog.
AWS Lambda says
Incident posts from AWS Lambda’s status page, with its titles, impact levels and times. They say what AWS Lambda chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
AWS does not publish a component catalog for this feed. This page includes an incident only when AWS names this product in the event. A quiet record does not mean the product was available.
0
incidents AWS Lambda posted, last 180 days
Most recent records · all dates
Increased Connectivity Issues
MinorAWS Lambda’s postStarted, per AWS Lambda
Closed in our record(38m)
Increased Error Rates
MinorAWS Lambda’s postStarted, per AWS Lambda
Closed in our record(1h 10m)
Region Availability
CriticalAWS Lambda’s postStarted, per AWS Lambda
Latest status AWS Lambda postedInvestigating. No resolution posted.
Region Availability
CriticalAWS Lambda’s postStarted, per AWS Lambda
Latest status AWS Lambda postedInvestigating. No resolution posted.
Increased Error Rates and Latencies
MinorAWS Lambda’s postStarted, per AWS Lambda
Closed in our record(15h 42m)
Your code, your dependencies
See which of your code paths call AWS Lambda
Connect GitHub or GitLab to find where your public or private repository uses AWS Lambda. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add AWS Lambda status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is AWS Lambda currently down?
AWS Lambda's latest recorded status is Major Outage. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did AWS Lambda last have an outage?
The most recent closed incident record began 204 days ago and spans 38 minutes. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for AWS Lambda?
No. CheckUpstream checks AWS Lambda’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor AWS Lambda in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track AWS Lambda?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.