Cornerstone incident

Reporting 2.0 not accessible for UK Swimlanes and FRA Swimlanes

Major Resolved View vendor source →

Cornerstone experienced a major incident on October 15, 2025 affecting Uptime and Uptime and 1 more component, lasting 2h 23m. The incident has been resolved; the full update timeline is below.

Started
Oct 15, 2025, 01:42 AM UTC
Resolved
Oct 15, 2025, 04:06 AM UTC
Duration
2h 23m
Detected by Pingoru
Oct 15, 2025, 01:42 AM UTC

Affected components

UptimeUptimeUptimeUptimeResponse TimeResponse TimeResponse TimeResponse Time

Update timeline

  1. identified Oct 15, 2025, 01:42 AM UTC

    Users in the UK and France swimlanes may encounter errors when accessing Reporting 2.0. Our team has identified the cause and is working to resolve it as a top priority. We will continue to share updates as we progress.

  2. identified Oct 15, 2025, 01:48 AM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Oct 15, 2025, 04:06 AM UTC

    The issue has been fully resolved. Start time: 3:45 PM PT End time: 8:20 PM PT Between these times, clients in the UK and FRA swimlanes experienced issues with Reporting 2.0, along with intermittent problems accessing Learning, Assignments, and email notifications. The outage occurred during a hotfix deployment, which caused temporary system instability across multiple components. We sincerely apologize for the disruption and appreciate your patience while we worked to restore services.

  4. postmortem Nov 06, 2025, 08:16 AM UTC

    **Incident Summary:** On October 14th, 2025, clients hosted in the FR,CDG SL1 & SL4,METPOL & UK Production environment experienced intermittent issues when accessing Reporting 2.0. Some users encountered page loading failures and brief service disruptions during this period. **Root Cause Analysis \(RCA\):** The issue was caused by a temporary communication problem between internal services handling authentication requests. This led to intermittent access failures for affected users. **Resolution:** Engineering teams performed an authentication reset between the impacted services, which resolved the connectivity issue and restored normal functionality. **Preventive Measures:** * Service Reliability: Review and strengthen authentication processes between dependent services to prevent recurrence.