Cornerstone incident
Intermittent Service Disruption on UK SL production
Cornerstone experienced a major incident on June 29, 2026 affecting Uptime and Uptime and 1 more component, lasting 3h 37m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 29, 2026, 08:49 AM UTC
UK swimlanes are experiencing an intermittent service disruption. 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.
- identified Jun 29, 2026, 09:13 AM UTC
Users report issue on Career Site as well. We keep on working on the problem.
- identified Jun 29, 2026, 11:05 AM UTC
We continue to work on the fix for this issue.
- monitoring Jun 29, 2026, 11:26 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 29, 2026, 12:27 PM UTC
This incident has been resolved.
- postmortem Jul 10, 2026, 06:22 AM UTC
**Incident Summary:** On June 28th, 2026, at 11:24 AM PT, users in the UK Production environment experienced intermittent service degradation impacting session management functionality. The issue resulted in reduced service availability and intermittent failures while accessing affected applications. **Impact:** Users experienced intermittent service disruption and degraded application responsiveness due to instability within the session management service. Some requests were impacted during the incident window, resulting in temporary failures across affected portal functionalities. **Root Cause Analysis \(RCA\):** The issue was related to transient service instability following infrastructure changes, which impacted the availability and responsiveness of the session management service. During recovery, service initialization delays affected the ability to restore full processing capacity within the expected timeframe, resulting in intermittent service impact. **Resolution:** As an immediate mitigation, service traffic handling was adjusted to allow the affected components to stabilize and recover successfully. Once service capacity was restored and stability was confirmed, normal traffic processing resumed and application performance returned to expected levels. **Preventive Actions:** The following measures have been implemented to reduce the likelihood of recurrence: * Service startup and recovery behavior are being reviewed to improve restoration time during availability events. * Additional monitoring and validation checks are being enhanced to improve visibility into service health and recovery patterns.