Lucidworks Outage History

Lucidworks is up right now

Lucidworks had 10 outages in the last 2 years totaling 16h 33m of downtime — averaging 0.4 incidents per month.

There were 10 Lucidworks outages since October 30, 2025 totaling 16h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.lucidworks.com

Minor August 6, 2026

Potential Connected Search Service Disruption

Detected by Pingoru
Aug 06, 2026, 03:03 PM UTC
Resolved
Aug 06, 2026, 04:19 PM UTC
Duration
1h 15m
Affected: Connected Search
Timeline · 3 updates
  1. investigating Aug 06, 2026, 03:03 PM UTC

    Lucidworks is currently responding to a report of service disruption affecting Connected Search functionality. While administrative operations within the Lucidworks Platform dashboard remain fully functional, external search operations for a subset of customers utilizing Connected Search are experiencing impact. End users accessing search through affected external applications are currently unable to receive search results or predictive suggestions. We are actively investigating this issue to identify the underlying cause and restore standard operation. Further updates will be provided as additional details become available.

  2. identified Aug 06, 2026, 03:48 PM UTC

    The Connected Search service disruption is limited in scope to a specific client configuration. Affected customers are experiencing 401 Unauthorized response codes related to invalid authorization credentials when attempting to perform search queries through this integration, preventing end users from receiving search results or suggestions. We have confirmed that this issue is isolated to requests using invalid or expired credentials and that backend services and Connected Search functionality remain fully operational for all other clients. We are actively reproducing the exact credential behavior to resolve the disruption. Further updates will be provided as additional details become available.

  3. resolved Aug 06, 2026, 04:19 PM UTC

    Connected Search and the Lucidworks Platform are fully operational, having experienced no service degradation. The root cause was confirmed to be isolated to a single customer issuing search requests using invalid credentials. The issue was validated and resolved after confirming all backend systems and platform functionality remained operating normally. Other customers utilizing the Lucidworks Platform are experiencing no impact. Please contact Lucidworks Support (https://support.lucidworks.com/hc/en-us) for any questions or assistance needed.

Read the full incident report →

Minor June 19, 2026

Commerce Studio Rules Interface Disruption

Detected by Pingoru
Jun 19, 2026, 04:23 PM UTC
Resolved
Jun 19, 2026, 05:56 PM UTC
Duration
1h 33m
Affected: Commerce Studio
Timeline · 4 updates
  1. investigating Jun 19, 2026, 05:08 PM UTC

    Lucidworks Commerce Studio is currently experiencing intermittent latency, specifically affecting the Rules component. Customers attempting to interact with the Rules interface will experience timeouts when trying to load their data. There is no direct end-user impact, as this issue only affects internal administrative tasks within the Lucidworks Platform. We are actively investigating the cause of this disruption and will provide further updates as more information becomes available.

  2. identified Jun 19, 2026, 05:21 PM UTC

    Commerce Studio is experiencing reduced performance within the Rules API due to apparent underlying database contention. Platform users attempting to interact with the Rules section of the interface, particularly when selecting the option to display 100 rules per page, will encounter timeouts. There is no direct end-user impact to search experiences, as this issue is confined to administrative functions within the management console. We believe the issue to be caused by database contention specifically triggered by simultaneous interactions involving a large number of rules. We are currently scaling up the database to alleviate the contention. While this scaling process is underway, some page loads may be interrupted. We are continuing to work toward full resolution and will provide an update once the system has stabilized.

  3. monitoring Jun 19, 2026, 05:48 PM UTC

    We have scaled up the database to alleviate the performance issues. Performance has now normalized, and Commerce Studio Rules interactions have stabilized. Platform users may still observe minor latency when attempting to page through 100 rules at a time within the interface, but these requests no longer experience complete timeouts or produce errors. There is no direct end-user impact. We are continuing to monitor database response times and page load times, and we will provide a final update once full resolution is confirmed.

  4. resolved Jun 19, 2026, 05:56 PM UTC

    The issue affecting the Commerce Studio Rules interface has been resolved, and all previously affected services are now operating normally. Commerce Studio users can interact with the Rules interface and page through large datasets without experiencing page load errors. There remains no direct end-user impact on search experiences. The root cause of the incident was database contention triggered by interactions involving a large number of rules. To resolve the issue, we scaled up the database, which normalized performance and stabilized the system.

Read the full incident report →