Lucidworks Outage History

Lucidworks is up right now

Lucidworks had 8 outages in the last 2 years totaling 11h 45m of downtime — averaging 0.3 incidents per month.

There were 8 Lucidworks outages since September 8, 2025 totaling 11h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.lucidworks.com

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 →

Minor September 8, 2025

Intermittent search failures of Connected Search sites

Detected by Pingoru
Sep 08, 2025, 11:54 AM UTC
Resolved
Sep 08, 2025, 01:15 PM UTC
Duration
1h 21m
Affected: Connected Search
Timeline · 4 updates
  1. investigating Sep 08, 2025, 12:57 PM UTC

    We are seeing an elevated error rate on search requests for our Connected Search customers. Lucidworks Engineering is actively investigating the issue, and updates will be posted here as soon as we have more information to share.

  2. investigating Sep 08, 2025, 01:00 PM UTC

    We are continuing to investigate this issue. We are seeing elevated query latency related to a critical backend search service, and are focusing our investigation there.

  3. monitoring Sep 08, 2025, 01:05 PM UTC

    The issue was due to a performance degradation with one of our 3rd-party service providers. Once their service was fully recovered, we saw recovery of the elevated Connected Search error rate. We will continue to monitor this issue to ensure it is fully resolved.

  4. resolved Sep 08, 2025, 01:15 PM UTC

    Recovery of the 3rd-party service provider's system led to recovery of our own backend search service, and Connected Search query responses have been fully functional since that time.

Read the full incident report →