Last checked: 21 seconds ago
Get notified about any outages, downtime or incidents for Lucidworks and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Lucidworks.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Connected Search | Active |
US Region Data Ingest | Active |
US Region Search APIs | Active |
Lucidworks AI | Active |
3rd-Party Generative Models | Active |
Custom Model Training | Active |
Custom-trained Embeddings Models | Active |
Shared Embeddings Models | Active |
Shared Generative Models | Active |
Lucidworks Analytics | Active |
Beacon & Signals Ingestion | Active |
Usage Analytics Hub | Active |
Lucidworks Platform | Active |
Billing & Entitlements Management | Active |
Integrations | Active |
User Logins & Configuration UI | Active |
View the latest incidents for Lucidworks and check for official updates:
Description: # Summary Beginning at approximately 10:17am PDT and lasting until service restoration at approximately 11:52am, the Lucidworks Signals Beacon on client sites was not functional due to an error in retrieving its configuration from the Lucidworks Platform. During this time, some signals from new site visits were not collected. # Root Cause A database change that was intended to only be applied in our development environment for testing purposes was inadvertently applied to the production database, which resulted in the creation of new, empty tables for storing Beacon configurations and authorization information. For the duration of this incident, when the Beacon initialized and attempted to retrieve its configuration from the Lucidworks Platform at page load time, the call failed with an HTTP 401 Unauthorized response, and the Beacon would silently fail to load. This behavior, while not site-impacting in any way, does result in the inability to send user behavior signals to Lucidworks Analytics, and so for the duration of this incident some analytics data for affected clients will be incomplete. The database change was rolled back, which allowed the Platform to once again successfully return Beacon configurations, which had persisted in the previously-used table throughout the duration of the incident. No configuration data was lost, and Signals Beacon functionality has been fully restored. # Lucidworks Actions We will update our Beacon and Signals APIs to return HTTP 500 errors when the configuration cannot be loaded, in order to generate a higher-severity alert for our teams so that we can more urgently react to similar issues in the future. We will also enhance the Beacon to cache the most recently retrieved configuration in local browser storage so that there is a fallback in addition to a potential backoff strategy to minimize throwing errors. # Recommended Client Actions There are no recommended client actions as a result of this event. Affected customers with additional questions or concerns may contact us via[ Lucidworks Support](https://support.lucidworks.com/).
Status: Postmortem
Impact: Minor | Started At: July 24, 2024, 5:30 p.m.
Description: A configuration change in our [ArgoCD](https://argo-cd.readthedocs.io/en/stable/#what-is-argo-cd) continuous deployment platform caused nondeterministic behavior when applied to our Kubernetes [ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/#what-is-ingress) controllers. Though this change was successfully applied in our development environment, when the same configuration was deployed to the production [Springboard UI](https://platform.lucidworks.com/), it put the cluster into an inaccessible state. We manually intervened to roll back the change as quickly as possible, but found that ArgoCD was still intermittently mis-applying the configuration in this environment. Further troubleshooting efforts identified a stale cache as the culprit; once we forced a hard reset of ArgoCD’s cache, the correct configuration was applied, and the configuration UI returned to a fully functional state. No Connected Search indexing or query functionality was affected during this incident; the extent of the impact was limited to the web-based configuration interface, and no data loss occurred.
Status: Postmortem
Impact: None | Started At: Sept. 29, 2023, 5:14 p.m.
Description: A configuration change in our [ArgoCD](https://argo-cd.readthedocs.io/en/stable/#what-is-argo-cd) continuous deployment platform caused nondeterministic behavior when applied to our Kubernetes [ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/#what-is-ingress) controllers. Though this change was successfully applied in our development environment, when the same configuration was deployed to the production [Springboard UI](https://platform.lucidworks.com/), it put the cluster into an inaccessible state. We manually intervened to roll back the change as quickly as possible, but found that ArgoCD was still intermittently mis-applying the configuration in this environment. Further troubleshooting efforts identified a stale cache as the culprit; once we forced a hard reset of ArgoCD’s cache, the correct configuration was applied, and the configuration UI returned to a fully functional state. No Connected Search indexing or query functionality was affected during this incident; the extent of the impact was limited to the web-based configuration interface, and no data loss occurred.
Status: Postmortem
Impact: None | Started At: Sept. 29, 2023, 5:14 p.m.
Description: Customers affected by this incident may request a detailed Event Analysis Report via their TAM or through Lucidworks Support.
Status: Postmortem
Impact: Minor | Started At: April 11, 2023, 12:30 p.m.
Description: Connected Search customers who were affected by this incident may request a detailed Event Analysis via Lucidworks Support.
Status: Postmortem
Impact: None | Started At: Jan. 6, 2023, 10:36 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.