All Systems Operational

LucidLink (North America) Operational
90 days ago
99.93 % uptime
Today
LucidLink (Latin America) Operational
90 days ago
99.93 % uptime
Today
LucidLink (Asia-Pacific) Operational
90 days ago
99.93 % uptime
Today
LucidLink (Europe) Operational
90 days ago
99.93 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Feb 17, 2026

No incidents reported today.

Feb 16, 2026

No incidents reported.

Feb 15, 2026

No incidents reported.

Feb 14, 2026

No incidents reported.

Feb 13, 2026
Resolved - 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

Feb 13, 17:22 UTC
Investigating - 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.
Feb 13, 16:03 UTC
Feb 12, 2026
Resolved - 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.
Feb 12, 15:00 UTC
Identified - 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.
Feb 12, 14:22 UTC
Monitoring - A fix has been implemented, and we are monitoring the results.
Feb 12, 13:00 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 12, 12:59 UTC
Investigating - 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.

Feb 12, 12:35 UTC
Feb 11, 2026

No incidents reported.

Feb 10, 2026
Completed - The scheduled maintenance has been completed.
Feb 10, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 10, 08:00 UTC
Scheduled - We will be undergoing maintenance to the New LucidLink WebService during this time to address an issue with clients infrequently and unexpectedly disconnecting from their filespace(s)/workspace(s). Users may experience occasional disconnections from their filespace during this window, but should be able to log back in immediately.
The LucidLink Classic service will not be affected.

Feb 9, 17:56 UTC
Feb 9, 2026

No incidents reported.

Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

Feb 6, 2026
Resolved - 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.
Feb 6, 18:30 UTC
Feb 5, 2026

No incidents reported.

Feb 4, 2026

No incidents reported.

Feb 3, 2026
Resolved - 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.

Feb 3, 12:00 UTC