Question Explain this Trace Route to me

Aug 23, 2021
2
0
10
0
I've been having ping spikes late in the evening throughout the night to where my 500mbit/500mbit won't even pull 10mbit both ways. I ran a trace route to google.com. Ill post the the image to where the service runs correctly, and ill post the image to where it doesn't run at all. If I'm reading this tracert right, it's on the ISPs end, correct? The issue happens on Line 6. If im reading this correctly, Line 1 is you local router, 2 is POP Router, and 3-6 looks like the ISP has a HUD somewhere housing routers/equipment that handles traffic, before getting out to the "Internet"
PING-3 PING-4
 
try switching to google dns?
https://developers.google.com/speed/public-dns

btw that request timed out doesnt means its not working, that server just doesnt support ping so you get stars with request timed out
Code:
C:\Users\kerbe>tracert 108.177.122.101

Tracing route to 108.177.122.101 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     9 ms     9 ms    10 ms  ip-78-45-242-1.net.upcbroadband.cz [78.45.242.1]
  3     8 ms     7 ms     7 ms  ip-86-49-0-161.net.upcbroadband.cz [86.49.0.161]
  4    13 ms    13 ms     9 ms  ip-84-116-222-216.net.upc.cz [84.116.222.216]
  5     9 ms    11 ms    11 ms  sitlG01-vla2122.net.upc.cz [84.116.223.123]
  6     *        *       10 ms  te0-0-1-0.sitnb00.vodafone.cz [217.77.160.41]
  7    13 ms    18 ms    13 ms  142.250.164.176
  8    11 ms    13 ms    13 ms  172.253.50.253
  9    10 ms    13 ms     9 ms  108.170.245.35
10    20 ms    19 ms    16 ms  209.85.253.0
11    21 ms    19 ms    17 ms  108.170.228.9
12    31 ms    29 ms    27 ms  209.85.253.185
13   105 ms   104 ms   104 ms  142.250.209.112
14   114 ms   110 ms   112 ms  216.239.56.111
15   120 ms   117 ms   116 ms  142.251.51.36
16   125 ms   118 ms   117 ms  142.251.51.8
17   118 ms   117 ms   117 ms  142.250.211.181
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     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27   116 ms   115 ms   112 ms  108.177.122.101

Trace complete.
otherwise your 6th hop is busy, which is ISP issue
 
Last edited:
Aug 23, 2021
2
0
10
0
try switching to google dns?
https://developers.google.com/speed/public-dns

btw that request timed out doesnt means its not working, that server just doesnt support ping so you get stars with request timed out
Code:
C:\Users\kerbe>tracert 108.177.122.101

Tracing route to 108.177.122.101 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     9 ms     9 ms    10 ms  ip-78-45-242-1.net.upcbroadband.cz [78.45.242.1]
  3     8 ms     7 ms     7 ms  ip-86-49-0-161.net.upcbroadband.cz [86.49.0.161]
  4    13 ms    13 ms     9 ms  ip-84-116-222-216.net.upc.cz [84.116.222.216]
  5     9 ms    11 ms    11 ms  sitlG01-vla2122.net.upc.cz [84.116.223.123]
  6     *        *       10 ms  te0-0-1-0.sitnb00.vodafone.cz [217.77.160.41]
  7    13 ms    18 ms    13 ms  142.250.164.176
  8    11 ms    13 ms    13 ms  172.253.50.253
  9    10 ms    13 ms     9 ms  108.170.245.35
10    20 ms    19 ms    16 ms  209.85.253.0
11    21 ms    19 ms    17 ms  108.170.228.9
12    31 ms    29 ms    27 ms  209.85.253.185
13   105 ms   104 ms   104 ms  142.250.209.112
14   114 ms   110 ms   112 ms  216.239.56.111
15   120 ms   117 ms   116 ms  142.251.51.36
16   125 ms   118 ms   117 ms  142.251.51.8
17   118 ms   117 ms   117 ms  142.250.211.181
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     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27   116 ms   115 ms   112 ms  108.177.122.101

Trace complete.
otherwise your 6th hop is busy, which is ISP issue
When you say the 6th hop is busy, that means more traffic than bandwidth correct? Meaning, the packets are buffering, causing the delay, or failing equipment? Happens the same time every night lol. I'll try the google DNS, just to try it. The IP addresses of the hops 3-6 are all in the same location so ill contact ISP and see if i can get this over to a network engineer and see if they'll look into it.
 
When you say the 6th hop is busy, that means more traffic than bandwidth correct? Meaning, the packets are buffering, causing the delay, or failing equipment? Happens the same time every night lol. I'll try the google DNS, just to try it. The IP addresses of the hops 3-6 are all in the same location so ill contact ISP and see if i can get this over to a network engineer and see if they'll look into it.
that 6th hop is some routing device which connects bunch of people...by being busy it means too many people connected overusing its hardware
sure contact ISP if they can reroute you
 

ASK THE COMMUNITY

TRENDING THREADS