CI Linux Cloud VM Networking issues - intermittent

What to do

• Check whether you use Harness Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds in us, us-west1. 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 3h 16m it lasted.

  Anything that failed between 2026-09-29 18:45 UTC and 2026-09-29 22:01 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 4

1. investigatingSep 29, 2026, 6:45 PM UTC

   We are currently investigating this issue.

   provider

2. monitoringSep 29, 2026, 9:49 PM UTC

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

   provider

3. resolvedSep 29, 2026, 10:01 PM UTC

   This incident has been resolved.

   provider

4. postmortemOct 2, 2026, 10:40 PM UTC

   ### Summary Between approximately **11:37 AM and 3:01 PM PDT \(18:37–22:01 UTC\) on September 29, 2026**, customers using Harness CI self-hosted Linux cloud runners in **prod1/prod2 \(us-west1\)** experienced intermittent networking failures during pipeline execution — primarily Git/network timeouts when fetching source code. **Root Cause** This was primarily due to saturation of our NAT which was futher exacerbated by a temporary cloud provider compute capacity, preventing new VM provisioning there. ### Impact * Customers running self-hosted Linux CI builds in us-west1 saw **intermittent build/pipeline failures**, not a full outage. * Observed customer-facing errors included Git fetch timeouts, e.g. `Failed to connect to github.com port 443: Connection timed out` **Remediation** * **Immediate:** Rebalanced ARM build-VM load from the saturated us-west1 path toward central1 \(partially limited by central1 capacity\); restarted the affected Cloud NAT gateways, which stabilized pipeline networking. **Action Items** 1. Secure additional NAT gateway/IP capacity \(In progress\) 2. Improve NAT saturation detection and alerting ahead of customer impact. 3. Evaluate cross-region capacity contingencies so a single region's compute shortage doesn't block failover mitigation.

   provider

Corrections

None so far.

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