Network Issues in us-midwest-2
none- Started
- Aug 2, 12:56 PM EDT
- Resolved
- Aug 24, 11:53 PM EDT
- Duration
- 538h 57m
Lambda Labs's updates (3)
- investigating · Aug 2, 12:56 PM EDT
**Severity Level:** Medium We’re currently investigating a potential issue with our network in us-midwest-2. Users may experience degraded egress to the internet. 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.
- monitoring · Aug 2, 3:05 PM EDT
**Severity Level:** Medium Our team has applied a fix to mitigate the network issue affecting us-midwest-2. We are currently monitoring the results to confirm full recovery. We will provide another update as soon as we have more information. 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 · Aug 24, 11:53 PM EDT
**Severity Level:** Medium The incident has been resolved. Networking in the us-midwest-2 region is confirmed restored after monitoring. ----------------------------------------------------------------------------- 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.
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 97 ms, against 87 ms over the 24 hours before. Lambda Labs posted the incident at Aug 2, 12:56 PM EDT.
Updates are Lambda Labs's own words from its status page (status: resolved); we never add an inferred cause.