LucidLink incident

Issue with initializing new 3.x filespaces

Minor Resolved View vendor source →

LucidLink experienced a minor incident on September 29, 2025 affecting LucidLink (North America) and LucidLink (Latin America) and 1 more component, lasting 3h 7m. The incident has been resolved; the full update timeline is below.

Started
Sep 29, 2025, 02:46 PM UTC
Resolved
Sep 29, 2025, 05:54 PM UTC
Duration
3h 7m
Detected by Pingoru
Sep 29, 2025, 02:46 PM UTC

Affected components

LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)

Update timeline

  1. 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.

  2. identified Sep 29, 2025, 05:34 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Sep 29, 2025, 06:57 PM UTC

    This incident has been resolved.