Learn / Answers

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

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.