US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminations
Sep 23, 21:41 UTCSep 23, 23:48 UTC
Duration
2h 6m
Impact
Minor
Root cause
Not disclosed
Lambda, 90 days
9 incidents
Affected
Not listed by the vendor.
Final update
**Severity Level:** High The incident has been resolved. us-south-3 services are now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, 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") To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.
Timeline
- Resolved · Sep 23, 23:48 UTC
**Severity Level:** High The incident has been resolved. us-south-3 services are now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, 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") To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.
- Identified · Sep 23, 22:22 UTC
**Severity Level:** High We've identified that this issue is affecting the status of instances and filesystems in the us-south-3 region within the API and Console. Some users may see these resources as unhealthy when checking their dashboard and API. For clarity, the alert/unhealthy status is a display issue, not a reflection of actual instance health. The underlying infrastructure is healthy. If you already have connection details for an instance in us-south-3, you can continue to access it normally. We're continuing to work on a resolution and will provide another update as soon as we have one. Thank you for your patience. ----------------------------------------------------------------------------- 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 · Sep 23, 21:41 UTC
**Severity Level:** Medium We’re currently investigating a potential issue with our us-south-3 region. Users may experience instance launches and terminations in a stuck state. 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 history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1007:09 UTC4 weeks ago | Issue with Cloud Services API KeysSep 10, 07:09 UTC | major | 8h 54m |
| Aug 1518:28 UTC7 weeks ago | Instances Unreachable in us-south-2 regionAug 15, 18:28 UTC | minor | 2d 2h |
| Aug 322:30 UTC2 months ago | Degraded Performance in us-midwest-2Aug 3, 22:30 UTC | minor | 21d 5h |
| Aug 216:56 UTC2 months ago | Network Issues in us-midwest-2Aug 2, 16:56 UTC | none | 22d 10h |
| Jul 3019:46 UTC2 months ago | Investigating network connectivity issues in us-east-2Jul 30, 19:46 UTC | minor | 3h 3m |
| Jul 2919:54 UTC2 months ago | Network issues in us-east-2Jul 29, 19:54 UTC | major | 22h 25m |