Failed Launches in US-EAST-3
Jun 17, 08:29 UTCJun 17, 09:17 UTC
Duration
47m
Impact
Informational
Root cause
Not disclosed
Lambda, 90 days
9 incidents
Affected
Not listed by the vendor.
Final update
**Severity Level:** Medium The launch issues in US-EAST-3 has been resolved. 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.
Timeline
- Resolved · Jun 17, 09:17 UTC
**Severity Level:** Medium The launch issues in US-EAST-3 has been resolved. 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.
- Investigating · Jun 17, 08:29 UTC
**Severity Level:** Medium We’re currently investigating a potential issue with the instance launches. Users may experience their US-EAST-3 instances going into Alert at launch. 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.
More from Lambda
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2321:41 UTC2 weeks ago | US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and TerminationsSep 23, 21:41 UTC | minor | 2h 6m |
| Sep 1007:09 UTC4 weeks ago | Issue with Cloud Services API KeysSep 10, 07:09 UTC | major | 8h 54m |
| Aug 1518:28 UTC7 weeks ago | Instances Unreachable in us-south-2 regionAug 15, 18:28 UTC | minor | 2d 2h |
| Aug 322:30 UTC2 months ago | Degraded Performance in us-midwest-2Aug 3, 22:30 UTC | minor | 21d 5h |
| Aug 216:56 UTC2 months ago | Network Issues in us-midwest-2Aug 2, 16:56 UTC | none | 22d 10h |
| Jul 3019:46 UTC2 months ago | Investigating network connectivity issues in us-east-2Jul 30, 19:46 UTC | minor | 3h 3m |