L
Outage recap · Lambda Labs

Lambda outage — July 29, 2026

On July 29, 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.

Network issues in us-east-2

major
Started
Jul 29, 3:54 PM EDT
Resolved
Jul 30, 2:19 PM EDT
Duration
22h 25m

Lambda Labs's updates (3)

  1. investigating · Jul 29, 3:54 PM EDT

    **Severity Level:** [High] We’re currently investigating an issue with our Network traffic in us-east-2. Users may experience impact to external network connectivity to instances in the region. 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 · Jul 29, 4:12 PM EDT

    **Severity Level:** [High] Our engineers have implemented a fix to address the issue with our Networking services. Impact to customers should be fixed, but if still experiencing issues please reach out to us. 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.

  3. resolved · Jul 30, 2:19 PM EDT

    **Severity Level: High** The incident has been resolved. Networking is 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.

What our checks recorded

We checked Lambda 269 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 107 ms, against 96 ms over the 24 hours before. Lambda Labs posted the incident at Jul 29, 3:54 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.