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.
State
Resolved
Started
Lasted
1 h 19 min
Worst impact
Notice
Timeline
2 updatesInvestigating
1 h 19 min 100%
Updates
Times in UTCAs posted by Lambda
Severity Level: Medium This incident has been resolved. Between approximately 15:31 and 16:27 UTC, a fault in network equipment in the us-east-3 region disrupted some connectivity to instances in the region. Our teams found the cause and applied a fix. Service has been fully restored, and we have monitored the region since then to confirm it is stable. We’re also working on follow-up actions to prevent this from happening again. We apologize for the disruption and thank you for your patience. --- If you’re experiencing issues with your instances in us-east-3, please open a support ticket and we’ll get back to you as soon as possible.
Severity Level: Medium We’re currently investigating a potential issue with our On-Demand Cloud in the us-east-3 region. Users may experience connectivity issues with existing instances in us-east-3. Launching new instances in the region is currently unavailable. 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
23
Median duration
5 h 55 min
This incident
78% shorter than 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.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