Cornerstone incident

All Queued Events Stuck and Delayed

Minor Resolved View vendor source →

Cornerstone experienced a minor incident on July 7, 2026 affecting Uptime and Uptime and 1 more component, lasting 4h 31m. The incident has been resolved; the full update timeline is below.

Started
Jul 07, 2026, 06:33 PM UTC
Resolved
Jul 07, 2026, 11:04 PM UTC
Duration
4h 31m
Detected by Pingoru
Jul 07, 2026, 06:33 PM UTC

Affected components

UptimeUptimeUptimeResponse TimeUptimeUptimeUptimeUptimeUptimeUptime

Update timeline

  1. investigating Jul 07, 2026, 06:33 PM UTC

    Customers across all swimlanes may experience delayed or stuck processing of queued events and background jobs (i.e., Content Uploader, Emails, Reporting, etc.). We are actively investigating this issue as a top priority, and will provide regular updates until it is fully resolved.

  2. identified Jul 07, 2026, 08:20 PM UTC

    We are seeing the backlog of queued events begin to decrease. We are working on taking additional action to reduce the backlog more quickly and accelerate recovery. We will continue to provide updates as progress is made.

  3. monitoring Jul 07, 2026, 09:03 PM UTC

    The backlog of queued events continues to decrease as events are processed. Our teams are closely monitoring activity to ensure recovery continues to progress as quickly as possible. We will continue to provide updates until the backlog has cleared.

  4. resolved Jul 07, 2026, 11:04 PM UTC

    All queues have been caught up and after a period of monitoring we are considering this issue Resolved.

  5. postmortem Jul 14, 2026, 06:24 PM UTC

    **Issue Summary:** On July 7, 2026, users across all Production regions experienced intermittent service degradation due to elevated background processing activity. The increased workload temporarily affected platform responsiveness and caused delays in certain application workflows. **Root Cause:** The issue was caused by an unexpected surge in background processing requests, which generated a significantly higher workload than anticipated. The elevated processing volume temporarily reduced system throughput, resulting in increased processing times and intermittent service degradation across multiple regions. **Corrective Action:** As an immediate mitigation, non-essential background processing was temporarily restricted to reduce system load and prioritize critical requests. Additional optimization activities were performed to accelerate queue processing and restore normal system performance. These actions stabilized the environment, and processing rates returned to expected levels. **Preventive Measures:** To reduce the risk of recurrence, Cornerstone has updated operational procedures for managing large-scale background processing activities. These updates are intended to better control processing volume and reduce the likelihood that unexpected workload surges will impact Production services.