Ridiculous Ping Spikes on Comcast

rkingrum · Nov 14, 2013

My internet on comcast has gradually been going down hill, and yet they insist that nothing is wrong. I'm not sure what to do about this issue, or even if there is anything I can do. These are my tracert results with Google.com.

C++:

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400e:c02::68]
over a maximum of 30 hops:

  1    31 ms    60 ms    45 ms  2601:1:a080:1f2:5e57:1aff:fe93:5f31
  2   112 ms   114 ms    93 ms  2001:558:6040:4e::1
  3   740 ms   137 ms    52 ms  te-4-3-ur01.fortcollins.co.denver.comcast.net [2001:558:1c2:98::1]
  4     *        *      166 ms  te-0-11-0-0-ar02.denver.co.denver.comcast.net [2001:558:1c0:10::1]
  5   279 ms    81 ms   121 ms  he-0-9-0-0-cr01.denverqwest.co.ibone.comcast.net [2001:558:0:f6ea::1]
  6   312 ms    59 ms    63 ms  he-3-13-0-0-cr01.denver.co.ibone.comcast.net [2001:558:0:f652::1]
  7   130 ms   100 ms    83 ms  xe-3-0-0-0-pe01.910fifteenth.co.ibone.comcast.net [2001:558:0:f886::2]
  8   826 ms   153 ms   119 ms  2001:559:0:9::6
  9    80 ms   144 ms    83 ms  2001:4860::1:0:7a4
 10    53 ms    63 ms   341 ms  2001:4860::8:0:3426
 11   191 ms   249 ms   251 ms  2001:4860::8:0:252d
 12   176 ms   315 ms   251 ms  2001:4860::8:0:2b60
 13   229 ms   176 ms   204 ms  2001:4860::2:0:ab
 14     *        *        *     Request timed out.
 15  1251 ms   301 ms   251 ms  pd-in-x68.1e100.net [2607:f8b0:400e:c02::68]

Trace complete.

bill001g · Nov 14, 2013

You need to run continuous pings to each hop in the trace to see which one in introducing the delays. Anything past the first device that is causing issues is corrupted. So if a trace was good until hop 5 and hop 5 was having a issue you cannot trust any trace data beyond it.

In general it appears it could all be caused by hop 1 in the trace. That already has a lot of jitter in it. This is a huge number for first hop and if you did not say it was comcast I would suspect you were running wireless broadband. The first hop in most traces is the time between the end device and the router in the house and is usually less than 1ms. The second hop is normally the connection to the ISP and is generally well under 10ms and is very very consistent with no variations. Anything past that is in the ISP network or the internet in general, although it may be interesting to look at there is little you can do to get anything fixed in provider network.

The key issue I would have is why the first hop is so high in the first place if this is wireless connection in your house then that is your problem

Search

Ridiculous Ping Spikes on Comcast

rkingrum

Honorable

bill001g

Titan

TRENDING THREADS

Latest posts

Moderators online

Share this page