System Latency on GCP Asia region

Incident Report for EdCast by Cornerstone

Postmortem

Issue Summary:

On February 17, users in the GCP Asia region experienced increased latency due to elevated database CPU utilization triggered by background processing activity. During the affected period, some users observed slower response times while accessing the platform.

Root Cause:

The incident was caused by a product defect in a background processing queue that generated excessive database activity. This resulted in high CPU utilization on the database servers, which temporarily degraded system responsiveness and increased service latency in the affected region.

Corrective Action:

As an immediate mitigation, the number of connections used by the background processing queue was reduced to lower the load on the database. This action stabilized database utilization and restored normal platform performance.

Preventive Measures:

To reduce the likelihood of recurrence, the following actions are being implemented:

  • Query optimization: Improving the database queries executed by the background processing queue to reduce unnecessary load.
  • Queue processing improvements: Enhancing the queue processing mechanism to better control resource usage and prevent similar spikes.
Posted Mar 12, 2026 - 12:42 PDT

Resolved

The elevated latency issue affecting GCP Asia Swimlane has been successfully resolved.

After careful monitoring for a day, this was resolved at 09:20 pm Pacific Time, 17 Feb 2026. CSOD team have taken necessary steps to restore normal performance levels.

We have verified that latency metrics have returned to expected thresholds and all impacted services are now operating normally.

We will continue to monitor the system to ensure continued stability. The RCA for the issue will be shared within 7 to 10 business days.

Thank you for your patience and understanding during this incident.
Posted Feb 19, 2026 - 07:50 PST

Monitoring

We observed performance degradation in the GCP Asia Production environment this morning. The Operations team has addressed the issue, and the sites are now loading as expected.

We will continue to closely monitor the environment to ensure ongoing stability.
Posted Feb 17, 2026 - 21:33 PST
This incident affected: Mumbai (GCP) (Web, API, Data and Analytics, Content Integrations).