Community incident signal · updated from GitHub
Is Claude Code having issues?
The newest completed day drew more GitHub issue reports than the recent baseline.
372 reports on 2026-10-15 · 258.9/day trailing baseline · 144% of baseline
This is not Anthropic uptime and does not declare a root cause. It compares the newest completed UTC day with the prior 28 days of public issue filings. For confirmed outages, check the official Anthropic status page.
Error classes drawing recent reports
Curated exact strings, ranked by 90-day report growth and activity. Open one for first-response steps and evidence.
-
account · growing
OAuth token expired / refresh failed
Authentication, usage state or session size blocked the request.
-
local · growing
Segmentation fault (SIGSEGV / SIGABRT)
The local Claude Code process crashed while parsing or executing.
-
network · growing
ECONNRESET: socket hang up
A DNS, proxy, TLS or socket layer interrupted the connection.
-
network · growing
getaddrinfo ENOTFOUND (DNS lookup failed)
A DNS, proxy, TLS or socket layer interrupted the connection.
-
account · growing
Your credit balance is too low
Authentication, usage state or session size blocked the request.
-
network · growing
ETIMEDOUT: request timed out
A DNS, proxy, TLS or socket layer interrupted the connection.
Latest completed release window
v2.1.296 drew 1935 repo-wide filings in the 7 completed days after publication, versus a baseline of 1768.3 (1.09×).
This measures timing, not causation. Reports may concern older builds or unrelated requests.
How to read this status
- Is this the official Claude status page?
- No. This page measures public GitHub issue-report activity. Use the official Anthropic status page for confirmed service incidents.
- Does elevated reporting prove a release caused a regression?
- No. The signal is temporal correlation only. A busy release, duplicate reports, or a service incident can all increase filing volume.
- What should I do when my exact error is listed?
- Open the error page for conservative first-response steps, affected build evidence, backlog direction, and community workaround leads.