Launch failures in Utah (us-west-3) region
Feb 22, 15:00 UTCFeb 22, 15:21 UTC
Duration
20m
Impact
Minor
Root cause
Not disclosed
Lambda, 90 days
7 incidents
Affected
Not listed by the vendor.
Final update
**Severity Level:** [Medium] The incident has been resolved. Launches in Utah (us-west-3) should now work as expected.
Timeline
- 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.
- 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 historyPower event impacting us-southeast-1 connectivitylasted 1h 17mService disruption in us-east-3lasted 1h 19mlambda.ai Unreachable Due to DNS Issuelasted 2h 32mDegraded instance launches and terminations in us-east-3lasted 0mExperiencing issues with instance launches/terminations in us-west-1lasted 2h 56mUS-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminationslasted 2h 6m