outages.live
Live
L

Lambda

Lambda is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

28

Median duration

8 h 54 min

Longest incident

22 days

Components

10
Website Operational
90 days agoNo incidentsToday
Cloud API Operational
90 days agoNo incidentsToday
Chat Completions API Operational
90 days agoNo incidentsToday
Network Operational
90 days agoNo incidentsToday
Virtual Machines Operational
90 days agoNo incidentsToday
Storage Operational
90 days agoNo incidentsToday
Power Operational
90 days agoNo incidentsToday
Cloudflare Tunnel Operational
90 days agoNo incidentsToday
Cloudflare API Operational
90 days agoNo incidentsToday
Cloudflare CDN/Cache Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 31, 2026

Duration2 h 32 min04:35 to 07:07lambda.ai Unreachable Due to DNS IssuePartial outage

**Severity Level:** [High] The incident has been resolved. [lambda.ai](http://lambda.ai) 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. • To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

Oct 12, 2026

Duration2 h 56 min18:43 to 21:39Experiencing issues with instance launches/terminations in us-west-1Notice

**Severity Level:** High Instance launches and terminations in us-west-1 are now operational. 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.

Oct 5, 2026

Duration2 h 24 min18:10 to 20:34US-SOUTH-2 Scheduled MaintenanceNotice

The us-south-2 power maintenance is now complete. ----------------------------------------------------------------------------- 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.

Sep 23, 2026

Duration2 h 6 min21:41 to 23:48US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and TerminationsDegraded

**Severity Level:** High The incident has been resolved. us-south-3 services are 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.

Sep 10, 2026

Duration8 h 54 min07:09 to 16:03Issue with Cloud Services API KeysPartial outage

**Severity Level:** High This incident has been resolved. The issue preventing users from viewing and creating Cloud Service API keys has been fixed, and API key functionality has been fully restored. We have continued monitoring since the fix was deployed and confirmed the service is operating normally. No action is required on your part. Existing API keys were not affected by this incident. Thank you for your patience and understanding during this time.

Aug 18, 2026

Duration8 days16:32 to 14:05Network Maintenance in us-east-3Notice

Severity Level: [Low] Status Completed (Maintenance) Summary The scheduled maintenance on our networking infrastructure in `us-east-3` has been completed successfully. Service health was monitored throughout the work and all systems are operating normally. Thank you for your patience. ----------------------------------------------------------------------------- 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.

Aug 15, 2026

Duration2 days18:28 to 20:39Instances Unreachable in us-south-2 regionDegraded

Severity 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 region has remained stable since the fix was implemented. In the event you believe your service is still impacted, 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") Thank you for your patience and understanding during this time.

Aug 3, 2026

Duration21 days22:30 to 04:23Degraded Performance in us-midwest-2Degraded

**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.

Aug 2, 2026

Duration22 days16:56 to 03:53Network Issues in us-midwest-2Notice

**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.

Follow Lambda

Your coding agent knows when Lambda is down, and tells you when a failure is theirs, not yours. You can also get Lambda incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "lambda" and tell me if Lambda has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=lambda
Slack
/feed subscribe https://outages.cc/feed.xml?providers=lambda

Go from tracking outages to fixing production issues with Polylane.

Try Polylane