Cornerstone experienced a critical incident on September 1, 2026 affecting Uptime, lasting 41m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 01, 2026, 02:02 PM UTC
Clients on US SL5 may encounter errors or issues when attempting to log in to Production. Our Engineering team has identified the root cause on the backend and is actively working on a fix as the highest priority. We will continue to provide regular updates as they become available.
- monitoring Sep 01, 2026, 02:15 PM UTC
We have received confirmation from the CSOD Engineering team that the issue has been fixed and the service has been fully restored. Our Engineering team is currently monitoring the fix to ensure its reliability and stability. We will provide further updates if there are any additional developments.
- resolved Sep 01, 2026, 02:43 PM UTC
The CSOD Technology Team observed a service disruption on US SL5. The issue began at 6:47 AM Pacific Time and service was restored at 6:56 AM Pacific Time. During this time, clients with portals on this swimlane were unable to access the application. Following a brief period of monitoring, the fix remains stable and the service continues to operate as expected.
- postmortem Sep 11, 2026, 09:00 AM UTC
**Root Cause Analysis** **Incident Summary:** On September 1st, 2026, a Service Disruption across US SL5 Production environments prevented users from being able to log in. **Impact:** Users in the US SL5 Production environment experienced portal access failures and timeouts. This prevented users from logging in during the incident window. **Root Cause:** The issue was caused by a database query that was running continuously and taking an extended period to complete. The prolonged execution resulted in significant database transaction log utilization, which impacted database resource availability and subsequently affected portal accessibility. The investigation identified that the query was executing repeatedly and consuming database log resources over an extended duration. **Resolution:** The Data team terminated the long-running database session, which immediately reduced the database log consumption and helped restore portal availability. **Preventive Measures:** * The development team has been engaged to review and optimize the query execution * The recurring execution pattern is being reviewed to prevent continuous long-running processing * Database resource and transaction log utilization is continuously being monitored to identify similar conditions proactively