Between May 17 and May 19, 2026, customers in the APAC region experienced intermittent unresponsiveness with the Harness platform. The incident occurred twice within a two-day window. In both cases, the GraphQL service became degraded, causing requests to fail or time out for affected users. The service was restored each time by restarting the impacted pods. A permanent alerting fix is in progress and expected to reach production shortly.
One of the two service pods in the APAC cluster entered a degraded state where downstream calls were timing out. While the downstream services showed no visible increase in response time on their end, the pod was unable to receive responses from them in time likely due to a network-level communication issue between the pod and its downstream dependencies.
Identified and restarted problematic nodes. Recovery was confirmed by the engineering team before the incident was marked resolved.
Improved Alerting and Proactive Detection — Implemented new alerts for elevated response times to ensure any recurrence is detected and mitigated before impacting customers.