Cornerstone incident
Intermittent timeouts observed on US Production Environment
Cornerstone experienced a major incident on June 1, 2026 affecting Uptime and Uptime and 1 more component, lasting 8h 6m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 01, 2026, 02:52 PM UTC
Some customers on the US swimlanes (SL1, SL2,SL3,SL5) may experience intermittent timeouts while accessing or navigating the application. We are actively investigating the issue and will share another update as soon as more information becomes available.
- monitoring Jun 01, 2026, 03:09 PM UTC
The CSOD Technology Team has confirmed that the issue has been resolved. We are actively monitoring application stability and performance and will keep you informed of any significant updates.
- investigating Jun 01, 2026, 04:15 PM UTC
The issue has resurfaced, and customers may again experience intermittent timeouts while accessing or navigating the application. Our Engineering Teams are actively looking into it. Thank you for your patience and understanding.
- investigating Jun 01, 2026, 07:37 PM UTC
We are actively investigating this issue and will share an update as soon as possible.
- monitoring Jun 01, 2026, 08:53 PM UTC
Our engineering teams have confirmed that the issue has been fixed. We are currently monitoring for at least 1 hour before marking the issue resolved.
- resolved Jun 01, 2026, 11:15 PM UTC
The CSOD Technology Team observed a performance degradation affecting this swimlane. The problem began at 7:24 AM Pacific Time and was resolved at 11:25 AM Pacific Time. During this time, clients with portals on this swimlane may have experienced slow performance or intermittent errors while accessing the application.
- postmortem Jun 23, 2026, 04:19 AM UTC
**Incident Summary:** On June 1st, 2026, clients in the US Production environment \(SL1, SL2, SL3, and SL5\) experienced intermittent latency for a brief duration. The issue primarily impacted platform responsiveness and request processing. **Impact:** Users experienced intermittent latency and delayed responses while accessing services. The degradation affected multiple application flows, leading to slower response times during the incident window. **Root Cause Analysis \(RCA\):** The issue was related to insufficient service capacity during a period of increased demand. As traffic levels increased, request processing delays were observed, resulting in intermittent latency and degraded responsiveness across affected services. **Resolution:** As an immediate mitigation, service capacity was increased in the impacted environment to better handle runtime load conditions. This action stabilized request processing and restored normal service performance. **Preventive Actions:** The following measures have been implemented to reduce the likelihood of recurrence: * Baseline capacity has been adjusted to better support expected traffic patterns