Harness Outage History

Harness experienced intermittent 503 errors affecting the Internal Developer Portal (IDP) services for 1.6 hours. The issue impacted IDP functionality with service unavailability errors. A fix was implemented and monitored before the incident was fully resolved.

Harness FME SDKs experienced streaming connection instability that caused SDKs to fall back to polling mode, resulting in delayed update propagation and increased reconnection noise in logs. The incident lasted 2.1 hours and was resolved after implementing a fix and monitoring the results.

This was a test incident for Harness's status page system that should be ignored. The test ran for 1.2 hours with a major status classification. The incident was marked as identified with a fix being implemented before being resolved.

Harness experienced intermittent failures in their hosted CI builds affecting both Linux and Windows cloud build environments for 3.8 hours. The issue impacted the Continuous Integration Enterprise (CIE) service across multiple build platforms. A fix was implemented and monitored before the incident was fully resolved.

Harness experienced a minor service incident during development testing that lasted 10 minutes. The incident was identified and investigated as part of routine development testing activities. The issue was resolved within the brief 10-minute timeframe.

Harness experienced degraded delivery of pipeline logging streams to the console for 9.1 hours. The issue affected users' ability to view pipeline logs in real-time through the console interface. A fix was implemented and monitored before the incident was fully resolved.

Harness experienced intermittent failures in their hosted CI builds affecting both Windows and Linux cloud build environments for 13.2 hours. The issue impacted Continuous Integration Enterprise (CIE) components, causing build executions to fail unpredictably. Harness implemented a failover solution and gradual fixes throughout the incident, with full resolution achieved after monitoring confirmed the implemented changes restored normal functionality.

Harness experienced a major service incident that lasted 10 minutes. The incident was under investigation with testing of the Dev Status Page incident messaging system. The specific services affected and resolution details were not detailed in the available incident updates.

Harness experienced slowness in the pipeline execution UI affecting the Continuous Delivery and Infrastructure as Code Management components for 2.7 hours. The investigation revealed that pipeline executions were functioning normally in the backend, with the slowness limited to UI updates only. The issue was identified, a fix was implemented and monitored, and the incident was fully resolved.

Harness experienced pipeline slowness in the Prod3 cluster affecting Continuous Delivery - Next Generation (CDNG) and Infrastructure as Code Management (IaCM) services. The engineering team implemented a fix that resolved the performance issues. The incident lasted 1.9 hours and has been fully resolved.