Cornerstone incident

Resolved - Service Disruption

Notice Resolved View vendor source →

Cornerstone experienced a notice incident on August 26, 2026 affecting Uptime and Uptime and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 26, 2026, 03:33 AM UTC
Resolved
Aug 26, 2026, 03:33 AM UTC
Duration
—
Detected by Pingoru
Aug 26, 2026, 03:33 AM UTC

Affected components

UptimeUptimeUptimeUptime

Update timeline

  1. resolved Aug 26, 2026, 03:33 AM UTC

    Production environment on AU, JP, FR, US swimlanes were experiencing a service disruption when accessing from CHINA region. Issue lasted around 50 minutes. The CSOD Technology Team observed a service disruption on these swimlanes. Our engineering team has resolved the issue and services are back to normal for users in China.

  2. postmortem Sep 06, 2026, 06:44 PM UTC

    **Root Cause Analysis** **Incident Summary:** On August 25th, 2026, an issue was identified affecting select customers using the China Content Delivery Network \(CDN\). The issue impacted requests for specific web resources across US SL1, US SL5, FRA SL1, JP SL1, and AU SL 1 Production environments. **Impact:** Affected users experienced errors when accessing certain resources through the China CDN during the incident window. The impact was limited to customers using the China CDN. **Root Cause:** The issue was caused by a configuration optimization implemented to improve resource caching behavior. The change resulted in an unexpected routing condition, which caused an incorrect SSL certificate to be presented for affected requests. As a result, requests for the impacted resources were rejected and returned errors to users. **Resolution:** The configuration was reverted to the previous stable state, which removed the unexpected routing condition and restored the correct SSL configuration. Following the change, the affected resources were validated and service was restored for the impacted customers. **Preventive Measures:** * Additional validation will be performed for CDN configuration changes to confirm correct routing and SSL behavior before and after implementation * Configuration changes impacting CDN caching and routing will undergo additional review prior to implementation