Request timed out.
Ping got no reply
Seen in Windows ping, tracert
Each ping was sent but no ICMP echo reply came back within the timeout.
Common causes
- The target or a firewall blocks ICMP; Windows hosts and many cloud servers drop ping by default.
- The host is down, or the address is wrong.
- Heavy packet loss or a routing problem on the path.
How to fix it
- Do not treat a failed ping as proof the host is down: test the actual service port instead.
- Allow ICMP echo requests in the host firewall and security group if you need ping to work.
- Run `tracert` (Windows) or `mtr` to see where replies stop.
Got a different message? Paste it into the error explainer.
Related errors
- * * * · A traceroute hop did not 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