Tivor AI Network Lab
Claude Code Network Doctor
Claude Code reconnects and timeouts do not establish a network root cause. Collect evidence before deciding which layer to inspect.
All checks use one measurement engine. Service status, browser paths and client functionality are interpreted separately.
Anonymous · Bounded · Local results
Is your connection ready for AI?
Check reachability and transport evidence, then choose a next step. Tivor streaming tests measure browser → Tivor, not an AI provider streaming path.
In-depth checks currently cover OpenAI / ChatGPT / Codex and Claude / Claude Code. For Gemini, Copilot, Cursor and more, use the 5-provider quick check.
Checking your AI network
Confirmed in this check
Observed irregularities
Still unverified
Next step
Score withheld. System DNS, Fake-IP, IPv4/IPv6 comparison, device proxy/TUN, and authenticated client functionality are outside browser visibility.
Understand this finding
Technical details
Samples, timing, evidence codes and browser scope; not a device-level root cause.
Analyze Codex / Claude Code logs — browser only
Paste text or choose a text file up to 256 KiB. Only symptom categories and counts are returned. Raw logs are never uploaded, retained or included in shared reports.
How to choose the next step
When anonymous web paths complete but the client still fails, compare local DNS, TLS, and terminal versus GUI proxy inheritance. The browser cannot read that configuration. If the Tivor stream interrupts, repeat and compare client logs before attributing a provider failure.
Open Probe Public Beta → · Problems & research →