Ping: Request timed out Networking Origin: Network OSI layer 3 · Network Last updated 5 Nov 2026

Networking: ping — Request timed out / 100% packet loss (host drops or filters ICMP)

No echo reply arrived in time: the host is down, unreachable, or simply ignores ping.

Exact message you may see Request timed out100% packet lossReply from: Request timed out4 packets transmitted, 0 received, 100% packet lossPing request timed out
Seen on: Windows Linux Networking

Meaning

Timeouts differ from "unreachable": nobody answered. Check whether ICMP is filtered by a firewall or cloud security group, and test the real service port (Test-NetConnection host -Port 443, nc -vz) because many hosts block ping but run fine.

Common causes

  • Host down or unplugged
  • Firewall or security group blocks ICMP
  • Routing problem or packet loss en route
  • Wrong IP address
  • Rate limiting of ICMP

⚡ Quick fix

  1. Test the service port instead of ping
  2. Allow ICMP echo in the firewall/security group
  3. Compare with a ping to the default gateway

Detailed fix by platform

Windows

  1. powershell
    Test-NetConnection 203.0.113.10 -Port 443
    ping -n 10 203.0.113.10

How to diagnose

  1. Gateway ping — Works?
  2. Port test — Open?
  3. ICMP — Allowed?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

1005 — Cloudflare Error 1005: Access denied — The owner of this website has banned the autonomous system number (ASN) your IP address is in (Cloudflare)10051006 — Cloudflare Error 1006 / 1007 / 1008: Access denied — Your IP address has been banned (Cloudflare)10061012 — Cloudflare Error 1012: Access denied (Cloudflare)10121020 — Cloudflare Error 1020: Access Denied (Cloudflare)102040615 — Azure SQL: Cannot open server 'x' requested by the login. Client with IP address 'y' is not allowed to access the server (Error 40615) (Azure)40615DNS lookups take 5 seconds (timeout then retry) — Networking: Every connection pauses about 5 seconds — resolv.conf nameserver timeout, then fallback to the next DNS server (Networking)DNS lookups take 5 se…Frag needed and DF set (ICMP type 3 code 4) — Networking: ping: local error: message too long, mtu=1500 / Packet needs to be fragmented but DF set (Networking)Frag needed and DF se…ICMP Destination unreachable (Port unreachable) — Networking: ICMP Destination unreachable (Port unreachable) — UDP packet sent to a port where nothing is listening (Networking)ICMP Destination unre…Ping: Req…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.