Is it the network? How to tell from a packet capture
Packets show exactly where a request stopped. Work through it in order: did the name resolve, did the connection open, did encryption succeed, and how long did the server take to answer? The first step that fails is the culprit, and the capture holds the proof.
-
Did the name resolve?
Find the DNS query for the server's name. An NXDOMAIN, SERVFAIL, or missing answer means it's DNS, and nothing after it can work.
-
Did the connection open?
Find the SYN. A SYN/ACK means the path and server are reachable. A reset means nothing is listening (the server). Silence means the network path or a firewall.
-
Did data flow cleanly?
Retransmissions mean packets are being lost on the path. A reset in the middle of a connection means the app or a middlebox gave up.
-
Did encryption succeed?
A fatal TLS alert during the handshake means the client and server couldn't agree, or one didn't trust the other's certificate.
-
How long did the server take?
If the connection opened quickly but the first response took seconds, or came back as an HTTP 5xx error, it's the server or the app, not the network.
All answers
- What does "connection refused" look like in a packet capture?
- Why does a connection request get no response?
- What do TCP retransmissions mean?
- Why was my connection reset (TCP RST)?
- Why is a connection slow to open?
- What does NXDOMAIN mean?
- What do SERVFAIL and REFUSED mean in DNS?
- Why does a DNS query get no answer?
- How slow is too slow for DNS?
- Why does a TLS handshake fail?
- Is TLS 1.0 or TLS 1.1 still safe to use?
- How do I find an expired certificate in a packet capture?
- What do HTTP 4xx and 5xx errors mean in a capture?
- Why doesn't my device get an IP address?
- What causes bad call quality? Jitter, packet loss, and MOS
- Why is QUIC (HTTP/3) not getting a response?
- How does traceroute work?
Skip the checklist
Upload a capture and Blame Finder runs these checks for you, then shows the most likely culprit and the packets that prove it.