How to use ping, traceroute, port and IP tools to diagnose connectivity
When a server is unreachable, these free network tools tell you where the problem is — DNS, routing, firewall or the service itself.
"The server is down" rarely means the server is broken. It usually means something between you and the service, or a firewall rule, is blocking the way. These free tools narrow it down from the outside.
1. Ping — is the host reachable at all?
The ping test sends ICMP echoes and reports packet loss and round-trip time. Interpretation:
Replies, low latency → the host is up and the network path is healthy. If your service still fails, the problem is above the network layer (a firewalled port, an app that is not running).
100% loss → the host is down, the IP is wrong, or ICMP is filtered (some hosts block ping deliberately, so a timeout is not proof of an outage — try a port check next).
High or variable latency → a routing or congestion problem, possibly at the ISP, not your server.
2. Traceroute — where does it stop?
The traceroute tool shows each hop to the destination. Where the trace stops, or latency suddenly jumps, is where the problem is:
Stops well before your host → trouble at an upstream network, not your server.
Reaches your host, then fails to the service → the service port is closed/filtered. Go to the port check.
Latency spikes at one hop → possible congestion or a bad link at that provider.
3. Port check — is the service actually reachable?
The port checker tries to open a TCP connection to a specific port. This is the definitive test for "is my web/SSH/mail server reachable":
Port open → the service is listening and the firewall allows it. If the app still fails, the problem is inside the app (config, crash, wrong document root).
Port closed/filtered → either nothing is listening, or a firewall (host or cloud) blocks it. Check both the server's own firewall and any cloud security group.
4. IP lookup & reverse IP — whose is it?
The IP lookup tool and reverse IP lookup tell you what network an IP belongs to and what else is hosted there:
Confirm your domain points at the IP you think it does.
See the owning network (useful when reporting abuse or diagnosing geo issues).
Reverse lookups help verify that a mail server's PTR record matches — a mismatch hurts email deliverability.
A simple decision tree
Ping — is the host up? → no: check the IP and whether the host itself is down.
Traceroute — where does it stop? → before the host: upstream network.
Port check — is the port open? → no: nothing listening or a firewall.
IP lookup — is my DNS pointing at the right host?
Nine out of ten "server down" reports resolve at step 3 (a closed firewall port) or step 1 (DNS pointing at an old IP). Related: Troubleshoot a down site, Firewall basics and IP addresses and networking.