Latency Observed on LMS Pages Across All US Swimlanes (Galaxy Customers Only)

Update timeline

1. identified Feb 23, 2026, 04:24 PM UTC

   We are currently investigating reports of increased latency affecting all US swimlane environments (Pilot, Sandbox, and Production). This issue impacts Galaxy customers using LXP and LMS, or LXP alone, and may result in slower page load times. Our Engineering team has identified the root cause and is actively working to restore normal response times. We will continue to share updates as progress is made. Thank you for your patience and understanding.

2. monitoring Feb 23, 2026, 06:08 PM UTC

   The issue has been identified and resolved, and services have been restored to normal operations. We will continue to monitor the situation closely.

3. resolved Feb 23, 2026, 10:23 PM UTC

   The CSOD Technology Team observed a performance degradation affecting this swimlane. The problem began at 7:54 AM Pacific Time and was resolved at 10:48 AM Pacific Time. During this time, clients with portals on this swimlane may have experienced slow performance or intermittent errors while accessing the application.

4. postmortem Mar 12, 2026, 08:24 PM UTC

   **Issue Summary:** On February 23, 2026, increased latency was observed across all U.S. swimlane environments due to an issue with an internal service that depends on a third-party database service \(ArangoDB\). The incident affected Galaxy customers using LXP and LMS, including environments running LXP and LMS together, or LXP alone. During the affected period, users experienced slower page load times and delayed system responses. **Root Cause:** The incident was caused by a disruption in the third-party ArangoDB service used by an internal platform component. The dependency caused the internal service to experience latency, which propagated to all US swimlane environments and resulted in broader platform responsiveness degradation. **Corrective Action:** Engineering teams collaborated with the ArangoDB vendor to identify and address the service disruption. Once the vendor restored normal operation of the database service, the dependent internal services recovered and system performance returned to expected levels. **Preventive Measures:** To reduce the likelihood of a similar incident in the future, the following improvement is being implemented: * Implement Circuit Breaker: Introducing circuit breaker within internal services to prevent dependency failures from propagating and causing broader platform latency.