Lambda

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-12 18:43 UTC

   **Severity Level:** [High] We’re currently investigating an issue with instance launches and terminations in our us-west-1 region. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank you for your patience and understanding during...

2. resolved 2026-10-12 21:39 UTC

   **Severity Level:** High Instance launches and terminations in us-west-1 are now operational. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- In the event you’re unsure as to whether...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-05 18:10 UTC

   **Severity Level:** Low We have identified that a small portion of servers in our datacenter in us-south-2​ requires an update to their configuration in order to address some power redundancy issues. Our engineers in this datacenter are addressing this issue currently. Due to...

2. resolved 2026-10-05 20:34 UTC

   The us-south-2 power maintenance is now complete. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a support ticket and we’ll get back to you as soon...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 21:41 UTC

   **Severity Level:** Medium We’re currently investigating a potential issue with our us-south-3 region. Users may experience instance launches and terminations in a stuck state. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank you...

2. identified 2026-09-23 22:22 UTC

   **Severity Level:** High We've identified that this issue is affecting the status of instances and filesystems in the us-south-3 region within the API and Console. Some users may see these resources as unhealthy when checking their dashboard and API. For clarity, the...

3. resolved 2026-09-23 23:48 UTC

   **Severity Level:** High The incident has been resolved. us-south-3 services are now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 07:09 UTC

   **Severity Level:** High We’re currently investigating a potential issue with the Cloud Services' API keys. Users may experience errors when creating an API key from their Cloud Dashboard. Existing keys should not be affected. Our teams are actively working to identify the root...

2. investigating 2026-09-10 07:19 UTC

   **Severity Level:** High We’re currently investigating a potential issue with the Cloud Services' API keys. Users may experience errors when creating an API key from their Cloud Dashboard. Existing keys should not be affected. Our teams are actively working to identify the root...

3. identified 2026-09-10 07:55 UTC

   **Severity Level:** High We’re currently investigating a potential issue with the Cloud Services' API keys. Users may experience errors when creating an API key from their Cloud Dashboard. Existing keys should not be affected. Our teams are actively working to resolve the issue....

4. monitoring 2026-09-10 08:36 UTC

   **Severity Level:** High We have deployed a fix for the Cloud Service API keys issue and are closely monitoring the situation. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- In the...

5. resolved 2026-09-10 16:03 UTC

   **Severity Level:** High This incident has been resolved. The issue preventing users from viewing and creating Cloud Service API keys has been fixed, and API key functionality has been fully restored. We have continued monitoring since the fix was deployed and confirmed the...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-26 14:05 UTC

   Severity Level: [Low] Status Completed (Maintenance) Summary The scheduled maintenance on our networking infrastructure in `us-east-3` has been completed successfully. Service health was monitored throughout the work and all systems are operating normally. Thank you for your...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-15 18:28 UTC

   Severity Level: Critical We're currently investigating a potential issue with our us-south-2 region. Users may experience an inability to reach instances in this region, including via SSH and Jupyter, and some instances may appear offline. Our teams are actively working to...

2. investigating 2026-08-15 22:09 UTC

   **Severity Level:** [Low/Medium/High/Critical] We're currently investigating a network issue affecting our us-south-2 region. Users may experience an inability to reach instances in this region, including via SSH and Jupyter, and some instances may appear offline. Our teams have...

3. monitoring 2026-08-16 01:12 UTC

   **Severity Level:** [High] 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.

4. resolved 2026-08-17 20:39 UTC

   Severity Level: [High] This incident has been resolved. The network issue affecting our us-south-2 region has been fixed, and connectivity to instances, including via SSH and Jupyter, has been fully restored. The region has remained stable since the fix was implemented. In the...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-03 22:30 UTC

   Severity Level: Medium We’re currently investigating a potential issue with our B200 cluster performance in us-midwest-2 impacting Managed Kubernetes, and 1-Click Cluster customers. Our teams are actively working to identify the root cause and mitigate or resolve the issue....

2. monitoring 2026-08-08 02:10 UTC

   **Severity Level:** Medium We identified an issue within the InfiniBand fabric and implemented changes to address it. Performance has returned to expected levels based on telemetry and internal testing. We are continuing to monitor for stability. To be automatically notified...

3. investigating 2026-08-11 15:47 UTC

   **Severity Level:** Medium We’re currently investigating a potential issue with our B200 cluster performance in us-midwest-2 impacting Managed Kubernetes, and 1-Click Cluster customers. Our teams are actively working to identify the root cause and mitigate or resolve the issue....

4. monitoring 2026-08-22 00:38 UTC

   **Severity Level:** Medium Performance has returned to acceptable levels based on current telemetry and internal testing. We are continuing to monitor for stability and will provide further updates as they become available....

5. resolved 2026-08-25 04:23 UTC

   **Severity Level:** Medium Performance has returned to expected levels based on current telemetry and internal testing after monitoring health over the weekend. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-02 16:56 UTC

   **Severity Level:** Medium We’re currently investigating a potential issue with our network in us-midwest-2. Users may experience degraded egress to the internet. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank you for your...

2. monitoring 2026-08-02 19:05 UTC

   **Severity Level:** Medium Our team has applied a fix to mitigate the network issue affecting us-midwest-2. We are currently monitoring the results to confirm full recovery. We will provide another update as soon as we have more information. Thank you for your patience and...

3. resolved 2026-08-25 03:53 UTC

   **Severity Level:** Medium The incident has been resolved. Networking in the us-midwest-2 region is confirmed restored after monitoring. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-30 19:46 UTC

   **Severity Level:** Medium We are investigating intermittent network connectivity and increased latency affecting certain workloads in our us-east-2 region. Customers may experience slow responses, failed requests, or temporary loss of connectivity. Our engineering team is...

2. resolved 2026-07-30 22:49 UTC

   Severity Level: Medium The incident has been resolved. Network traffic is now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-29 19:54 UTC

   **Severity Level:** [High] We’re currently investigating an issue with our Network traffic in us-east-2. Users may experience impact to external network connectivity to instances in the region. Our teams are actively working to identify the root cause and mitigate or resolve the...

2. monitoring 2026-07-29 20:12 UTC

   **Severity Level:** [High] Our engineers have implemented a fix to address the issue with our Networking services. Impact to customers should be fixed, but if still experiencing issues please reach out to us. Thank you for your patience and understanding during this time....

3. resolved 2026-07-30 18:19 UTC

   **Severity Level: High** The incident has been resolved. Networking is now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 08:46 UTC

   **Severity Level:** High We’re currently investigating a potential issue with our launches and termination from multiple regions. Users may experience their machines being stalled while booting up or terminating. Our teams are actively working to identify the root cause and...

2. monitoring 2026-07-27 11:30 UTC

   **Severity Level:** High We’re currently investigating a potential issue with our launches and termination from multiple regions. Users may experience their machines being stalled while booting up or terminating. Services have been restarted and the launches are enabled again....

3. resolved 2026-07-27 11:45 UTC

   **Severity Level:** High The incident has been resolved. Launches and terminations are now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this,...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-26 18:48 UTC

   **Severity Level:** Medium DAL01 - COLO Internet Connectivity Disruption (Upstream Provider) We are currently investigating a loss of internet connectivity affecting colocation customers in our DAL01 (Dallas) facility. The disruption is due to a down Dedicated Internet Access...

2. identified 2026-07-27 00:52 UTC

   **Severity Level: Medium** DAL01 - COLO Internet Connectivity Disruption (Upstream Provider) We continue to work with our upstream provider to resolve the DIA circuit outage affecting DAL01. Our team is actively engaged and we're in regular contact as we work toward restoration....

3. resolved 2026-07-27 01:41 UTC

   **Severity Level:** Medium The incident has been resolved. The network is now working as expected. Thank you for your patience. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-02 04:39 UTC

   **Severity Level:** Medium We’re currently investigating a potential issue with instance launching in the US-SOUTH-2 region. Users may experience boot/termination failures. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank you for...

2. resolved 2026-07-02 05:38 UTC

   **Severity Level:** Medium The US-SOUTH-2 launch/termination issue has been resolved. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-20 06:51 UTC

   **Severity Level:** [Medium] We're currently investigating a potential issue in the US-SOUTH-2 region. Users may experience slow booting of newly launched instance. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank you for your...

2. investigating 2026-06-23 13:46 UTC

   **Severity Level:** [High] We’re currently investigating an issue with our [SERVICE]. Users are experiencing [specific impact]. Our teams are actively working to identify the root cause and mitigate or resolve the issue. New instance launches in [SERVICE] have been temporarily...

3. investigating 2026-06-23 13:49 UTC

   **Severity Level:** [Low/Medium/High/Critical] We’re currently investigating a potential issue in US-SOUTH-2. Users are experience new instance launch failing to boot. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Currently new...

4. monitoring 2026-06-23 14:38 UTC

   **Severity Level:** [High] Our engineers have pushed a fix to remediate the problem of new instance launches failing to boot in US-SOUTH-2. New instance launches have now been reactivated for this region. Our engineers will continue to monitor this issue closely. Thank you for...

5. resolved 2026-06-24 13:04 UTC

   **Severity Level:** High 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.

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-17 08:29 UTC

   **Severity Level:** Medium We’re currently investigating a potential issue with the instance launches. Users may experience their US-EAST-3 instances going into Alert at launch. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank...

2. resolved 2026-06-17 09:17 UTC

   **Severity Level:** Medium The launch issues in US-EAST-3 has been resolved. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your service is...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-04 19:31 UTC

   **Severity Level:** High We’re currently investigating a potential issue with our instance launches. Users may experience slower than normal instance launches in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-cental-1 •...

2. resolved 2026-06-04 19:45 UTC

   **Our team has resolved the issue impacting slow instance launches.** Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your service was impacted...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-04 04:11 UTC

   **Severity Level:** [Medium] We’re currently investigating a potential issue in the US-SOUTH-3 region. Users may experience failures when launching and terminating instances. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank you...

2. monitoring 2026-06-04 05:18 UTC

   **Severity Level:** [Medium] We’re currently investigating a potential issue in the US-SOUTH-3 region. Users may experience failures when launching and terminating instances. We have rolled out a fix and are currently monitoring the progress. Thank you for your patience and...

3. resolved 2026-06-04 05:55 UTC

   **Severity Level:** [Medium] The incident has been resolved. US-SOUTH-3 launches and terminations are now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-20 01:08 UTC

   **Severity Level:** High We are currently investigating an issue affecting the Cloud Dashboard. Some users may experience delays when launching or terminating instances. We will provide an update as soon as more information is available. Instance Launches and Terminations have...

2. identified 2026-05-20 01:28 UTC

   **Severity Level:** High We've identified the cause of the issue and our engineers are working to restore services at this moment. Some users may experience delays when launching or terminating instances. We will provide an update as soon as more information is available....

3. resolved 2026-05-20 04:30 UTC

   **Severity Level:** High We've identified the cause of the issue and our engineers are working to restore services at this moment. Some users may experience delays when launching or terminating instances. We will provide an update as soon as more information is available....

4. resolved 2026-05-21 03:46 UTC

   **Severity Level:** High The incident has been resolved. Instance launches and terminations are now working as expected in the previously affected regions below: asia-northeast-1 asia-northeast-2 asia-south-1 australia-east-1 europe-central-1 me-west-1 us-east-1 us-midwest-1...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-03 11:43 UTC

   **Severity Level:** [High] We're currently investigating a potential issue with our cloud portal. Non-admin users may experience the Launch Instance page failing to load. As a workaround, please ask an admin user to launch the instance on your behalf. Our teams are actively...

2. resolved 2026-04-03 12:32 UTC

   **Severity Level:** [High] The incident has been resolved. Launches for team members should now work as expected. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your service is impacted by this incident,...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-24 23:16 UTC

   **Severity Level:** Medium We’re currently investigating a potential issue with our Firewall rulesets page on our Cloud Dashboard. Users may experience an error that "something went wrong" when viewing the page. Our teams are actively working to identify the root cause and...

2. identified 2026-03-24 23:47 UTC

   **Severity Level:** Medium We’re currently investigating a potential issue with our Firewall rulesets page on our Cloud Dashboard. Users may experience an error that "something went wrong" when viewing the page. We've identified the issue and will be implementing a fix shortly....

3. monitoring 2026-03-24 23:48 UTC

   **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.

4. resolved 2026-03-25 00:15 UTC

   **Severity Level:** Medium The incident has been resolved. The Firewall page is now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-19 20:12 UTC

   **Severity Level:** [Low] A scheduled power maintenance is being conducted tonight, 03/19/26, in the us-west-3 region. This will cause a loss of power redundancy, but is not expected to cause any customer impact for our On-Demand Cloud customers. Thank you for your patience and...

2. resolved 2026-03-20 15:23 UTC

   **Severity Level:** [Low] The incident has been resolved. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a support ticket and we’ll get back to you...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-03-16 16:00 UTC

   **Severity Level:** [Low] We’re currently experiencing severe weather warnings and a tornado watch near US-East 2 and US-East 3. No impact is expected and we will continue monitoring for any interruptions in service. We will update this page again is there are any status...

2. resolved 2026-03-16 23:12 UTC

   **Severity Level:** [Low] The incident has been resolved. US-East 2 and US-East 3 is now clear of severe thunderstorm and tornado watch. We will update agin if there are any changes over the next 24 hours. Thank you....

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (Bahrain): Region Availability.

1. investigating 2026-03-02 22:42 UTC

   **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...

2. monitoring 2026-03-03 13:02 UTC

   **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.

3. investigating 2026-03-03 18:40 UTC

   **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...

4. investigating 2026-03-03 19:22 UTC

   **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 •...

5. investigating 2026-03-03 23:36 UTC

   **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...

6. investigating 2026-03-04 18:37 UTC

   **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 •...

7. identified 2026-03-04 18:53 UTC

   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...

8. identified 2026-03-04 21:25 UTC

   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...

9. resolved 2026-03-05 18:10 UTC

   **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...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-02-26 04:55 UTC

   **Severity Level:** High We’re currently investigating a potential issue with launching /terminating instances these regions: us-east-1 us-midwest-1 europe-central-1 asia-northeast-1 asia-northeast-2 australia-east-1 Users may experience launch/termination failures. Our...

2. identified 2026-02-26 05:02 UTC

   > Severity Level: High > > We’re currently investigating a potential issue with launching /terminating instances these regions: > > us-east-1 > us-midwest-1 > us-west-1 > us-west-2 > europe-central-1 > asia-northeast-1 > asia-northeast-2 > australia-east-1 > > Users may...

3. resolved 2026-02-26 05:16 UTC

   **Severity Level:** High Our engineers have identified the root cause and have resolved the issue. Launches are enabled on the affected regions. 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...

Excerpts are shortened. Read the full incident on Lambda's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-22 15:00 UTC

   **Severity Level:** [Medium] We’re currently investigating a potential issue with VM launches in our On-Demand Cloud services at Utah (us-west-3) region. Users may experience newly launched instances going into "Alert" status. Our engineers are actively working to identify the...

2. resolved 2026-02-22 15:21 UTC

   **Severity Level:** [Medium] The incident has been resolved. Launches in Utah (us-west-3) should now work as expected.

Excerpts are shortened. Read the full incident on Lambda's status page.