Skip to content
OutageDeck

Incident detail

Traceable APAC Cluster Slowness

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Harness breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Harness alerts work

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    We are currently investigating this issue.

  2. Identified

    We have identified a potential issue causing the service access problem and are working hard to address it. Please continue to monitor this page for updates.

  3. Resolved

    We can confirm normal operation, Slowness issue is resolved. We will publish the RCA

  4. Resolved

    ## Summary

    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.

    ‌

    ## Impact

    • APAC-region customers experienced intermittent inability to access the Harness platform UI and API
    • No data loss was reported; the impact was limited to service availability

    ‌

    ## Root Cause

    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.

    ‌

    ## Mitigation

    Identified and restarted problematic nodes. Recovery was confirmed by the engineering team before the incident was marked resolved.

    ## Next Steps

    Improved Alerting and Proactive Detection — Implemented new alerts for elevated response times to ensure any recurrence is detected and mitigated before impacting customers.