Is Harness down?

Last checked 1m ago
Current status
Harness is up

No incidents right now.

  • Official status page: status.harness.io
  • Checked every 5 minutes
  • 183 components tracked

Harness is operational right now. Last checked 1m ago; the most recent incident resolved 2h ago.

Real-time Harness status, recent outages, and incident history: pulled directly from Harness's official status page at status.harness.io every 5 minutes. Pingoru tracks 183 Harness services and has captured 59 incidents in the last 90 days (99.05% uptime). Get email, Slack, Discord, or webhook alerts the moment Harness reports a new incident, free for 3 monitors, no credit card.

Users who monitor Harness also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo Rollbar View all 8,000+ providers
Harness uptime 99.05% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved –
    Started Oct 28, 2026, 05:10 PM UTC · Resolved Oct 28, 2026, 05:10 PM UTC
    Timeline · 1 update
    • resolved · Oct 28, 2026, 07:22 PM UTC

      Starting 10/28/2026 10:10 AM CI jobs on internal VM runners intermittently hung or expired without logs, affecting some customers in prod1/2. The resolution is to upgrade the new runner version https://github.com/drone-runners/drone-runner-aws/releases/tag/v1.0.0-rc.318 (Docker image: drone/drone-runner-aws:1.0.0-rc.318)

    Latest: Starting 10/28/2026 10:10 AM CI jobs on internal VM runners intermittently hung or expired without logs, affecting some customers in prod1/2. The resolution is to upgrade the new r…

  2. Resolved 2h 31m
    Started Oct 27, 2026, 07:52 PM UTC · Resolved Oct 27, 2026, 10:24 PM UTC
    Continuous Integration Enterprise(CIE) - Self Hosted Runners
    Timeline · 5 updates
    • investigating · Oct 27, 2026, 07:52 PM UTC

      We are currently investigating this issue.

    • investigating · Oct 27, 2026, 07:58 PM UTC

      CI pipelines on VM infrastructure are failing at the Initialize step because the task goes to a delegate outside the intended pool

    • identified · Oct 27, 2026, 09:15 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Oct 27, 2026, 10:16 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Oct 27, 2026, 10:24 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 34m
    Started Oct 19, 2026, 07:46 AM UTC · Resolved Oct 19, 2026, 08:21 AM UTC
    Continuous Delivery - Next Generation (CDNG)Continuous Integration Enterprise(CIE) - Self Hosted RunnersContinuous Integration Enterprise(CIE) - Mac Cloud BuildsContinuous Integration Enterprise(CIE) - Windows Cloud BuildsContinuous Integration Enterprise(CIE) - Linux Cloud BuildsSecurity Testing Orchestration (STO)Infrastructure as Code Management (IaCM)Platform
    Timeline · 6 updates
    • investigating · Oct 19, 2026, 07:46 AM UTC

      We are currently investigating this issue.

    • monitoring · Oct 19, 2026, 08:02 AM UTC

      A fix has been implemented and we are monitoring the results.

    • identified · Oct 19, 2026, 08:02 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Oct 19, 2026, 08:04 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Oct 19, 2026, 08:21 AM UTC

      This incident has been resolved.

    • postmortem · Oct 23, 2026, 06:21 PM UTC

      ## **Summary** On October 19, 2026, between approximately 12:10 AM and 12:55 AM PDT, customers on Prod4 experienced errors and intermittent unavailability of Harness Pipelines services. Heavy pipeline executions drove a sharp rise in CPU and memory use on the pipeline service, and for a short period all service instances were unavailable. Harness engineering scaled the service both vertically and horizontally, which restored service. A fix for the underlying behavior is being rolled out. ## **Root Cause** On October 19th, high number of concurrent executions with very large execution graphs drove a sharp increase in cluster resources. The service stores and retrieves this full execution graph for visualization purposes and further progressing the pipelines to next states. Our auto-scalaers on Prod4 took longer than usual for scaling resources due to a sharp rise in CPU and memory.  As a part of the fix, the execution graph update will now process graph changes incrementally instead of the full graph. It is being rolled out in a phased manner and will be completely rolled out at the earliest. ## **Impact** * Affected users: Customers on Prod4. * Symptom: unavailability of pipeline functionality in the Harness platform. * Data: No data loss. * Suggested workaround: None required from customers. Harness engineering resolved the issue. * Duration of impact: Approximately 20 minutes of full unavailability and degraded performance for 25 minutes. Harness continued monitoring after recovery and confirmed platform stability with customers. ## **Remediation** **Immediate** Harness engineering scaled the pipeline service both vertically \(more resources per instance\) and horizontally \(more instances\), and removed instances in an unhealthy state. The instance count stabilized and normal service was restored. The system will stay scaled up till the fix is completely rolled out.  **Permanent fix and Action Items** To prevent such issues from happening again, Harness is 1. Tuning the auto heal/scaling process so that impact is mimimal to none. 2. Optimizing the execution graph flow so that large graphs can be process faster.

    Latest: ## **Summary** On October 19, 2026, between approximately 12:10 AM and 12:55 AM PDT, customers on Prod4 experienced errors and intermittent unavailability of Harness Pipelines serv…

  4. Resolved 17m
    Started Oct 15, 2026, 10:10 AM UTC · Resolved Oct 15, 2026, 10:27 AM UTC
    Continuous Delivery - Next Generation (CDNG)
    Timeline · 3 updates
    • investigating · Oct 15, 2026, 10:10 AM UTC

      We are currently investigating this issue.

    • identified · Oct 15, 2026, 10:10 AM UTC

      The issue has been identified and a fix is being implemented.

    • resolved · Oct 15, 2026, 10:27 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 11m
    Started Oct 15, 2026, 08:04 AM UTC · Resolved Oct 15, 2026, 08:15 AM UTC
    Continuous Delivery - Next Generation (CDNG)
    Timeline · 4 updates
    • investigating · Oct 15, 2026, 08:04 AM UTC

      We are currently investigating this issue.

    • identified · Oct 15, 2026, 08:05 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Oct 15, 2026, 08:09 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Oct 15, 2026, 08:15 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Harness outage history

41 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Harness outage history →

Or sign up free to get alerts when Harness breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 183 components checked every 5 minutes
168incidents recorded
168last 12 months
46last 90 days
8 hourstypical duration, 12 months

The longest incident in the last year, Integration Authentication Issue Affecting Data Ingestion on June 23, 2026, ran for 7 days. 62 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Continuous Integration Enterprise(CIE) - Linux Cloud Builds23
  • Continuous Integration Enterprise(CIE) - Linux Cloud Builds21
  • Continuous Integration Enterprise(CIE) - Linux Cloud Builds20
  • Continuous Delivery - Next Generation (CDNG)18
  • Continuous Integration Enterprise(CIE) - Windows Cloud Builds18

Latest incidents

Outage history

Past 90 days · 46 incidents View full outage history →