Lambda GPU Cloud incident

Launch failures in Utah (us-west-3) region

Minor Resolved View vendor source →

Lambda GPU Cloud experienced a minor incident on February 22, 2026 affecting Virtual Machines, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 22, 2026, 03:21 PM UTC
Resolved
Feb 22, 2026, 03:21 PM UTC
Duration
Detected by Pingoru
Feb 22, 2026, 03:21 PM UTC

Affected components

Virtual Machines

Update timeline

  1. investigating Feb 22, 2026, 03:00 PM UTC

    Status: Investigating 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 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. • 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. Affected components Virtual Machines (Degraded performance)

  2. resolved Feb 22, 2026, 03:21 PM UTC

    Status: Resolved Severity Level: [Medium] The incident has been resolved. Launches in Utah (us-west-3) should now work as expected. Affected components Virtual Machines (Operational)