So many 'request timed outs' on tracert


Jul 16, 2017
I've been having a networking issue for so long now and my ISP is no help at all because they find no problem. I'm constantly getting fluctuating ping between 25ms - 12,000ms.
Every couple mins it would go into the hundreds and on some occassions would climb high into the thousands.
I ran a tracert but I don't understand much of it but I have gotten multiple request timed outs. If someone could please tell me what the issue looks like I'd appreciate it thanks.

Tracing route to []
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms bthub []
2 * * * Request timed out.
3 * * * Request timed out.
4 13 ms 14 ms 14 ms
5 19 ms 15 ms 16 ms []
6 15 ms 11 ms 12 ms
7 13 ms 19 ms 16 ms []
8 16 ms 16 ms 13 ms
9 16 ms 14 ms 14 ms
10 92 ms 88 ms 97 ms
11 103 ms 104 ms 107 ms
12 112 ms 111 ms 112 ms
13 112 ms 113 ms 112 ms
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 118 ms 112 ms 116 ms []

Trace complete.
If you get pings that go into the thousands you likely are running on wireless and that is causing that issue. You will get delays in the internet but they seldom go above a few hundred ms.

First before you get too far into this realize you can only fix things that are wrong in your house and things that are wrong with your ISP...assume they want to fix their stuff. Many of the things you find in a tracert are in different ISP or companies you can do nothing about.

Timeout mean little in a tracert especially when they consistently happen at the same point. This just means some device is configured to not respond to you, many times a firewall but it can be any router in the path because it takes cpu away from doing its real job of passing traffic.

Tracert is a very simplistic tool it does not run enough traffic to find problems many times. You could try things like pathping but you are better off doing this manually because then you will understand better.

I would open multiple cmd windows and leave continuous ping run. Normally I would say to ping hop 2 since that is your connection to the ISP but your ISP is hiding his routers which makes things hard. So to start I would leave pings run to hop 1, hop 4 and the final destination.

If you see problems in hop1 then it is inside your house, If that is ok but hop 4 has a problem you can try to call your ISP and see if they can find a problem to your house. If you see no issues in the first 2 but still issues to the final location it is someplace other than the simple to fix locations. You can continue to ping other hops in the trace but if you were to find a problem say between the ISP ATT and Level3 what could you do it not like you can call them up.



The request timed out is nothing in of itself. Just means the server doesn't respond to request for information.

The ping thing typically occurs when there is traffic on your local network. How many people are using the same internet connection?


Jul 16, 2017

Only 2 people use connection