L
Outage recap · Lambda Labs

Lambda outage — August 3, 2026

On August 3, 2026, Lambda had a reported incident on Lambda Labs's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded Performance in us-midwest-2

minor
Started
Aug 3, 6:30 PM EDT
Resolved
Aug 25, 12:23 AM EDT
Duration
509h 53m

Lambda Labs's updates (5)

  1. investigating · Aug 3, 6:30 PM EDT

    Severity Level: Medium We’re currently investigating a potential issue with our B200 cluster performance in us-midwest-2 impacting Managed Kubernetes, and 1-Click Cluster customers. 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

  2. monitoring · Aug 7, 10:10 PM EDT

    **Severity Level:** Medium We identified an issue within the InfiniBand fabric and implemented changes to address it. Performance has returned to expected levels based on telemetry and internal testing. We are continuing to monitor for stability. 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.

  3. investigating · Aug 11, 11:47 AM EDT

    **Severity Level:** Medium We’re currently investigating a potential issue with our B200 cluster performance in us-midwest-2 impacting Managed Kubernetes, and 1-Click Cluster customers. 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.

  4. monitoring · Aug 21, 8:38 PM EDT

    **Severity Level:** Medium Performance has returned to acceptable levels based on current telemetry and internal testing. We are continuing to monitor for stability and will provide further updates as they become available. ----------------------------------------------------------------------------- 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.

  5. resolved · Aug 25, 12:23 AM EDT

    **Severity Level:** Medium Performance has returned to expected levels based on current telemetry and internal testing after monitoring health over the weekend. ----------------------------------------------------------------------------- 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 96 ms, against 96 ms over the 24 hours before. Lambda Labs posted the incident at Aug 3, 6:30 PM EDT.

Updates are Lambda Labs's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Lambda Labs. This recap summarizes incidents published on Lambda Labs's official status page.