Harness Outage History

The Harness Code Module became inaccessible across production environments prod1, prod2, and prod3. The issue was identified and a fix was implemented after investigation, with the service being monitored before full resolution after 2.4 hours.

Harness experienced a delay in Cloud provider billing data processing within their EU1 environment, affecting the Cloud Cost Management (CCM) service for 4.6 hours. The incident was identified and subsequently resolved, restoring normal billing data flow to the affected region.

Harness experienced degraded access to the login page for 6.2 hours. The issue affected users' ability to log into the platform. A fix was implemented and the incident was resolved after monitoring confirmed the solution was effective.

Harness experienced slowness in the Pipeline Execution graph UI that affected the Continuous Delivery - Next Generation (CDNG) interface for 1.4 hours. Pipeline executions continued to function normally while only the UI display was impacted. The issue was identified and resolved with a implemented fix.

Harness experienced a major incident affecting Prod1/Prod2 pipelines and user logins in their Continuous Delivery Next Generation service. The issue impacted users' ability to access the platform and run deployment pipelines. The incident was resolved after 36 minutes once the engineering team identified the root cause and implemented a fix.

Harness experienced a major incident affecting their Continuous Integration Enterprise Mac Cloud Builds service for 35 minutes. The issue impacted hosted CI mac builds, preventing users from running their continuous integration workflows on Mac infrastructure. The incident was resolved after the team identified the root cause and implemented a fix.

Harness experienced degraded performance in SEI insights for 3.2 hours. The issue was identified and a fix was implemented, with monitoring confirming the resolution. The incident was classified as minor impact.

Harness experienced a minor incident where hosted CI builds were failing, affecting the Continuous Integration Enterprise (CIE) Self Hosted Runners components. A fix was implemented and the incident was resolved after 17 minutes of monitoring to ensure the solution was effective.