{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-07-24T10:19:17.887Z"
  },
  "data": {
    "id": "incident_statuspage_harness_5s77b51fpx5s",
    "slug": "harness-platform-is-experiencing-degraded-performance-for-some-organizations-2026-04-30",
    "title": "Platform is experiencing degraded performance for some organizations.",
    "summary": "Platform is experiencing degraded performance for some organizations.",
    "status": "resolved",
    "severity": "minor",
    "startedAt": "2026-04-30T16:25:42.814+00:00",
    "updatedAt": "2026-05-11T20:51:23.883+00:00",
    "resolvedAt": "2026-04-30T17:50:48+00:00",
    "provider": {
      "slug": "harness",
      "name": "Harness"
    },
    "affectedServices": [
      {
        "slug": "harness-cicd",
        "name": "CI/CD"
      },
      {
        "slug": "harness-feature-flags",
        "name": "Feature flags & FME"
      },
      {
        "slug": "harness-platform",
        "name": "Platform & dashboards"
      }
    ],
    "links": {
      "html": "/incidents/harness-platform-is-experiencing-degraded-performance-for-some-organizations-2026-04-30",
      "api": "/api/v1/incidents/harness-platform-is-experiencing-degraded-performance-for-some-organizations-2026-04-30",
      "providerHtml": "/providers/harness"
    },
    "impactSummary": "Harness reported a minor event for the affected tracked services.",
    "source": {
      "id": "source_harness_status",
      "kind": "official_status_page",
      "name": "Harness Status",
      "checkedAt": "2026-07-23T12:00:00Z",
      "officialUrl": "https://status.harness.io",
      "statusPageUrl": "https://status.harness.io"
    },
    "updates": [
      {
        "id": "update_statuspage_harness_5s77b51fpx5s_7vsbs7kr7nj8",
        "status": "investigating",
        "body": "We are currently investigating this issue.",
        "createdAt": "2026-04-30T16:25:43.27+00:00"
      },
      {
        "id": "update_statuspage_harness_5s77b51fpx5s_t3g086138wyp",
        "status": "identified",
        "body": "Issue has been identified and mitigated",
        "createdAt": "2026-04-30T17:27:26.442+00:00"
      },
      {
        "id": "update_statuspage_harness_5s77b51fpx5s_y8qsrwvq6cvf",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-04-30T19:08:48.351+00:00"
      },
      {
        "id": "update_statuspage_harness_5s77b51fpx5s_kc688yyysd71",
        "status": "resolved",
        "body": "# **Summary**\n\nOn April 30, 2026, between approximately 15:29 UTC and 17:00 UTC, customers in Prod3 experienced degradation impacting delegate connectivity, instance synchronization, pipeline executions, and connector operations due to spike in load on one of our services. .\n\nService stability was restored through service scaling, infrastructure capacity increases, and database resource expansion.  \n\n# **Impact**\n\nCustomer Impact:\n\n* Delegates disconnected intermittently during the incident window\n* Instance synchronization operations were delayed\n* Some pipeline executions and connector operations experienced failures or delays\n\nDuration:\n\n* Delegate connectivity impact: ~15 minutes\n* Elevated service degradation: ~90 minutes\n\n# **Root Cause**\n\nThe incident was caused by spike causing thread exhaustion and elevated request contention between internal  services during a period of increased synchronization and delegate activity.\n\n‌\n\n# **Mitigation and Recovery**\n\nThe following actions were taken to restore service stability:\n\n* Scaled management service replicas horizontally\n* Increased autoscaling thresholds and maximum replica counts\n* Expanded Database compute capacity\n* Upgraded MongoDB infrastructure components\n* Stabilized delegate reassignment and reconnection processing\n\nServices recovered progressively beginning at approximately 15:47 UTC, with full stability restored by ~17:00 UTC.  \n\n# **Preventive Actions**\n\nTo prevent such issues from happening again, We are implementing the following improvements\n\n* Improving our circuit breakers and fail-fast protections between dependent services\n* Enhancing monitoring and alerting for thread pool saturation and queue buildup\n* Increasing baseline service headroom and resiliency protections",
        "createdAt": "2026-05-11T20:47:58.681+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}