Cornerstone experienced a minor incident on September 2, 2026 affecting Response Time and Response Time and 1 more component, lasting 20h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 02, 2026, 04:16 PM UTC
The swimlane is experiencing some latency issues. Clients with portals across US Swimlanes may experience delays or issues accessing certain pages in the application. 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.
- monitoring Sep 02, 2026, 05:16 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 03, 2026, 12:56 PM UTC
This incident has been resolved.
- postmortem Sep 09, 2026, 08:11 PM UTC
**Issue Summary:** Across two separate incidents on September 1 and 2, 2026, customers in the US West region experienced application performance degradation, including increased response times and intermittent Gateway Timeout \(504\) errors. The incidents were associated with an unexpected and sustained increase in API traffic within the environment, which placed significant demand on shared infrastructure resources and affected overall platform performance. **Root Cause:** The incidents were caused by an unusually high and sustained volume of API requests originating from a single integration. The request volume exceeded expected usage patterns and consumed a significant amount of available infrastructure resources, resulting in resource contention and degraded application performance. **Corrective Action:** Cornerstone increased infrastructure capacity to stabilize platform performance and investigated the source and pattern of the increased API traffic. Once the source was identified, the abnormal traffic was restricted to prevent further impact. Following these actions, platform performance returned to normal, and the environment was monitored to confirm continued stability. **Preventive Measures:** To reduce the risk of a similar issue, Cornerstone has taken the following actions: * Implemented additional monitoring and alerting to provide earlier notification when abnormal resource consumption or API traffic patterns are detected. * Initiated a review of additional usage-based controls, including throttling mechanisms, to better contain unusually high resource consumption and reduce the potential for broader platform impact.