Is Lambda down? › Outage history › Mar 2, 2026
Lambda outage on Mar 2, 2026: what happened
On Mar 2, 2026, the Lambda GPU Cloud status page reported "Launches Failing in Multiple Regions". About 2 days 19 hours: from Mar 2, 2026, 22:42 UTC to Mar 5, 2026, 18:10 UTC, by the official start and resolution times.
Lambda right now
At our last refresh (Oct 22, 2026, 12:35 UTC) Lambda was up: All Systems Operational.
- Started
- Mar 2, 2026, 22:42 UTC
- Resolved
- Mar 5, 2026, 18:10 UTC
- Duration
- 2 days 19 hours
- Official impact
- Critical
- Source
- Launches Failing in Multiple Regions on the Lambda GPU Cloud status page
The Lambda GPU Cloud status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.
What caused the Lambda outage?
The Lambda GPU Cloud status page has not published a cause. When it identified the problem at 18:53 UTC on Mar 4, 2026, it said: "Severity Level: [High] We're currently investigating an issue with On-Demand Cloud instance launches across multiple regions. A disruption to the creation of new Firewall Rulesets is causing instance launches to fail or enter an Alert status for customers without existing Firewall Rulesets in the affected regions. We have re-enabled launches, however customers without existing Firewall Rulesets may still experience failures in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 In the event you're unsure as to whether your service is impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time."
When was it fixed?
The Lambda GPU Cloud status page marked it resolved at Mar 5, 2026, 18:10 UTC, 2 days 19 hours after it started. A fix was in place and being monitored from Mar 3, 2026, 13:02 UTC. Its resolution note: "Severity Level: [High] Our Engineering team was able to identify and remediate the root cause of the issue. Users that were experiencing instance launch failures should no longer be impacted. In the event you're unsure as to whether your service is still impacted by this incident, please open a ..."
Timeline of official updates
Every update the Lambda GPU Cloud status page posted, oldest first. Times are UTC.
Mar 2, 2026, 22:42 UTC investigating
Severity Level: Medium We're currently investigating a potential issue with our us-east-1 instance launches. Users will currently experience instance launch failures in this region. Our engineers are actively working to identify the root cause of the issue. Other regions are not currently impacted. In the event you're unsure as to whether your service is impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Mar 3, 2026, 13:02 UTC monitoring
Severity Level: [Medium] A fix has been implemented and we're monitoring the results. To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Mar 3, 2026, 18:40 UTC investigating
Severity Level: High We're currently investigating instance failure launches with our On-Demand Cloud. Currently, Instance launches are disabled. Our engineers are actively working to identify the root cause of the issue. In the event you're unsure as to whether your service is impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Mar 3, 2026, 19:22 UTC investigating
Severity Level: High We're currently investigating instance failure launches with our On-Demand Cloud. Our engineers are actively working to identify the root cause of the issue. Instance Launches have been disabled for the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 • asia-south-1 • asia-northeast-1 In the event you're unsure as to whether your service is impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Mar 3, 2026, 23:36 UTC investigating
Severity Level: [High] UPDATE: • The below is still accurate. We're continuing the investigation with our service provider. Please bear with us as we work to re-enable instance launches in the regions listed below. We're currently investigating instance failure launches with our On-Demand Cloud. Our engineers are actively working to identify the root cause of the issue. Instance Launches have been disabled for the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 • asia-south-1 • asia-northeast-1 In the event you're unsure as to whether your service is impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Mar 4, 2026, 18:37 UTC investigating
Severity Level: [High] We're investigating instance launch failures for On-Demand Cloud with our service provider. Please bear with us as we work to re-enable instance launches in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 • asia-south-1 • asia-northeast-1 In the event you're unsure as to whether your service is impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Mar 4, 2026, 18:53 UTC identified
Severity Level: [High] We're currently investigating an issue with On-Demand Cloud instance launches across multiple regions. A disruption to the creation of new Firewall Rulesets is causing instance launches to fail or enter an Alert status for customers without existing Firewall Rulesets in the affected regions. We have re-enabled launches, however customers without existing Firewall Rulesets may still experience failures in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 In the event you're unsure as to whether your service is impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Mar 4, 2026, 21:25 UTC identified
Severity Level: [High] We're currently investigating an issue with On-Demand Cloud instance launches across multiple regions. An issue with Firewall Rulesets is causing instance launches to fail or enter an Alert status for customers when creating new Firewall Rulesets in the affected regions. We have re-enabled launches, however customers without existing Firewall Rulesets may still experience failures in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 Please note that you will not be charged for an instance until it has reached a healthy boot state. In the event you're unsure as to whether your service is impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Mar 5, 2026, 18:10 UTC resolved
Severity Level: [High] Our Engineering team was able to identify and remediate the root cause of the issue. Users that were experiencing instance launch failures should no longer be impacted. In the event you're unsure as to whether your service is still impacted by this incident, please open a support ticket. We'll get back to you as soon as possible. • [https://support.lambdalabs.com/hc/en-us/requests/new](https://support.lambdalabs.com/hc/en-us/requests/new "https://support.lambdalabs.com/hc/en-us/requests/new") To be automatically notified when the status of this incident changes, please click on the "Subscribe to updates" button. Thank you for your patience and understanding during this time.
Lambda outage questions
What caused the Lambda outage on Mar 2, 2026?
The Lambda GPU Cloud status page has not published a cause. When it identified the problem (Mar 4, 2026, 18:53 UTC) it said: "Severity Level: [High] We're currently investigating an issue with On-Demand Cloud instance launches across multiple regions. A disruption to the creation of new Firewall Rulesets is causing instance launches to fail or enter an Alert status for customers without existing Firewall Rulesets in the ..."
When was the Lambda outage on Mar 2, 2026 fixed?
The Lambda GPU Cloud status page marked it resolved at Mar 5, 2026, 18:10 UTC, 2 days 19 hours after it started. A fix was in place and being monitored from Mar 3, 2026, 13:02 UTC. Its resolution note: "Severity Level: [High] Our Engineering team was able to identify and remediate the root cause of the issue. Users that were experiencing instance launch failures should no longer be impacted. In the event you're unsure as to whether your service is still impacted by this incident, please open a ..."
How long did the Lambda outage last?
About 2 days 19 hours: from Mar 2, 2026, 22:42 UTC to Mar 5, 2026, 18:10 UTC, by the official start and resolution times.
Was Lambda completely down?
The Lambda GPU Cloud status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.
Other recent Lambda incidents
- Experiencing issues with instance launches/terminations in us-west-1 Oct 12, 2026, 18:43 UTC, 2 hours 56 min
- US-SOUTH-2 Scheduled Maintenance Oct 5, 2026, 18:10 UTC, 2 hours 24 min
- US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminations Sep 23, 2026, 21:41 UTC, 2 hours 6 min
- Issue with Cloud Services API Keys Sep 10, 2026, 07:09 UTC, 8 hours 54 min
- Network Maintenance in us-east-3 Aug 18, 2026, 16:32 UTC, 7 days 22 hours
- Instances Unreachable in us-south-2 region Aug 15, 2026, 18:28 UTC, 2 days 2 hours
Full Lambda outage history and biggest outages → · Recent outages across all services →
Quotes are the Lambda GPU Cloud status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with Lambda. Times are UTC.