Cornerstone experienced a major incident on September 8, 2026 affecting Response Time, lasting 1d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 08, 2026, 02:03 PM UTC
A production incident occurred in the EU Production environment hosted in Frankfurt (FRA PRD), resulting in the Careersite service becoming completely unavailable. The issue has been identified, and the Engineering team is actively working on a resolution. Given the high severity of the incident, restoring service remains our top priority, and the team is working diligently to restore functionality as quickly as possible.
- monitoring Sep 08, 2026, 03:22 PM UTC
A fix has been deployed, and we are seeing no errors. We will monitor for one hour before placing this in Resolved status.
- monitoring Sep 08, 2026, 06:11 PM UTC
We are continuing to monitor for any further issues.
- monitoring Sep 09, 2026, 09:20 AM UTC
We are continuing to monitor for any further issues.
- resolved Sep 09, 2026, 05:35 PM UTC
No new reports of Career Site inaccessibility noted during last 24 hours. Hence we close this status page. Given recent occurrences engineering team is actively working on permanent solution to prevent future inconvenience.
- postmortem Sep 21, 2026, 06:08 PM UTC
**Root Cause Analysis** **Incident Summary:** Between Sep. 3rd and Sep. 8th, 2026, there were three Production incidents that affected Career Site functionality. This issue was intermittent across the FRA SL1 Production environment. These incidents occurred * Sep. 3rd from 4:37 am - 5:02 am PT * Sep. 7th from 2:13 pm - 2:25 pm PT * Sep. 8th from 6:20 am - 8:14 am PT **Impact:** Users experienced intermittent failures while accessing Career Site functionality. This resulted in a degraded user experience and partial service disruption during the incident window. **Root Cause:** The issue was caused by a sudden increase in traffic that temporarily exceeded the available service capacity. During the resulting scale-up activity, newly provisioned application capacity required additional time to become fully operational and could not immediately accommodate the increased demand. The limited capacity buffer combined with the application startup time resulted in intermittent service failures until sufficient capacity was available to handle the traffic. **Resolution:** * The service capacity and scaling configuration were adjusted to maintain an appropriate capacity buffer and better accommodate sudden increases in traffic. The affected service was also redeployed to restore stability * As a permanent improvement, the service has been moved to infrastructure with enhanced scaling capabilities to respond more rapidly to sudden increases in traffic. Since Sep. 12th, the new infrastructure has been fully handling service traffic **Preventive Measures:** * The service has been transitioned to infrastructure with improved scaling capabilities to better accommodate unexpected traffic increases * Capacity and application health will continue to be monitored during traffic fluctuations to ensure sufficient resources are available to maintain service stability