Cornerstone experienced a minor incident on June 17, 2026 affecting Uptime and Uptime and 1 more component, lasting 2h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 17, 2026, 09:46 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 Jun 17, 2026, 10:21 PM UTC
Our engineering teams have identified the cause and implemented a fix. We've validated that the issue is no longer present. We will monitor for 1 hour before marking this incident resolved.
- resolved Jun 18, 2026, 12:00 AM UTC
This incident has been resolved.
- postmortem Jul 02, 2026, 06:19 PM UTC
**Incident Summary:** Beginning in mid-April 2026, users in the US Production environment \(SL1, SL2, SL3, and SL5\) experienced intermittent 502 and 504 Gateway Timeout errors while accessing the platform. The issue primarily occurred during periods of elevated traffic and affected multiple customers, resulting in occasional request failures and degraded platform responsiveness. **Root Cause:** The issue was caused by capacity constraints that impacted request processing during periods of elevated traffic. As system utilization increased, available processing capacity across multiple platform components was not sufficient to consistently support peak request volumes, resulting in intermittent gateway timeout errors. The intermittent nature of the issue made it difficult to reproduce consistently and required multiple rounds of investigation to identify the contributing factors. The analysis identified opportunities to improve resource allocation, request processing efficiency, and overall platform resiliency during peak workloads. **Corrective Action:** Capacity optimizations were implemented across multiple platform layers to improve request handling and system resilience. These changes increased the platform’s ability to process higher traffic volumes while maintaining stable performance. Following implementation, the occurrence of 502 and 504 Gateway Timeout errors was significantly reduced, and overall platform stability improved during periods of elevated demand. **Preventive Measures:** The following measures have been implemented to reduce the likelihood of recurrence: * Enhanced capacity monitoring has been implemented to proactively identify resource utilization trends before they impact customers. * Additional performance and network monitoring alerts have been added to improve early detection of potential capacity bottlenecks. * Ongoing capacity reviews and performance tuning will continue to ensure the platform scales effectively with increasing workloads. * Periodic validation of platform performance under peak traffic conditions will be performed to verify continued service resilience.