Resolved after 3 hours 7 minutes, affecting LucidLink (North America) and LucidLink (Latin America) and 1 more, on September 29, 2025.
We are continuing to work on a fix for this issue.
Affected components
LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Update timeline
- identified Sep 29, 2025, 05:31 PM UTC
We’ve identified the root cause of an issue with newly created 3.x filespaces being initialized in all regions. Our DevOps team is currently working hard to fix the problem. This will not impact already initialized and operating filespaces in 3.x and Classic filespace initialization is not effected. We’ll keep you posted with any updates.
- identified Sep 29, 2025, 05:34 PM UTC
We are continuing to work on a fix for this issue.
- resolved Sep 29, 2025, 06:57 PM UTC
This incident has been resolved.
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