US-SOUTH-2 Booting Failures of Newly Launched Instance
Jun 20, 06:51 UTCJun 24, 13:04 UTC
Duration
4d 6h
Impact
Minor
Root cause
Not disclosed
Lambda, 90 days
7 incidents
Affected
Not listed by the vendor.
Final update
**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.
Timeline
- Resolved · Jun 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.
- Monitoring · Jun 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 your patience and understanding during this time. ----------------------------------------------------------------------------- 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.
- Investigating · Jun 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 instance launches in US-SOUTH-2 have been temporarily disabled until the issue has been remediated. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- 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.
- Investigating · Jun 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 disabled. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- 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.
- Investigating · Jun 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 patience and understanding during this time. ----------------------------------------------------------------------------- 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.
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