Power event impacting us-southeast-1 connectivity
Severity Level: High We’re currently investigating a potential issue with our On-Demand Cloud instances in our us-southeast-1 data center. Users may experience loss of network connectivity to running instances and may be unable to launch, terminate, or manage instances in this location. 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. **To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.**
The latest update from Lambda.
State
Investigating
Started
Ongoing for
34 min
Worst impact
Notice
Timeline
1 updateInvestigating
34 min 100%
Updates
Times in UTCAs posted by Lambda
Severity Level: High We’re currently investigating a potential issue with our On-Demand Cloud instances in our us-southeast-1 data center. Users may experience loss of network connectivity to running instances and may be unable to launch, terminate, or manage instances in this location. 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. **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
10
Days with an incident
13
Median duration
2 h 56 min
This incident
81% shorter than the median
Other Lambda incidents
All incidentsLambda·Service disruption in us-east-3
Lambda reports a service disruption in the us-east-3 region. Connectivity to existing instances failed, and new instance launches were unavailable. Lambda resolved the incident. The disruption lasted about 56 minutes.
Lambda·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.
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.live/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.live/feed.xml?providers=lambda/feed subscribe https://outages.live/feed.xml?providers=lambdaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane