HTTP 401 or 403 from an AI service: authentication or connectivity?
Why a measured HTTP 401 or 403 is an authorization response—not automatic proof of provider unavailability.
Research & Concepts
Technical interpretation without false certainty.
Ten explanations of protocol evidence and the limits of diagnosis.
Provider outage or local network failure? A disciplined way to tell
Compare local protocol evidence, official provider status, and one controlled alternate path without overstating root cause.
Why WebSocket can fail when HTTPS works
Understand the distinct WebSocket handshake and persistent channel without claiming that Open Probe V0.1 measures it.
TLS inspection and AI coding agents
How certificate replacement and inspected traffic can affect AI agents, and how to investigate without disabling TLS validation.
Fake-IP DNS: synthetic address or real failure?
Why a synthetic DNS address is not automatically a leak or outage, and which evidence is still needed.
IPv4 works while IPv6 is degraded
Why dual-stack networks can produce different outcomes and why Open Probe V0.1 does not yet compare the two paths.
Captive portal or AI provider failure?
Use link, gateway, portal, general-access, and provider evidence in the right order.
HTTP/2 versus HTTP/1.1 in AI streaming failures
Why negotiated HTTP version is useful context but not a root-cause verdict.
Changing egress IP: failure or normal multi-egress?
Why an exit-address change is an observation, not automatically an AI route failure or quality score.
What a browser AI network scanner cannot measure
Understand browser evidence limits and when a local, read-only Open Probe run adds defensible context.