Lambda Labs Outage History

39 incidents recorded over the last 365 days, 36 of them resolved, 3 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Lambda Labs status72.86% uptime history

Every Recorded Lambda Labs Incident

Lambda Labs incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 18, 2026Network Maintenance in us-east-3**Severity Level:** [Low] > **Status** > Scheduled (Maintenance) > > **Summary** > We’re performing scheduled maintenance on our networking infrastructure in `us-east-3`. Brief connectivity interruptions may occur…—Investigating
Aug 15, 2026Instances Unreachable in us-south-2 regionSeverity Level: [High] This incident has been resolved. The network issue affecting our us-south-2 region has been fixed, and connectivity to instances, including via SSH and Jupyter, has been fully restored. The…50h 10mResolved
Aug 3, 2026Degraded Performance in us-midwest-2**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…—Investigating
Aug 2, 2026Network Issues in us-midwest-2**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…—Investigating
Jul 30, 2026Investigating network connectivity issues in us-east-2Severity Level: Medium The incident has been resolved. Network traffic is now working as expected.3h 2mResolved
Jul 29, 2026Network issues in us-east-2**Severity Level: High** The incident has been resolved. Networking is now working as expected.22h 25mResolved
Jul 27, 2026Multiple Regions | Launch and Termination Issues**Severity Level:** High The incident has been resolved. Launches and terminations are now working as expected.2h 58mResolved
Jul 26, 2026DAL01 - COLO Internet Connectivity Disruption (Upstream Provider)**Severity Level:** Medium The incident has been resolved. The network is now working as expected. Thank you for your patience.6h 52mResolved
Jul 2, 2026US-SOUTH-2 - Instance Launch Issues**Severity Level:** Medium The US-SOUTH-2 launch/termination issue has been resolved. Thank you for your patience and understanding during this time.59 minResolved
Jun 20, 2026US-SOUTH-2 Booting Failures of Newly Launched Instance**Severity Level:** High A fix has been implemented and we’re monitoring the results. To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button. Thank…102h 13mResolved
Jun 17, 2026Failed Launches in US-EAST-3**Severity Level:** Medium The launch issues in US-EAST-3 has been resolved. Thank you for your patience and understanding during this time.47 minResolved
Jun 4, 2026Slow Instance Launches in Certain Regions**Our team has resolved the issue impacting slow instance launches.** Thank you for your patience and understanding during this time.13 minResolved
Jun 4, 2026US-SOUTH-3 Instance Launch / Termination Issues**Severity Level:** [Medium] The incident has been resolved. US-SOUTH-3 launches and terminations are now working as expected.1h 44mResolved
May 20, 2026Launches and Terminations Failing in Multiple Regions**Severity Level:** High The incident has been resolved. Instance launches and terminations are now working as expected in the previously affected regions…3h 22mResolved
Apr 3, 2026Non-admin users are unable to launch instances.**Severity Level:** [High] The incident has been resolved. Launches for team members should now work as expected.49 minResolved
Mar 24, 2026Global Firewall Rulesets Page Not Loading**Severity Level:** Medium The incident has been resolved. The Firewall page is now working as expected.59 minResolved
Mar 19, 2026Power Maintenance Causing Loss of Power Redundancy in us-west-3**Severity Level:** [Low] The incident has been resolved.19h 11mResolved
Mar 16, 2026US-East 2 and US-East 3 placed under a tornado watch / severe weather warning all day - 3/16/25**Severity Level:** [Low] The incident has been resolved. US-East 2 and US-East 3 is now clear of severe thunderstorm and tornado watch. We will update agin if there are any changes over the next 24 hours. Thank you.7h 12mResolved
Mar 2, 2026Launches Failing in Multiple Regions**Severity Level:** [High] Our Engineering team was able to identify and remediate the root cause of the issue. Users that were experiencing instance launch failures should no longer be impacted. In the event you’re…67h 27mResolved
Feb 26, 2026Launches Disabled in Multiple Regions**Severity Level:** High Our engineers have identified the root cause and have resolved the issue. Launches are enabled on the affected regions. In the event you’re unsure as to whether your service is impacted by…21 minResolved
Feb 22, 2026Launch failures in Utah (us-west-3) region**Severity Level:** [Medium] The incident has been resolved. Launches in Utah (us-west-3) should now work as expected.20 minResolved
Feb 20, 2026Partial Outage in AUS01 (us-south-3) region**Severity Level:** [High] The incident has been resolved. Services in AUS01 (us-south-3) region is now working as expected.16h 49mResolved
Feb 14, 2026AUS01 - Power event and storage loss**Severity Level:** Critical Our engineers have identified the root cause of the issue and they’re actively working on remediation. Starbase and other storage-dependent services in us-west-3 have been restored and are…3h 31mResolved
Feb 13, 2026Launch failures in us-east-1**Severity Level:** Medium The incident has been resolved. Launches in us-east-1 should now work as expected.11h 3mResolved
Feb 10, 2026US-EAST-3 | Instances Failing to Launch**Severity Level:** [Medium] The incident has been resolved. us-east-3 launches are now working as expected.6h 45mResolved
Feb 6, 2026Unable to Launch New Instances **Severity Level:** High The incident has been resolved. Instance launches are now working as expected.21 minResolved
Jan 25, 2026Launch failures in us-east-1**Severity Level:** Low The incident has been resolved. VM launches are now working as expected in the us-east-1 region. Thank you for your patience and understanding during this time.68h 8mResolved
Jan 8, 2026Network Degradation in us-west-3**Severity Level:** Low The incident has been resolved. Networking in us-west-3 is now working as expected.22h 45mResolved
Jan 7, 2026Console shows a blank pageWe've confirmed that the console is back to consistent, normal operation, and we're closing this incident.17 minResolved
Dec 18, 2025Longer than normal instance launch and termination times in multiple regions**Severity Level:** Medium The incident has been resolved. Instance launches and terminations are now working as expected.9h 19mResolved
Dec 12, 2025Metrics graphs not visible in cloud consoleInstance metrics graphs should now be visible again for all users. Thanks for your patience!3h 14mResolved
Nov 30, 2025US-EAST-3 Instances Becoming Inaccessible**Severity Level:** [Medium] Our engineers have completed the rolling reboots so users should no longer be experiencing reboots in US-WEST-3. In the event you’re unsure as to whether your service is impacted by this…122h 5mResolved
Nov 26, 2025HTTP Error 502 from Cloud IDE in New Instances**Severity Level:** Low The incident has been resolved. The Cloud IDE of new instances is now working as expected.1h 19mResolved
Nov 24, 2025[us-east-3] Launches Temporarily Disabled**Severity Level:** Medium A fix has been implemented and we’re monitoring the results. To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button. Thank…142h 34mResolved
Nov 19, 2025S3 Gateway Connectivity Issues in us-midwest-224h 8mResolved
Nov 18, 2025Network Issues In Multiple Regions10h 3mResolved
Nov 16, 2025[US-SOUTH-2] Launch and Termination Issues 2h 31mResolved
Nov 14, 2025US-WEST-3 Network connectivity degraded due to down carrier67h 37mResolved
Oct 31, 2025Lost connectivity in SLC0116 minResolved

How to Read This Lambda Labs Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Lambda Labs acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Lambda Labs outage in this window ran 5d 22h, against a mean recovery of 22h 20m. If you depend on Lambda Labs in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.