Is LucidLink down?
Last checked just nowNo new incidents. 1 long-running issue listed below.
LucidLink is operational right now, apart from 1 long-running issue open since September 1, 2026. Last checked just now.
Real-time LucidLink status, recent outages, and incident history: pulled directly from LucidLink's official status page at status.lucidlink.com every 5 minutes. Pingoru tracks 4 LucidLink services and has captured 4 incidents in the last 90 days (99.72% uptime). Get email, Slack, Discord, or webhook alerts the moment LucidLink reports a new incident, free for 3 monitors, no credit card.
Active incident 1
- LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 3 updates
- monitoring · Oct 23, 2026, 05:17 PM UTC
What happened This week, security researchers disclosed that eight certificates issued by eMudhra, a third-party certificate authority (CA), were created with weak cryptographic keys. eMudhra has revoked them, and Google, Mozilla, and Apple have removed trust in them. Like other software that bundles its own list of trusted CAs, the LucidLink desktop client needs an update. LucidLink’s servers and infrastructure are not affected. How it relates to LucidLink The LucidLink desktop client includes its own list of trusted certificate authorities. In theory, an attacker positioned on your network connection who had forged one of these certificates could attempt to impersonate a server to an out-of-date client. We have seen no indication that it has been attempted against LucidLink or our customers. What are we doing LucidLink is actively working to remove the affected third-party certificates from both LucidLink 2.x / Classic and LucidLink 3.x. We will release updated desktop clients as soon as our test process is complete, likely this weekend. What’s next We appreciate your partnership and we are committed to maintaining your trust. Please look out for a follow up email as our team works to deliver this patch asap. As always, you have access to the LucidLink status page and our support team if you need additional assistance. We will be back in touch shortly when fixes are available. Sincerely, Gregory Tomczyk VP of Security
- monitoring · Oct 24, 2026, 04:19 PM UTC
What's new Following our earlier advisory (https://status.lucidlink.com/incidents/pyrcv6319vn6) about the eMudhra certificate issue, we have released updated LucidLink desktop clients that remove the affected third-party certificates from the client's list of trusted certificate authorities. We recommend that you install the update as soon as you are able. Available downloads Patches are now available on the [LucidLink Downloads](https://www.lucidlink.com/download) page for LucidLink 2.x and 3.x clients as well as mobile app stores. What to do next Please update all LucidLink desktop and mobile clients to the latest versions, and if you have any issues, please use the links below to get in touch. If you have questions As always, the LucidLink status page (https://status.lucidlink.com) and support portal for LucidLink 3.x (https://support.lucidlink.com) and LucidLink Classic / 2.X (https://support-classic.lucidlink.com) are available if you need additional information or assistance. Thank you for being a LucidLink customer and for your prompt attention to this update. Sincerely, LucidLink Engineering
- monitoring · Oct 26, 2026, 08:49 AM UTC
We are continuing to monitor for any further issues.
Latest: We are continuing to monitor for any further issues.
-
Recent outages & incidents
Past 90 days- LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)
Timeline · 4 updates
- identified · Sep 02, 2026, 06:38 PM UTC
LucidLink has investigated and identified a service disruption in the Southwestern US region, with clients unable to connect to LucidLink infrastructure. Although this outage does affect the client routes to the LucidLink infrastructure, the data in the LucidLink Filespaces is not at risk. It has been determined that this disruption has been caused by a service incident with Cogent Communications and their network infrastructure. Here is the information from Cogent Communications on their status page: https://ecogent.cogentco.com/network-status Customers in the Los Angeles and Southwestern United States areas may be experiencing increased latency and/or service disruptions due to two separate fiber cuts. Transoceanic traffic to certain Asia-Pacific regions may also be affected. Cogent Engineers are currently being dispatched to both locations, and our third-party fiber vendor has also been engaged to assist with restoration efforts. There is no ETR at this time. We will continue to update here as we have more information.
- monitoring · Sep 02, 2026, 09:39 PM UTC
All LucidLink services are operational. The connectivity disruption identified earlier is related to the external Cogent Communications network incident and is not caused by LucidLink infrastructure. Cogent Communications continues to provide updates on the incident here: https://ecogent.cogentco.com/network-status Some previously affected customers have reported restored connectivity. Customers who continue to experience connectivity issues are advised to contact their Internet Service Provider, as the issue may be related to network routing through Cogent or other upstream providers. We are continuing to monitor customer connectivity and the progress of the Cogent network recovery and will provide further updates if there are any significant changes.
- monitoring · Sep 02, 2026, 09:40 PM UTC
We are continuing to monitor for any further issues.
- resolved · Sep 04, 2026, 05:05 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- LucidLink (North America)LucidLink (Europe)
Timeline · 2 updates
- monitoring · Aug 06, 2026, 09:20 PM UTC
We are monitoring intermittent access issues affecting a limited number of LucidLink filespaces using Wasabi object storage. Affected customers may experience connection errors, interrupted or partial file transfers, or brief difficulty accessing their filespace. Wasabi has linked recent cases to temporary service conditions and infrastructure maintenance affecting subsets of storage resources. Wasabi has advised that these conditions are temporary and that service should recover automatically once the affected maintenance or service event is complete. While previously affected filespaces have recovered, we continue to receive isolated reports. We are working with Wasabi and monitoring for further impact.
- resolved · Aug 12, 2026, 07:01 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full LucidLink outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse LucidLink outage history →Or sign up free to get alerts when LucidLink breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · Statuspage by Atlassian · 4 components checked every 5 minutesThe longest incident in the last year, IBM connectivity issues on May 7, 2026, ran for 8 days. 20 maintenance windows announced in the same period.
Most affected components, last 12 months
- LucidLink (North America)8
- LucidLink (Europe)7
- LucidLink (Asia-Pacific)6
- LucidLink (Latin America)5
Latest incidents
- Security Advisory: Third-party security vulnerability and LucidLink update
What happened This week, security researchers disclosed that eight certificates issued by eMudhra, a third-party certificate authority (CA), were created with…
- LucidLink Service Disruption
LucidLink has investigated and identified a service disruption in the Southwestern US region, with clients unable to connect to LucidLink infrastructure.…
- Intermittent Access Issues Affecting Some Wasabi-Backed Filespaces
We are monitoring intermittent access issues affecting a limited number of LucidLink filespaces using Wasabi object storage. Affected customers may experience…
- Started Oct 23, 2026, 05:17 PM UTC · ● 9d 1h
- LucidLink Service Disruption ResolvedStarted Sep 02, 2026, 06:38 PM UTC · Resolved Sep 04, 2026, 05:05 AM UTC · 1d 10h
- Started Sep 01, 2026, 04:10 PM UTC · ● 61d 2h
- Started Aug 06, 2026, 09:20 PM UTC · Resolved Aug 12, 2026, 07:01 AM UTC · 5d 9h