* * *
A traceroute hop did not reply
Seen in traceroute, tracert (Request timed out), mtr
No reply came back from that hop within the timeout, which on its own does not mean traffic is being lost.
Common causes
- The router at that hop does not send ICMP "time exceeded" replies, or rate-limits them; harmless if later hops reply.
- A firewall blocks the probes (UDP by default on Linux and macOS, ICMP on Windows) from that point on.
- When every hop after a point shows stars and the target never replies, traffic is dropped there or the target blocks the probe type.
How to fix it
- Ignore stars in the middle of a trace if later hops and the destination answer.
- Retry with other probe types: `traceroute -I` (ICMP) or `sudo traceroute -T -p 443` (TCP) on Linux.
- Test the destination service directly to see whether it is actually reachable.
Got a different message? Paste it into the error explainer.
Related errors
- Request timed out. · Ping got no reply
- ECONNREFUSED · Connection refused
- ETIMEDOUT · Connection timed out
- ECONNRESET · Connection reset by peer
- EHOSTUNREACH · No route to host
- getaddrinfo ENOTFOUND · The hostname doesn't exist in DNS
- getaddrinfo EAI_AGAIN · Temporary DNS failure
- ENETUNREACH · Network is unreachable
- Broken pipe · Wrote to a connection or pipe that was already closed
- Software caused connection abort · Your own system aborted the connection
- WSAETIMEDOUT (10060) · Windows connection attempt timed out
- WSAECONNREFUSED (10061) · Windows connection refused