Lambda outage history
We hold 28 Lambda incidents from Lambda Labs's status page, the newest from Nov 18, 2026. 28 of the 28 listed carry Lambda Labs's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.
Uptime & history
Tracking since Jun 22, 2026% of our checks that found Lambda fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.
- Power event impacting us-southeast-1 connectivityNov 18, 2026 → Nov 18, 2026 · resolved
- Service disruption in us-east-3Nov 7, 2026 → Nov 7, 2026 · resolved
- lambda.ai Unreachable Due to DNS IssueOct 31, 2026 → Oct 31, 2026 · resolved
- Degraded instance launches and terminations in us-east-3Oct 28, 2026 → Oct 28, 2026 · resolved
- Experiencing issues with instance launches/terminations in us-west-1Oct 12, 2026 → Oct 12, 2026 · resolved
- US-SOUTH-2 Scheduled MaintenanceOct 5, 2026 → Oct 5, 2026 · resolved
- US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and TerminationsSep 23, 2026 → Sep 23, 2026 · resolved
- Issue with Cloud Services API KeysSep 10, 2026 → Sep 10, 2026 · resolved
- Network Maintenance in us-east-3Aug 18, 2026 → Aug 26, 2026 · resolved
- Instances Unreachable in us-south-2 regionAug 15, 2026 → Aug 17, 2026 · resolved
- Degraded Performance in us-midwest-2Aug 3, 2026 → Aug 25, 2026 · resolved
- Network Issues in us-midwest-2Aug 2, 2026 → Aug 24, 2026 · resolved
How Lambda fails
Since Jul 2, 2026, Lambda Labs's status page has marked 4 Lambda components as impaired, across 12,374 of our five-minute readings. Virtual Machines accounts for the most: 6,596 readings (about 550 hours) on 27 days, most recently on Sep 23, 2026. Next is Network, with 5,632 readings on 24 days. We hold 28 Lambda incidents from Lambda Labs's status page, the earliest from Feb 25, 2026. Of the 27 that Lambda Labs closed with an end time, the median lasted 2 h 59 min.
| Component | Outage | Degraded | Maint. | Days | Last |
|---|---|---|---|---|---|
| Virtual Machines | — | 6596 | — | 27 | Sep 23, 2026 |
| Network | — | 5632 | — | 24 | Sep 23, 2026 |
| Cloud API | — | 123 | — | 2 | Sep 23, 2026 |
| Website | — | 23 | — | 1 | Oct 31, 2026 |
Incidents by month: Jun 2026: 4 · Jul 2026: 5 · Aug 2026: 4 · Sep 2026: 2 · Oct 2026: 4 · Nov 2026: 2
Counts are five-minute readings of Lambda Labs's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.
Every recorded incident
November 2026 · 2
- Nov 18, 2026Power event impacting us-southeast-1 connectivitynone1 h 17 min2 updates
- Nov 7, 2026Service disruption in us-east-3none1 h 19 min2 updates
October 2026 · 4
- Oct 31, 2026lambda.ai Unreachable Due to DNS Issuemajor2 h 32 min3 updates
- Oct 28, 2026Degraded instance launches and terminations in us-east-3none—1 update
- Oct 12, 2026Experiencing issues with instance launches/terminations in us-west-1none2 h 56 min2 updates
- Oct 5, 2026US-SOUTH-2 Scheduled Maintenancenone2 h 24 min2 updates
September 2026 · 2
- Sep 23, 2026US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminationsminor2 h 6 min3 updates
- Sep 10, 2026Issue with Cloud Services API Keysmajor8 h 54 min5 updates
August 2026 · 4
- Aug 18, 2026Network Maintenance in us-east-3none189 h 33 min1 update
- Aug 15, 2026Instances Unreachable in us-south-2 regionminor50 h 11 min4 updates
- Aug 3, 2026Degraded Performance in us-midwest-2minor509 h 53 min5 updates
- Aug 2, 2026Network Issues in us-midwest-2none538 h 57 min3 updates
July 2026 · 5
- Jul 30, 2026Investigating network connectivity issues in us-east-2minor3 h 3 min2 updates
- Jul 29, 2026Network issues in us-east-2major22 h 25 min3 updates
- Jul 27, 2026Multiple Regions | Launch and Termination Issuesminor2 h 59 min3 updates
- Jul 26, 2026DAL01 - COLO Internet Connectivity Disruption (Upstream Provider)minor6 h 53 min3 updates
- Jul 2, 2026US-SOUTH-2 - Instance Launch Issuesminor59 min2 updates
June 2026 · 4
- Jun 20, 2026US-SOUTH-2 Booting Failures of Newly Launched Instanceminor102 h 13 min5 updates
- Jun 17, 2026Failed Launches in US-EAST-3none47 min2 updates
- Jun 4, 2026Slow Instance Launches in Certain Regionsminor14 min2 updates
- Jun 4, 2026US-SOUTH-3 Instance Launch / Termination Issuesminor1 h 44 min3 updates
May 2026 · 1
- May 19, 2026Launches and Terminations Failing in Multiple Regionsminor3 h 23 min4 updates
April 2026 · 1
- Apr 3, 2026Non-admin users are unable to launch instances.minor49 min2 updates
March 2026 · 4
- Mar 24, 2026Global Firewall Rulesets Page Not Loadingminor59 min4 updates
- Mar 19, 2026Power Maintenance Causing Loss of Power Redundancy in us-west-3minor19 h 11 min2 updates
- Mar 16, 2026US-East 2 and US-East 3 placed under a tornado watch / severe weather warning all day - 3/16/25none7 h 13 min2 updates
- Mar 2, 2026Launches Failing in Multiple Regionscritical67 h 28 min9 updates
February 2026 · 1
- Feb 25, 2026Launches Disabled in Multiple Regionsnone21 min3 updates
Incidents and their updates are Lambda Labs's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Lambda Labs.