IACM Module Registry performance degradation

What to do

• Check whether you use Harness Infrastructure as Code Management (IaCM). 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 2h 53m it lasted.

  Anything that failed between 2026-09-15 12:05 UTC and 2026-09-15 14:58 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 6

1. investigatingSep 15, 2026, 12:05 PM UTC

   We are currently investigating this issue.

   provider

2. identifiedSep 15, 2026, 1:19 PM UTC

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

   provider

3. monitoringSep 15, 2026, 1:22 PM UTC

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

   provider

4. monitoringSep 15, 2026, 1:32 PM UTC

   We are continuing to monitor for any further issues.

   provider

5. resolvedSep 15, 2026, 2:58 PM UTC

   This incident has been resolved.

   provider

6. postmortemSep 22, 2026, 9:04 PM UTC

   ## 1. Summary On Monday, September 15, 2026, some customers using Infrastructure as Code Management \(IaCM\) Module Registry on Prod EU1, and later Prod1, experienced timeouts and failed requests. ‌ Affected customers saw Module Registry operations hang or fail in the UI, and IaCM pipelines that look up modules or module-registry connectors during Initialize or Plan could stall and then expire. This was not a platform-wide outage. Other Harness modules were not broadly impacted. We have no report of customer data loss. Workspace plan/apply that did not need Module Registry during the failing calls continued as normal. # 2. Impact * Product area: IaCM Module Registry \(UI and API\) and IaCM pipelines that call Module Registry during Initialize or Plan. * Customer experience: timeouts and failed Initialize/Plan steps; Module Registry UI/API delays or failures. In at least one case, the Module Registry CLI continued to work while the plan path timed out. * Environments: Prod EU1, then Prod1. This was not a full multi-cluster outage. * Severity: S-2. * Data: no data loss reported. # 3. Root Cause A sudden traffic surge caused backend connections to hit capacity limits, leading to client-side timeouts. Increasing capacity and restarting the IaCM service cleared remediated the issue # 4. Remediation **Immediate:** restarted the IaCM service to release stale connections and restore Module Registry and related pipeline steps. **Capacity:** increased the backend capacity for  Module Registry database connection **Permanent:** Tune and optimize the backend for latency and resiliency so that we can absorb traffic spikes without impact. ‌ # Next Steps ‌ To prevent such issues happening again, Harness is working on ‌ _We apologize for the disruption to Module Registry and to pipelines that depend on it. Please reach out to your Harness support contact if you have any further questions about this incident._

   provider

Corrections

None so far.

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