Instances Unreachable in us-south-2 region
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.
The latest update from Lambda.
State
Resolved
Started
78 d ago
2026-08-15 18:28 UTC
Lasted
2 days
until 2026-08-17 20:39 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
6 h 44 min 13%
Monitoring
43 h 27 min 87%
Updates
Times in UTCAs posted by Lambda
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.
**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 you for your patience and understanding during this time.
**Severity Level:** [Low/Medium/High/Critical] We're currently investigating a network issue affecting our us-south-2 region. Users may experience an inability to reach instances in this region, including via SSH and Jupyter, and some instances may appear offline. Our teams have made progress in narrowing down the cause and are actively working to mitigate and 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.
Severity Level: Critical We're currently investigating a potential issue with our us-south-2 region. Users may experience an inability to reach instances in this region, including via SSH and Jupyter, and some instances may appear offline. 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.**
Lambda in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
28
Median duration
8 h 54 min
This incident
5.6× the median
Other Lambda incidents
All incidentsLambda·lambda.ai Unreachable Due to DNS Issue
**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.
Lambda·Experiencing issues with instance launches/terminations in us-west-1
**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.
Lambda·US-SOUTH-2 Scheduled Maintenance
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.
Lambda·US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminations
**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.
Lambda·Issue with Cloud Services API Keys
**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.
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.
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.
https://outages.cc/feed.xml?providers=lambda/feed subscribe https://outages.cc/feed.xml?providers=lambdaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane