US-SOUTH-2 - Instance Launch Issues
minor- Started
- Jul 2, 12:39 AM EDT
- Resolved
- Jul 2, 1:38 AM EDT
- Duration
- 59 min
Lambda Labs's updates (2)
- investigating · Jul 2, 12:39 AM EDT
**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 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.
- resolved · Jul 2, 1:38 AM EDT
**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 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.
What our checks recorded
We checked Lambda 12 times from Lambda Labs's start time to its resolution, once every five minutes. Every one of them reached Lambda's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 93 ms, against 92 ms over the 24 hours before. Lambda Labs posted the incident at Jul 2, 12:39 AM EDT.
Updates are Lambda Labs's own words from its status page (status: resolved); we never add an inferred cause.