LucidLink incident
Creation of new filespaces in US East regions is currently disabled
Resolved after 3 hours 31 minutes, affecting LucidLink (North America), on February 25, 2025.
Our infrastructure provider has resolved the problem creating new metadata service machines in the US East region. We have re-enabled all impacted storage regions. If you have any problems creating new filespaces in the US East region, please submit a request at https://support-classic.lucidlink.com
Affected components
Update timeline
- identified Feb 25, 2025, 04:42 PM UTC
Our infrastructure provider is currently having problems creating new filespace metadata service machines in the US East region so you will find the affected storage regions disabled in the Classic Web Portal and New LucidLink applications. This includes AWS backed storage in North Virginia and Ohio, and IBM backed storage in Dallas and Washington DC as well Classic Custom filespaces. We will re-enable this functionality as soon as the infrastructure provider has resolved this problem.
- resolved Feb 25, 2025, 08:14 PM UTC
Our infrastructure provider has resolved the problem creating new metadata service machines in the US East region. We have re-enabled all impacted storage regions. If you have any problems creating new filespaces in the US East region, please submit a request at https://support-classic.lucidlink.com
Your product runs on more than LucidLink
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services