IBM connectivity issues
Affected: LucidLink (Europe)
LucidLink Outage History
LucidLink is up right nowLucidLink had 22 outages in the last 2 years totaling 286h 22m of downtime — averaging 0.9 incidents per month.
There were 22 LucidLink outages since August 6, 2024 totaling 286h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.
Connectivity issues in India region
Affected: LucidLink (Asia-Pacific)
Timeline · 1 update
- resolved Feb 27, 2026, 10:40 PM UTC
Customers may have experienced issues connecting to filespaces in the India region caused by an upstream ISP. The issue started at 19.30 and finished by 21:10 UTC.
New LucidLink connection and login Issues
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 2 updates
- investigating Feb 13, 2026, 04:03 PM UTC
We are investigating a critical issue with our New LucidLink Webservice. Users are currently unable to log in to the New LucidLink application, and those with active sessions are experiencing disconnections from their filespaces.
- resolved Feb 13, 2026, 05:22 PM UTC
The critical issue with our New LucidLink Webservice has been identified and resolved. Users should now be able to log in to the New LucidLink application. Any users who are still receiving messages that the service is unreachable, please submit a support ticket with us to investigate. https://support.lucidlink.com/hc/en-us/requests/new
Filespace Creation Issues
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 5 updates
- investigating Feb 12, 2026, 12:35 PM UTC
We have identified an issue preventing the creation of New LucidLink filespaces. While existing filespaces remain fully accessible and functional, the provisioning of new filespaces is currently not possible. Our engineering team is actively working to identify the root cause and restore full functionality as quickly as possible.
- identified Feb 12, 2026, 12:59 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 12, 2026, 01:00 PM UTC
A fix has been implemented, and we are monitoring the results.
- identified Feb 12, 2026, 02:22 PM UTC
We have identified the root cause affecting New LucidLink filespace creation and are currently deploying a fix. During this deployment, the ability to create new filespaces will remain temporarily unavailable.
- resolved Feb 12, 2026, 05:09 PM UTC
The issue preventing the creation of New LucidLink filespaces has been resolved. A network failure exposed a bug affecting 3.x filespace creation. DevOps was able to resolve the issue and restore service and new filespaces are now being created successfully. We will continue monitoring the service for any issues - please create a Support ticket if you experience any problems creating a new filespace.
Emergency maintenance of 3.0 WebService Database
Timeline · 1 update
- resolved Feb 09, 2026, 05:50 PM UTC
Our Engineering team identified an area in our webservice backend that required an emergency maintenance downtime to fix. Customers may have experienced short disconnect from the filespace in their clients but should have been able to reconnect without further incident.
Service Disruption: New LucidLink Web Service
Timeline · 1 update
- resolved Feb 03, 2026, 01:32 PM UTC
Resolved – Between 12:20 PM and 12:25 PM UTC, a deployment of our New LucidLink web service caused a brief service interruption. During this 5-minute window, active users were disconnected from their workspaces, and new logins were unavailable. Our team has stabilized the service, and all systems are now performing normally. We are conducting a thorough review of our deployment process to ensure this does not happen again. We apologize for the disruption to your workflow.
LucidLink Service Disruption
Timeline · 1 update
- resolved Nov 20, 2025, 11:38 PM UTC
There was a few-minute disruption of the LucidLink service around 20.45 UTC. The service is now operational.
AWS outage impacting LucidLink
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 3 updates
- identified Oct 20, 2025, 09:54 AM UTC
Amazon Web Services (AWS) is currently experiencing a major outage in the US-EAST-1 region. This global AWS issue is causing increased error rates and latency across multiple AWS services, which may impact access to LucidLink for some users. Our engineering and operations teams are actively monitoring the situation and working closely with AWS to restore normal performance as soon as possible. We’ll continue to share updates as AWS provides more information. Thank you for your patience. We know how critical uptime is for your workflows, and we’re doing everything possible to minimize disruption.
- monitoring Oct 20, 2025, 10:43 AM UTC
Earlier today, a major outage in the AWS US-EAST-1 region temporarily affected parts of LucidLink’s Classic environment. For about 30–35 minutes, some Classic users may have been unable to log in to their filespaces. No data or connected users were affected: Anyone already logged in remained fully connected and continued working without interruption. No performance degradation was observed or reported on the new LucidLink: all systems continue to operate normally. Thanks for your patience while we worked through today’s AWS outage. Service is fully restored and running as expected.
- resolved Oct 21, 2025, 08:37 AM UTC
This incident has been resolved.
Release 3.3.7372 - macOS connectivity issues
Timeline · 1 update
- resolved Oct 06, 2025, 01:03 PM UTC
We published a release today (3.3.7372) and had reports that users were unable to reconnect to their filespace following the update. As such, we have pulled the release from our website while we investigate what has caused this. This appears to affect macOS only and only certain configurations. The advice for anyone affected is to follow the steps below: 1. Quit the LucidLink application completely 2. Download the previous release from our website, which is now the latest public release: https://www.lucidlink.com/download/new-ll-latest/macos/stable/ 3. Delete `/Applications/LucidLink.app` Please note, this does not delete or affect any data in your filespace. 4. Install from the `lucidlink-3.3.7297.pkg` 5. Reconnect to your filespace. If you have any issues, please raise a support ticket with us.
Issue with initializing new 3.x filespaces
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 3 updates
- 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.
New LucidLink service issue
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 2 updates
- monitoring Sep 26, 2025, 07:44 AM UTC
Our New LucidLink webservice experienced an issue earlier today that resulted in users getting disconnected from their filespaces and not being able to log back in. We found the root cause and applied a fix. We are currently monitoring the status of the service, but users should be able to log back in and continue working.
- resolved Sep 26, 2025, 08:16 AM UTC
The issue was identified and fixed, and normal service was restored at 10:36 UTC. We continued to monitor the status following successful reports of logins, which now confirm the issue is resolved.
LucidLink Classic Service Outage
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 3 updates
- investigating Sep 02, 2025, 01:23 PM UTC
We are currently investigating an outage affecting the discovery service for Classic filespaces. Users may be unable to connect to their filespaces. We are actively working to restore service and will provide updates as more information becomes available.
- monitoring Sep 02, 2025, 01:39 PM UTC
We've identified the issue and applied a fix. We're now monitoring the service to ensure full recovery.
- resolved Sep 02, 2025, 06:47 PM UTC
Our team has confirmed the issue with the discovery service for Classic filespaces is fully resolved. If you continue to experience any problems, please open a support ticket at https://support.lucidlink.com/. Thanks for your patience during this incident!
Wasabi connectivity issues
Affected: LucidLink (Europe)
Timeline · 3 updates
- investigating Jul 08, 2025, 12:57 PM UTC
Customers with Wasabi filespaces in eu-central-2 region are experiencing degraded performance. Wasabi is working on identifying the issue: https://status.wasabi.com/incidents/cg1kq94vj8k1
- identified Jul 08, 2025, 01:12 PM UTC
The Wasabi Operations Team is working to restore services in the region. Customers may continue to experience issues with their Wasabi-backed filespaces in the eu-central-2 region.
- resolved Jul 08, 2025, 10:06 PM UTC
Wasabi has resolved this issue and EU-CENTRAL-2 region is now fully operational. The Wasabi Operations Team will continue to monitor the service, and LucidLink customers with Wasabi-backed filespaces in the region should experience normal operation.
Google Cloud Platform connectivity issues
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 3 updates
- identified Jun 12, 2025, 07:33 PM UTC
Customers with GCP backed filespaces have reported issues connecting or staying connected to their filespaces. GCP reports a system-wide outage at https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW that they are currently mitigating and that may already be resolved in some regions. We will monitor their status and update ours as they report on it. Here is their last update: Summary: Multiple GCP products are experiencing Service issues with API requests Description We are experiencing service issues with multiple GCP products beginning at Thursday, 2025-06-12 10:51 PDT.
- monitoring Jun 12, 2025, 07:59 PM UTC
GCP Update - 12 Jun 2025 12:41 PDT Our engineers have identified the root cause and have applied appropriate mitigations. While our engineers have confirmed that the underlying dependency is recovered in all locations except us-central1, we are aware that customers are still experiencing varying degrees of impact on individual google cloud products. All the respective engineering teams are actively engaged and working on service recovery. We do not have an ETA for full service recovery.
- resolved Jun 12, 2025, 10:56 PM UTC
All services appear to be operational. Please open a support request with us if you have a GCP-backed filespace that is still having problems. Here is the latest update from Google: GCP Update - 12 Jun 2025 14:23 PDT Most of the Google Cloud products have confirmed full service recovery. A few services are still seeing some residual impact and the respective engineering teams are actively working on recovery of those services. We expect the recovery to complete in less than an hour.
Wasabi connectivity issues in eu-central-1
Affected: LucidLink (Europe)
Timeline · 4 updates
- investigating Apr 04, 2025, 09:27 AM UTC
Customers with filespaces in the Wasabi eu-central-1 region are experiencing degraded performance since 10 AM UTC on the 4th of April, 2025. We are in contact with Wasabi and will update the status page upon progress.
- identified Apr 04, 2025, 10:47 AM UTC
Wasabi is investigating the issue: https://status.wasabi.com/incidents/9k6jnr97sdgb
- monitoring Apr 04, 2025, 12:41 PM UTC
Wasabi reported that they fixed the issue.
- resolved Apr 04, 2025, 02:01 PM UTC
This incident has been resolved.
Creation of new filespaces in US East regions is currently disabled
Affected: LucidLink (North America)
Timeline · 2 updates
- 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
Azure Blob Storage connectivity issues
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 3 updates
- investigating Dec 31, 2024, 02:26 PM UTC
Several customers reported connectivity issues in multiple regions of Azure Blob Storage. We are in contact with Microsoft and will update upon progress.
- identified Dec 31, 2024, 04:43 PM UTC
The issue has been identified as a leap year bug and our team is working on implementing a fix for a future release. In the meantime, a temporary workaround would be to set the date of the client system to one day ahead of today (1/1/2025). We expect the issue to be resolved automatically tomorrow.
- resolved Jan 01, 2025, 12:40 AM UTC
At 0:00 UTC time all Azure-backed filespaces started working normally as expected with this leap-year bug.
Wasabi connectivity issues in eu-central-2 region
Affected: LucidLink (Europe)
Timeline · 3 updates
- investigating Dec 03, 2024, 10:48 AM UTC
Several customers reported connectivity issues in Wasabi eu-central-2 region. We are in contact with Wasabi and will update upon progress.
- monitoring Dec 04, 2024, 04:18 AM UTC
Wasabi took necessary actions and we are monitoring the results.
- resolved Dec 04, 2024, 11:44 AM UTC
This incident has been resolved.
Wasabi connectivity issues affecting all regions
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 3 updates
Partial Outage for some IBM Filespaces
Affected: LucidLink (North America)LucidLink (Latin America)
Timeline · 3 updates
- investigating Oct 09, 2024, 10:27 PM UTC
Starting about 4:05pm CST we received reports of clients being disconnected from their IBM backed filespaces. It appears that there are a number of filespaces in multiple regions of IBM that are effected. Clients are unable to reach the object storage endpoint so users cannot connect or got disconnected from their filespace. IBM is aware and investigating.
- monitoring Oct 09, 2024, 10:31 PM UTC
IBM has determined the cause and implemented a fix. We are starting to receive reports that this is resolved and confirmed with our testing. Will update after confirming all effected customers have had their service restored.
- resolved Oct 09, 2024, 10:44 PM UTC
At 5:17pm CST IBM reported that the problem had been resolved. We have received numerous reports from customers that their service has been restored. We are going to mark this incident as Resolved but if you are still having any trouble connecting to your filespace, please submit a request at https://support.lucidlink.com so we can investigate.
Delayed creation of filespaces in Canada
Affected: LucidLink (North America)
Timeline · 2 updates
- identified Aug 30, 2024, 07:54 AM UTC
Customers may experience issues when trying to create filespaces in Montreal and Toronto. We are currently working on a fix.
- resolved Aug 30, 2024, 10:42 AM UTC
This incident has been resolved.
Wasabi service degradation
Affected: LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 3 updates
- investigating Aug 06, 2024, 11:10 AM UTC
Customers with Basic filespaces in Wasabi regions are experiencing degraded performance since 11 AM UTC on August 6th. Wasabi is currently investigating the root cause.
- monitoring Aug 06, 2024, 11:58 AM UTC
A fix has been implemented on Wasabi's side and we are monitoring the results.
- resolved Aug 06, 2024, 12:39 PM UTC
This incident has been resolved.