Critical incident

Cornerstone: Service Disruption

Affected: Response Time, Response Time, Response Time

Current status of Cornerstone: Operational — live Cornerstone status

Timeline

1. Jul 24, 2026, 03:21 UTC
   investigating
   Some customers in UK, France and Japan swimlanes are experiencing issues while logging into the system. This is our top priority and we are working to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.
2. Jul 24, 2026, 04:36 UTC
   monitoring
   The fix has been successfully deployed to all Production instances across all regions. We are currently working on deploying the fix to the lower environments. In the meantime, we will continue to closely monitor the Production environments to ensure the solution remains stable and no further issues are observed.
3. Jul 24, 2026, 04:48 UTC
   monitoring
   The fix has been successfully deployed to all the environments (Production and lower environments). We will continue to closely monitor the environments to ensure the solution remains stable and no further issues are observed.
4. Jul 24, 2026, 09:59 UTC
   resolved
   Some customers in UK, France and Japan swim lanes experienced issues while logging into the system. The problem began on 23rd July 7:10 PM Pacific Time and was resolved by 8:20 PM Pacific Time.
5. Aug 6, 2026, 18:12 UTC
   postmortem
   **Root Cause Analysis \(RCA\)** ‌ **Incident Summary:** On July 23rd, 2026, users across the UK, JP, and EU Production environments experienced intermittent login failures. The issue primarily affected users authenticating using Multi-Factor Authentication \(MFA\), resulting in temporary portal access issues. **Impact:** Temporarily impacted authentication and portal accessibility for affected users. **Root Cause:** The issue was related to transient instability within the authentication processing flow, which impacted the successful processing of a subset of login requests. This resulted in intermittent authentication failures for affected users until normal service processing was restored. **Resolution:** As an immediate mitigation, the affected authentication application components were recycled across the impacted regions to restore normal request processing. Following the recovery actions, authentication services stabilized and successful user login was validated. **Preventive Measures:** The following measures have been implemented to reduce the likelihood of recurrence: * Application monitoring has been reviewed to improve visibility into authentication service health and login processing. * Operational procedures have been updated to enable faster identification and recovery of authentication service interruptions.

Updates as published by Cornerstone (original).