Network response notes

Network timeout first triage response

A Network first triage note for timeout: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection refused first triage response

A Network first triage note for connection refused: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection reset first triage response

A Network first triage note for connection reset: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network TLS handshake first triage response

A Network first triage note for TLS handshake: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

Network proxy first triage response

A Network first triage note for proxy: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication. It includes evidence, output examples, branches, and the smallest reliable fix.

Network VPN first triage response

A Network first triage note for VPN: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network MTU first triage response

A Network first triage note for MTU: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network DNS cache first triage response

A Network first triage note for DNS cache: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Network packet loss first triage response

A Network first triage note for packet loss: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network port blocked first triage response

A Network first triage note for port blocked: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network timeout post-release regression response

A Network post-release regression note for timeout: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection refused post-release regression response

A Network post-release regression note for connection refused: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection reset post-release regression response

A Network post-release regression note for connection reset: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network TLS handshake post-release regression response

A Network post-release regression note for TLS handshake: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

Network proxy post-release regression response

A Network post-release regression note for proxy: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication. It includes evidence, output examples, branches, and the smallest reliable fix.

Network VPN post-release regression response

A Network post-release regression note for VPN: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network MTU post-release regression response

A Network post-release regression note for MTU: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network DNS cache post-release regression response

A Network post-release regression note for DNS cache: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Network packet loss post-release regression response

A Network post-release regression note for packet loss: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network port blocked post-release regression response

A Network post-release regression note for port blocked: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network timeout affected user or permission response

A Network affected user or permission note for timeout: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection refused affected user or permission response

A Network affected user or permission note for connection refused: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection reset affected user or permission response

A Network affected user or permission note for connection reset: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network TLS handshake affected user or permission response

A Network affected user or permission note for TLS handshake: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

Network proxy affected user or permission response

A Network affected user or permission note for proxy: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication. It includes evidence, output examples, branches, and the smallest reliable fix.

Network VPN affected user or permission response

A Network affected user or permission note for VPN: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network MTU affected user or permission response

A Network affected user or permission note for MTU: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network DNS cache affected user or permission response

A Network affected user or permission note for DNS cache: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Network packet loss affected user or permission response

A Network affected user or permission note for packet loss: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network port blocked affected user or permission response

A Network affected user or permission note for port blocked: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network timeout specific path failure response

A Network specific path failure note for timeout: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection refused specific path failure response

A Network specific path failure note for connection refused: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection reset specific path failure response

A Network specific path failure note for connection reset: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network TLS handshake specific path failure response

A Network specific path failure note for TLS handshake: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

Network proxy specific path failure response

A Network specific path failure note for proxy: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication. It includes evidence, output examples, branches, and the smallest reliable fix.

Network VPN specific path failure response

A Network specific path failure note for VPN: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network MTU specific path failure response

A Network specific path failure note for MTU: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network DNS cache specific path failure response

A Network specific path failure note for DNS cache: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Network packet loss specific path failure response

A Network specific path failure note for packet loss: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network port blocked specific path failure response

A Network specific path failure note for port blocked: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network timeout proxy versus origin split response

A Network proxy versus origin split note for timeout: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection refused proxy versus origin split response

A Network proxy versus origin split note for connection refused: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection reset proxy versus origin split response

A Network proxy versus origin split note for connection reset: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network TLS handshake proxy versus origin split response

A Network proxy versus origin split note for TLS handshake: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

Network proxy proxy versus origin split response

A Network proxy versus origin split note for proxy: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication. It includes evidence, output examples, branches, and the smallest reliable fix.

Network VPN proxy versus origin split response

A Network proxy versus origin split note for VPN: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network MTU proxy versus origin split response

A Network proxy versus origin split note for MTU: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network DNS cache proxy versus origin split response

A Network proxy versus origin split note for DNS cache: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Network packet loss proxy versus origin split response

A Network proxy versus origin split note for packet loss: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network port blocked proxy versus origin split response

A Network proxy versus origin split note for port blocked: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network timeout timeout and load response

A Network timeout and load note for timeout: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection refused timeout and load response

A Network timeout and load note for connection refused: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection reset timeout and load response

A Network timeout and load note for connection reset: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network TLS handshake timeout and load response

A Network timeout and load note for TLS handshake: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

Network proxy timeout and load response

A Network timeout and load note for proxy: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication. It includes evidence, output examples, branches, and the smallest reliable fix.

Network VPN timeout and load response

A Network timeout and load note for VPN: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network MTU timeout and load response

A Network timeout and load note for MTU: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network DNS cache timeout and load response

A Network timeout and load note for DNS cache: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Network packet loss timeout and load response

A Network timeout and load note for packet loss: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network port blocked timeout and load response

A Network timeout and load note for port blocked: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network timeout cache or propagation drift response

A Network cache or propagation drift note for timeout: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection refused cache or propagation drift response

A Network cache or propagation drift note for connection refused: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection reset cache or propagation drift response

A Network cache or propagation drift note for connection reset: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network TLS handshake cache or propagation drift response

A Network cache or propagation drift note for TLS handshake: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

Network proxy cache or propagation drift response

A Network cache or propagation drift note for proxy: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication. It includes evidence, output examples, branches, and the smallest reliable fix.

Network VPN cache or propagation drift response

A Network cache or propagation drift note for VPN: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network MTU cache or propagation drift response

A Network cache or propagation drift note for MTU: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network DNS cache cache or propagation drift response

A Network cache or propagation drift note for DNS cache: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Network packet loss cache or propagation drift response

A Network cache or propagation drift note for packet loss: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network port blocked cache or propagation drift response

A Network cache or propagation drift note for port blocked: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network timeout local versus production drift response

A Network local versus production drift note for timeout: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection refused local versus production drift response

A Network local versus production drift note for connection refused: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network connection reset local versus production drift response

A Network local versus production drift note for connection reset: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.

Network TLS handshake local versus production drift response

A Network local versus production drift note for TLS handshake: TLS or certificate failure caused by hostname mismatch, expired chain, protocol policy, SNI, or mixed content. It includes evidence, output examples, branches, and the smallest reliable fix.

Network proxy local versus production drift response

A Network local versus production drift note for proxy: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication. It includes evidence, output examples, branches, and the smallest reliable fix.

Network VPN local versus production drift response

A Network local versus production drift note for VPN: network failure caused by blocked port, refused listener, packet loss, VPN/proxy path, MTU, VPC rule, or long-running request. It includes evidence, output examples, branches, and the smallest reliable fix.