Harness incident

PROD4 – Overview Dashboards Experiencing Issues

Minor Resolved View vendor source →
Started
Feb 03, 2026, 11:24 AM UTC
Resolved
Feb 03, 2026, 02:26 PM UTC
Duration
3h 1m
Detected by Pingoru
Feb 03, 2026, 11:24 AM UTC

Affected components

Continuous Delivery - Next Generation (CDNG)Platform

Update timeline

  1. investigating Feb 03, 2026, 11:24 AM UTC

    We are currently investigating this issue.

  2. identified Feb 03, 2026, 11:56 AM UTC

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

  3. monitoring Feb 03, 2026, 12:39 PM UTC

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

  4. resolved Feb 03, 2026, 02:26 PM UTC

    This incident has been resolved.

  5. postmortem Feb 16, 2026, 06:24 PM UTC

    ## **Summary** On February 3, 2026, dashboards in the Prod4 environment experienced data-fetch failures following the deployment . The issue was caused by an unintended configuration change prevented dashboard metrics from loading.The issue was identified and mitigated the same day through configuration correction and service redeployment. ## **Impact** * Dashboard metrics failed to load in the Prod4 environment. * Underlying system functionality remained operational. * No data loss occurred. * The issue was limited to dashboard data visibility. ## **Root Cause** A recent update to a shared configuration chart was introduced to support an unrelated migration initiative. This change resulted in authentication failures, preventing services from connecting to the database and loading dashboard data ## **Mitigation** The issue was mitigated through the following steps: * Reverted the shared configuration to restore normal functionality. * Applied an emergency configuration fix to explicitly set the correct values. * Rebuilt and redeployed all affected services across relevant versions. ## **Action Items** To prevent recurrence, the following improvements are being implemented: * Enhance version control mechanisms to prevent automatic adoption of shared configuration changes without explicit service-level upgrades. * Improve configuration precedence logic to ensure safer fallback mechanisms. * Enhance monitoring and validation for all dependency connectivity. * Strengthen regression validation processes for shared configuration changes.

Looking to track Harness downtime and outages?

Pingoru polls Harness's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Harness reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Harness alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Harness for free

5 free monitors · No credit card required