Network request timeout

What this failure means

A network request exceeded its timeout limit. The remote host did not respond within the expected window, causing the CI step to fail.

Symptoms

Faultline looks for one or more of these log fragments:

connection timed out
read timeout
dial timeout
Get ".*": context deadline exceeded
context deadline exceeded while fetching
operation timed out
request timeout
ETIMEDOUT

Diagnosis

A network request exceeded its timeout limit. The remote host did not respond within the expected window, causing the CI step to fail.

Fix steps

1. Identify the exact host and command that timed out — registry, API, artifact store, or internal service — so you know where to look.

2. Test connectivity directly from the runner with a short timeout:

   curl -v --max-time 10 <URL>
   nc -zv <host> <port>
   

3. Retry the failed job once to separate a transient blip from a persistent routing or service problem.

4. Check the service status page and confirm the endpoint is healthy before adjusting timeout settings.

5. Verify the CI runner can reach the required host through any proxy, firewall, or egress policy applied in that environment.

6. Increase client-side timeout settings only when the endpoint is confirmed healthy and the operation is legitimately large or slow.

Validation

• curl -v --max-time 10 <URL> completes within 10 seconds from the runner.
• Re-run the failing step and confirm it completes without a timeout error.

Why it matters

CI runners may have restricted outbound network access, or the remote service (package registry, API endpoint, artifact store) is temporarily unavailable or slow. Transient network congestion also causes timeouts.

Prevention

• Mirror critical packages, container images, and build artifacts in infrastructure you control to reduce dependency on public services.
• Add explicit retry and exponential back-off behaviour to network operations that are safe to repeat.
• Keep runner egress, DNS, and proxy settings under test with a lightweight connectivity check in CI.
• Separate optional external calls from the critical path so transient upstream slowness does not fail the whole pipeline unnecessarily.

How Faultline detects it

Use faultline explain network-timeout to see the full playbook.

faultline analyze build.log
faultline explain network-timeout

Generated from playbooks/bundled/log/network/network-timeout.yaml. Do not edit directly.