lambda.ai Unreachable Due to DNS Issue
major- Started
- Oct 31, 12:35 AM EDT
- Resolved
- Oct 31, 3:07 AM EDT
- Duration
- 2h 32m
Lambda Labs's updates (3)
- investigating · Oct 31, 12:35 AM EDT
**Severity Level:** [High] We’re currently investigating a potential issue with the Cloud Dashboard. Users may experience timeouts when logging in or out of the portal. 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> To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.
- monitoring · Oct 31, 1:41 AM EDT
**Severity Level:** [High] Service is beginning to recover, though some users may continue to experience disruptions. We’re monitoring progress. 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.
- resolved · Oct 31, 3:07 AM EDT
**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. • <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.
What our checks recorded
We checked Lambda 30 times from Lambda Labs's start time to its resolution, once every five minutes. Our request could not reach Lambda on 1 of those checks. Median response time was 108 ms, against 130 ms over the 24 hours before. Lambda Labs posted the incident at Oct 31, 12:35 AM EDT; our checks first failed 25 minutes later.
Updates are Lambda Labs's own words from its status page (status: resolved); we never add an inferred cause.