Instances Unreachable in us-south-2 region
minor- Started
- Aug 15, 2:28 PM EDT
- Resolved
- Aug 17, 4:39 PM EDT
- Duration
- 50h 11m
Lambda Labs's updates (4)
- investigating · Aug 15, 2:28 PM EDT
Severity Level: Critical We're currently investigating a potential issue with our us-south-2 region. Users may experience an inability to reach instances in this region, including via SSH and Jupyter, and some instances may appear offline. 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.**
- investigating · Aug 15, 6:09 PM EDT
**Severity Level:** [Low/Medium/High/Critical] We're currently investigating a network issue affecting our us-south-2 region. Users may experience an inability to reach instances in this region, including via SSH and Jupyter, and some instances may appear offline. Our teams have made progress in narrowing down the cause and are actively working to mitigate and 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.
- monitoring · Aug 15, 9:12 PM EDT
**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.
- resolved · Aug 17, 4:39 PM EDT
Severity Level: [High] This incident has been resolved. The network issue affecting our us-south-2 region has been fixed, and connectivity to instances, including via SSH and Jupyter, has been fully restored. The region has remained stable since the fix was implemented. In the event you believe your service is still impacted, please open a support ticket and 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") Thank you for your patience and understanding during this time.
What our checks recorded
We checked Lambda 575 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 86 ms, against 76 ms over the 24 hours before. Lambda Labs posted the incident at Aug 15, 2:28 PM EDT.
Updates are Lambda Labs's own words from its status page (status: resolved); we never add an inferred cause.