Ping and tracert — how to find where a connection breaks down
Two simple command-line tools let you tell whether a problem is in your own local network, with your internet provider, or on the server you're trying to reach.
How ping and tracert differ
Ping sends a few small packets to a given address and checks whether a reply comes back and how long it takes. It answers: "can I even connect, and how fast."
Tracert shows the entire path your data takes to reach its destination — every router (a "hop") it passes through, along with the response time at each one. It answers: "exactly where along the way something is breaking."
How to use them
Open Command Prompt and check your router
Type ping 192.168.1.1 (or whatever default gateway address you found in the ipconfig article). No reply at this stage means the problem is in your own local network, before data even leaves for the internet.
Check the connection to the internet
Type ping google.com. If the router replies but this doesn't, the problem is somewhere between your network and the internet — most often on your provider's side.
Trace the route with tracert
Type tracert google.com. You'll see a list of routers along the path and the response time at each one. A jump in response time, or no response at all at a specific point, shows roughly where things slow down or break.
Don't panic over a single asterisk
Some routers along the way deliberately ignore these requests for security reasons — a single "Request timed out" at one hop is often normal and doesn't mean an outage. The real warning sign is no reply from that point all the way to the destination.
When it's a job for IT
- Ping to your own router (default gateway) fails — the problem is in your local network.
- Tracert cuts off early and never leaves your own network at all.
- Response times are very high (hundreds of milliseconds) consistently, not just once.
- Results look fine, but a specific app or site still doesn't work — that's no longer a network problem, but an application-side one.
Why it's worth including these results in your report
A screenshot or copied text of the ping and tracert output lets remote IT support narrow the diagnosis down to a specific segment of the route right away, instead of starting from scratch.
Couldn't fix it yourself?
Report the issue — it goes straight into our ticketing system, and our AI assistant assesses priority right away.