Who is down right now

Lambda · AIFeb 22, 2026, 15:00 UTC 7 months ago

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

MinorNot disclosedUpdated 2h ago
Feb 22, 15:00 UTCFeb 22, 15:21 UTC
Duration
20m
Impact
Minor
Root cause
Not disclosed
Lambda, 90 days
9 incidents
Affected
Not listed by the vendor.
Status page

Final update

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

Timeline

  1. Resolved · Feb 22, 15:21 UTC
    **Severity Level:** [Medium] The incident has been resolved. Launches in Utah (us-west-3) should now work as expected.
  2. Investigating · Feb 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 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](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.

More from Lambda

Full history
IncidentDuration
US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and TerminationsSep 23, 21:41 UTC2h 6m
Issue with Cloud Services API KeysSep 10, 07:09 UTC8h 54m
Instances Unreachable in us-south-2 regionAug 15, 18:28 UTC2d 2h
Degraded Performance in us-midwest-2Aug 3, 22:30 UTC21d 5h
Network Issues in us-midwest-2Aug 2, 16:56 UTC22d 10h
Investigating network connectivity issues in us-east-2Jul 30, 19:46 UTC3h 3m