Lucidworks Platform Outage History
12 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Lucidworks Platform Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Connected Search and AI Agent Service Disruption## Summary On October 27, 2026, between 02:51 UTC and 17:29 UTC, Connected Search and Agent Studio agents in the Lucidworks production environment began returning intermittent errors. Any query request could… | 6h 51m | Resolved |
| Oct 27, 2026 | Connected Search Service DisruptionThis incident is now fully resolved and all systems have returned to normal operations. Lucidworks services and software are operating normally with no remaining disruption, and there is no remaining direct customer… | 1h 44m | Resolved |
| Aug 7, 2026 | Lucidworks Platform and Search Service Disruption## Summary On August 7, 2026, Lucidworks was alerted to several application credentials being invalidated across Connected Search, Lucidworks AI, and Lucidworks Platform, and declared a Sev1 incident. Lucidworks found… | 3h 49m | Resolved |
| Aug 6, 2026 | Potential Connected Search Service DisruptionConnected 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… | 1h 15m | Resolved |
| Jul 27, 2026 | SaaS Platform User Interface and Signals Beacon Disruption# Summary On July 27, 2026, at 17:56 UTC, the Secure Sockets Layer/Transport Layer Security \(SSL/TLS\) certificate serving the Lucidworks SaaS Platform domains expired. Users attempting to access the SaaS Platform UI… | 1h 4m | Resolved |
| Jun 19, 2026 | Commerce Studio Rules Interface DisruptionThe 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… | 1h 33m | Resolved |
| May 28, 2026 | Lucidworks AI Hosted LLM Service Disruption## Summary On May 28, 2026, between 16:18 UTC and 17:53 UTC, Lucidworks AI hosted LLMs were unavailable in the `us-southcarolina` region. Customers using hosted LLM inference \(`llama-3-8b-instruct`… | 53 min | Resolved |
| May 12, 2026 | SaaS Platform Access Disruption## Summary On May 12, 2026, at 21:19 UTC, the Lucidworks SaaS Platform experienced an access disruption. Users encountered errors when attempting to use the Lucidworks Platform UI… | 2h 42m | Resolved |
| Apr 24, 2026 | SaaS Platform Service Routing Disruption## Summary On April 24, 2026, at 16:05 UTC, the Lucidworks SaaS Platform experienced an issue that made the entire platform temporarily unavailable and all requests returned IO errors. Lucidworks Engineering was made… | -28 min | Resolved |
| Mar 6, 2026 | platform.lucidworks.com user interface unavailable## Summary On March 6, 2026, at 05:05 UTC, the Lucidworks SaaS Platform experienced a user interface disruption. Users were consistently redirected to a 404 error page when attempting to access… | 1h 8m | Resolved |
| Dec 3, 2025 | SaaS Platform unavailable## Summary On December 3, 2025, at 13:30 UTC, the Lucidworks SaaS Platform experienced widespread service disruptions affecting multiple clients. This issue affected Lucidworks AI functionality \(including Neural… | 2h 34m | Resolved |
| Nov 13, 2025 | SaaS Platform unavailable## Summary On November 13, 2025, at 16:12 UTC, the Lucidworks SaaS Platform became unavailable. This issue affected Lucidworks AI functionality \(including Neural Hybrid Search\), Commerce Studio and Analytics Studio… | 40 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Lucidworks Platform incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Lucidworks Platform Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Lucidworks Platform acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Lucidworks Platform outage in this window ran 6h 51m, against a mean recovery of 2h 12m. If you depend on Lucidworks Platform in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.