Prod2: CV is failing with errors for all customers

What to do

• Check whether you use Harness Continuous Delivery - Next Generation (CDNG). Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 8m it lasted.

  Anything that failed between 2026-09-29 14:41 UTC and 2026-09-29 18:49 UTC may need a replay.

• Subscribe to Harness's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=harness works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Harness 5

1. investigatingSep 29, 2026, 2:41 PM UTC

   We are currently investigating this issue.

   provider

2. monitoringSep 29, 2026, 3:54 PM UTC

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

   provider

3. monitoringSep 29, 2026, 3:57 PM UTC

   We are continuing to monitor for any further issues.

   provider

4. resolvedSep 29, 2026, 6:49 PM UTC

   This incident has been resolved.

   provider

5. postmortemOct 2, 2026, 5:37 AM UTC

   **Summary** Customers on Prod-2 experienced elevated failure rates in Continuous Verification pipelines. Verification jobs failed to complete or reported errors because CV data-collection workers could not communicate with the platform service that coordinates their work. This was caused by an unexpected traffic spike to one of our backend systems.  Service was restored by scaling out the affected platform component. No data loss or corruption occurred. ‌ **Customer Impact** Customers using Continuous Verification on Prod-2 saw verification pipeline jobs fail or time out during the incident window. A significant fraction of verification job instances that ran during this period ended in an operational failure. Pipelines not using CV continued to operate normally. ‌ **Root Cause** A large automated provisioning run created a significant number of persistent CV monitoring workers in a short window, which overwhelmed a shared platform component. The sudden increase in concurrent outbound calls exhausted the available network connections on each service instance.   ‌ **Mitigation** The maximum scaling limit for the CV service was raised, allowing it to expand capacity to meet demand. Failures stopped shortly after the scale-out was completed. ‌ **Next Steps** To prevent recurrence, Harness will: * **Increase capacity headroom and add provisioning guardrails:** Raise the CV service scaling limit to maintain headroom under burst loads, and introduce rate limiting for bulk provisioning of monitored services. * **Improve Resiliency:** Add exponential backoff and jitter for worker retries, and use a reusable connection pool to reduce overhead and prevent transient failures from compounding under high concurrency. * **Improve monitoring and alerting:** Enhance alerting for abnormal per-account worker growth rates, so similar conditions are detected and acted on earlier.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.