Cornerstone incident
System latency observed in US Swimlanes Production Environment
Cornerstone experienced a notice incident on June 16, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Jun 16, 2026, 05:04 PM UTC
The CSOD Technology Team observed performance degradation affecting US swimlanes. During this time, clients with portals on these swimlanes may have experienced slow performance or intermittent errors while accessing the application. Our Engineering teams have implemented a fix, and after a period of monitoring, we now consider this issue resolved. The incident started on 06/16/2026 at 8:30 AM PST and was resolved at 06/16/2026 at 8:52 AM PST.
- postmortem Jun 23, 2026, 08:21 AM UTC
**Incident Summary:** On June 16th, 2026, users in the US \(SL1,SL2,SL3,SL5\) Production environment experienced intermittent latency and service degradation. The issue primarily impacted request processing and resulted in intermittent error responses for a brief duration. **Impact:** Users experienced increased response times and intermittent failures while accessing services. The degradation impacted application responsiveness during the incident window. **Root Cause Analysis \(RCA\):** The issue was related to transient performance degradation within the request processing layer. During the investigation, increased processing constraints were identified, which impacted request handling and resulted in intermittent service errors. **Resolution:** The incident was investigated in collaboration with the relevant platform teams. Service performance was stabilized after addressing the underlying capacity constraints, and normal request processing was restored. **Preventive Actions:** The following measures have been implemented to reduce the likelihood of recurrence: * Service capacity and performance characteristics are being reviewed to ensure alignment with workload requirements * Additional monitoring has been enabled to improve visibility into service performance and identify potential capacity constraints proactively