›_ Claude Code Issues
Claude Code Issues / Error strings / ETIMEDOUT: request timed out

ETIMEDOUT: request timed out

A socket exceeded its timeout before the response arrived.

33 issues · 10 open · 23 resolved (70%) · first seen Feb 26, 2025

First response · network

What to do now

Most likely: A DNS, proxy, TLS or socket layer interrupted the connection.

  1. Check whether the same request works without the current VPN or corporate proxy.
  2. Verify DNS and certificate trust without disabling TLS verification.
  3. Capture the hostname and exact socket code before escalating.

These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.

Is this getting better or worse?

This class of problem is still growing. 13 new reports in the last 90 days vs 4 in the 90 before — +225%. The open backlog peaked at 10 in 2026-10 and sits at 10 today.

0 3 5 8 10 2025-022025-092026-042026-10
2025-02 — First reports2026-03 — Most new reports (6)2026-10 — Peak backlog (10 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

23 of these reports name the Claude Code build they were running, spanning 21 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 38 days across 23 closures. Of the 23 closures with a recorded reason, 9% were closed as completed and 21 as not-planned or duplicate. The most recent completed fix landed in 2026-03.

Workarounds reported by the community

9 of these issues post a workaround someone says worked. The highest-engagement ones:

[BUG] WSL: "Unable to connect to Anthropic services" resolved by disabling telemetry
…pected) - and both work - SSL/TLS handshake works: succeeds Workaround that works: `bash DISABLE TELEMETRY=1 claude
Found in the description of #2481 · resolved
Network Timeout Errors Occurring Frequently in API Calls
…do. Sometimes, restarting the binary helps. Update: Another workaround is to open multiple windows—4 work for me. Run in each. When one starts working well, close the others.
Found in the thread of #128 · resolved
[BUG] Connection-level errors (ECONNRESET, EPIPE, ETIMEDOUT) are never retried — immediate failure with zero recovery
…+ partial retry reimplementation is the core issue. Partial workaround: PostToolUseFailure hook to auto-retry You can't retry API calls from a hook, but you can detect connection-related failures and alert: Better workar…
Found in the thread of #37077 · resolved
Native binary hangs silently at 100% CPU on VMs with the kvm64 CPU model (no SSE4/POPCNT) — needs a CPU feature pre-flight check
…i/uv exports): - - - . has no effect, so there's no env-var workaround. 2. Stock Bun is not affected — this isn't just "the bundled Bun needs AVX2". 1.4.2, which ships the same simdutf configuration (same implementation-…
Found in the thread of #95566 · still open
Since 2.1.213, one connection error disables HTTP keep-alive for the rest of the process; long sessions then degrade into stream-idle-watchdog stalls and full-conversation resends until restart
…on-streaming fallbacks and 400s/404s pile up until restart. Workarounds 1. Restart long-lived sessions after the first line in the debug log. 2. Run a version before 2.1.213. 3. Patch the setter locally (what we run now;…
Found in the description of #100353 · still open

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 1–33

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. ECONNRESET: socket hang up

    251 issues

  2. ECONNREFUSED: connection refused

    214 issues

  3. Self-signed certificate in certificate chain

    43 issues

  4. getaddrinfo ENOTFOUND (DNS lookup failed)

    59 issues

  5. EADDRINUSE: address already in use

    31 issues

  6. API Error 400 (invalid_request_error)

    2,649 issues