Power event impacting us-southeast-1 connectivity
none- Started
- Nov 18, 9:17 AM EST
- Resolved
- Nov 18, 10:34 AM EST
- Duration
- 1h 17m
Lambda Labs's updates (2)
- investigating · Nov 18, 9:17 AM EST
Severity Level: High We’re currently investigating a potential issue with our On-Demand Cloud instances in our us-southeast-1 data center. Users may experience loss of network connectivity to running instances and may be unable to launch, terminate, or manage instances in this location. 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> **To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.**
- resolved · Nov 18, 10:34 AM EST
Severity Level: Medium Power has been restored to the affected equipment in us-southeast-1, and the facility work that caused the power event has been completed. Network connectivity and our cloud management services in this region have recovered, and our teams have confirmed that the underlying infrastructure is healthy. We are continuing to monitor while our data center provider finishes restoring full power redundancy. 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> **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 15 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 157 ms, against 166 ms over the 24 hours before. Lambda Labs posted the incident at Nov 18, 9:17 AM EST.
Updates are Lambda Labs's own words from its status page (status: resolved); we never add an inferred cause.