Harness incident

Deployment Degradation - Slowness in Prod3

Critical Resolved View vendor source →

Harness experienced a critical incident on May 7, 2026 affecting Continuous Delivery (CD) - FirstGen - EOS and Continuous Delivery - Next Generation (CDNG) and 1 more component, lasting 4h 54m. The incident has been resolved; the full update timeline is below.

Started
May 07, 2026, 08:00 AM UTC
Resolved
May 07, 2026, 12:54 PM UTC
Duration
4h 54m
Detected by Pingoru
May 07, 2026, 08:00 AM UTC

Affected components

Continuous Delivery (CD) - FirstGen - EOSContinuous Delivery - Next Generation (CDNG)Cloud Cost Management (CCM)Continuous Error Tracking (CET)Continuous Integration Enterprise(CIE) - Self Hosted RunnersContinuous Integration Enterprise(CIE) - Mac Cloud BuildsContinuous Integration Enterprise(CIE) - Windows Cloud BuildsContinuous Integration Enterprise(CIE) - Linux Cloud BuildsCustom DashboardsFeature Flags (FF)Security Testing Orchestration (STO)Service Reliability Management (SRM)Chaos EngineeringInternal Developer Portal (IDP)Infrastructure as Code Management (IaCM)Software Supply Chain Assurance (SSCA)Software Engineering Insights (SEI)Code RepositoryArtifact RegistryPlatformFME

Update timeline

  1. investigating May 07, 2026, 09:08 AM UTC

    We are currently investigating this issue.

  2. investigating May 07, 2026, 10:19 AM UTC

    We are continuing to investigate this issue.

  3. identified May 07, 2026, 11:20 AM UTC

    We have identified the root cause as elevated queue depth and throughput saturation on the MongoDB layer, leading to processing latency. A fix is being implemented to optimize handling and restore database stability

  4. identified May 07, 2026, 12:06 PM UTC

    Executions are running fine now. However, there is still some slowness in the execution graph generation so we might see some delay in the execution updates to show up in UI. But executions would work without any delay/slowness.

  5. monitoring May 07, 2026, 12:09 PM UTC

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

  6. monitoring May 07, 2026, 12:12 PM UTC

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

  7. monitoring May 07, 2026, 12:12 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved May 07, 2026, 12:54 PM UTC

    This incident has been resolved.

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