Timeout vs Unreachable Explainer
Timeout or unreachable — the two mean opposite things about where the fault is.
What you paste
Parsed in your browser — never uploadedResult
No error message recognised
Nothing in that output matches one of the errors ping reports. The reference above covers all of them. The distinction worth carrying away is between a timeout and an unreachable: a timeout is silence, and an unreachable is a router actively telling you it could not deliver — which means the path is working well enough to carry that message back, and makes it the more diagnosable of the two despite sounding worse.
- Request timed outThe reply was lost, the destination is ignoring ICMP, or a firewall is dropping the probe silently. Silently is the key word — a device that drops without replying leaves exactly this.
- Nothing came back within the wait, and nothing on the path reported a problem.
- Destination host unreachableUsually the last router before the destination, which knows the subnet and got no ARP reply — so the host is off, disconnected, or does not exist at that address.
- A router on the path sent back a message saying it could not deliver the packet.
- TTL expired in transitA routing loop, or a path genuinely longer than the TTL allows. A loop is much the likelier of the two.
- The packet was passed between routers until its hop limit ran out.
- Unknown host / could not find hostA DNS problem rather than a network one. The packet never left.
- The name could not be resolved to an address, so nothing was ever sent.
- Network is unreachableNo default gateway, or an interface that is down. The packet did not leave your computer.
- Your own machine has no route toward the destination.
What this cannot tell you
- Explains the message. It cannot tell you why the device behaved that way, only what the message establishes about where to look.
- A host that will not answer a ping frequently serves traffic perfectly. ICMP is blocked by policy far more often than by fault, so a timeout is weak evidence of a problem.
- Parsed in your browser. Nothing is uploaded, and the output you paste is not stored.
Take this with you
How this reads your output
Ping reports several distinct failures and they are routinely treated as one, which sends people looking in the wrong place. A timeout is silence: nothing came back and nothing on the path admitted to dropping it, so it could be loss, or a firewall discarding the probe without comment, or a host that simply ignores ICMP. A destination unreachable is the opposite — a router actively sent a message back saying it could not deliver, which means the path is working well enough to carry that message to you, and the address that sent it names where delivery stopped. That makes the more alarming-sounding message by far the more diagnosable one. Two more are not network faults at all: an unknown host is DNS, and a network unreachable is your own machine having no route.
What the results mean
- Request timed out
- Silence. Nothing came back and nothing reported a problem — including a firewall dropping quietly.
- Destination host unreachable
- A router answered to say it could not deliver. The address that sent it is where delivery stopped.
- Unknown host
- DNS. The packet never left, so nothing about the network is implicated.
- Network is unreachable
- Your own machine has no route out. Check your interface and default gateway first.
Common problems and fixes
- Ping times out but the website loads
- Entirely normal. ICMP is blocked by policy on a great many hosts and networks while everything else works, so a timeout is not evidence that something is wrong.
- I get unreachable from my own router's address
- That router knows the destination subnet and got no reply from the host. The device is off, disconnected, or not at that address.
- TTL expired in transit
- A routing loop, most likely. Run a traceroute and look for the same two or three addresses repeating.
Frequently asked questions
What is the difference between a timeout and an unreachable?
A timeout is silence — nothing replied and nothing reported dropping it. An unreachable is a router telling you it could not deliver, which is more informative: the path works well enough to carry that message back, and the address that sent it tells you where delivery stopped.
Why does ping fail when the site works fine?
Because ICMP is blocked by policy far more often than by fault. Many hosts and networks discard pings deliberately while serving traffic normally, so a failed ping proves very little on its own.
Is unreachable worse than a timeout?
It sounds worse and is usually easier to fix, because it names a router that gave up. A timeout tells you nothing about where the packet stopped.
Put this on your own site
Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.
<iframe src="https://runthetests.com/embed/ping-error-explainer/" width="100%" height="720" style="border:1px solid #e5e5e5;border-radius:8px" title="Timeout vs Unreachable Explainer" loading="lazy"></iframe>
Preview it at https://runthetests.com/embed/ping-error-explainer/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.
More in Interpreter
- Ping Output AnalyserPaste any ping run and get latency, jitter and loss with a plain-English verdict.
- Traceroute Output InterpreterRead a traceroute or MTR properly — and stop blaming the hop that is not at fault.
- Packet Loss Significance CheckerMeasure packet loss from ping output — and know when the sample is too small to trust.