10 Messages
Ping spikes and Packet Loss
I am having issues with our home network. There is consistent packet loss and ping spikes on this hop: be-309-arsc1.area4.il.chicago.comcast.net [162.151.45.109]
Here are the tracert commands I ran:
C:\Users\richa>tracert 8.8.8.8
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 5 ms 2 ms 1 ms 10.0.0.1
2 11 ms 11 ms 9 ms 96.120.25.177
3 12 ms 9 ms 10 ms po-309-1209-rur301.wchicago.il.chicago.comcast.net [68.87.208.189]
4 10 ms 9 ms 8 ms po-2-rur302.wchicago.il.chicago.comcast.net [96.216.150.150]
5 9 ms 8 ms 8 ms po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
6 * * * Request timed out.
7 14 ms 19 ms 13 ms be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
8 20 ms 13 ms 13 ms c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
9 19 ms 13 ms 14 ms 142.250.209.145
10 14 ms 14 ms 15 ms 142.251.60.17
11 30 ms 14 ms 13 ms dns.google [8.8.8.8]
Trace complete.
C:\Users\richa>tracert 8.8.8.8
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 5 ms 1 ms 1 ms 10.0.0.1
2 51 ms 10 ms 13 ms 96.120.25.177
3 10 ms 8 ms 10 ms po-309-1209-rur301.wchicago.il.chicago.comcast.net [68.87.208.189]
4 15 ms 10 ms 9 ms po-2-rur302.wchicago.il.chicago.comcast.net [96.216.150.150]
5 9 ms 9 ms 14 ms po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
6 * * 39 ms be-309-arsc1.area4.il.chicago.comcast.net [162.151.45.109]
7 11 ms 13 ms 13 ms be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
8 15 ms 14 ms 14 ms c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
9 16 ms 13 ms 13 ms 142.250.209.145
10 16 ms 20 ms 13 ms 142.251.60.17
11 18 ms 15 ms 19 ms dns.google [8.8.8.8]
Trace complete.
C:\Users\richa>tracert 8.8.8.8
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 4 ms 2 ms <1 ms 10.0.0.1
2 11 ms 9 ms 11 ms 96.120.25.177
3 18 ms 15 ms 9 ms po-309-1209-rur301.wchicago.il.chicago.comcast.net [68.87.208.189]
4 12 ms 8 ms 8 ms po-2-rur302.wchicago.il.chicago.comcast.net [96.216.150.150]
5 15 ms 8 ms 8 ms po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
6 * * * Request timed out.
7 14 ms 12 ms 12 ms be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
8 17 ms 17 ms 14 ms c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
9 24 ms 16 ms 13 ms 142.250.209.145
10 13 ms 13 ms 13 ms 142.251.60.17
11 14 ms 13 ms 20 ms dns.google [8.8.8.8]
Trace complete.
BruceW
Gold Problem Solver
•
26K Messages
2 months ago
Trace packets are reaching the target, so the "loss" at hop 6 is likely more apparent than real, and probably not significant. Please see https://www.dslreports.com/faq/14068. The fact that hops beyond than ones you are concerned received the trace packets indicates that the router at that address is doing its job: forwarding data packets. The hop 6 router's occasional delay in or failure to respond to trace packets, while annoying, is most likely not actually slowing down data transfer. If it was we'd see high RTT values and/or packet loss in all subsequent hops.
Interpreting trace results is tricky. What appears to be "late" or is reported as "lost" could mean 1) the packet did not reach or was delayed in reaching that hop, or 2) the router at that hop didn't reply or was slow to reply, or 3) the reply from that hop didn't make it back or was delayed in making it back to the trace program.
Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.
1
BruceW
Gold Problem Solver
•
26K Messages
2 months ago
Not really. I'm not Comcast and have no way of knowing how that router is programed or of running diagnostics on it. All I have to work with is the trace information posted, and, as explained previously, it is not consistent with what we'd expect to see if the router was causing packet loss and ping spikes. It's possible that the router is misbehaving, but if it is the traces don't show that.
The most we can say is that trace packets sent to that router are not resulting in the response packets we'd expect to see. Why, we can only guess, and my best guess is that the router is programmed to give low priority to trace packets. Comcast could determine what's happening here, but that would cost them a few pennies, so it would surprise me if they bothered to check. Regrettably, in 17 years of reading these forums, I've never seen them respond to the many, many similar complaints.
Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.
0
XfinityShawn
Official Employee
•
1K Messages
2 months ago
@Odyssey34 Is this happening when you're doing a specific task (like working, streaming, gaming etc)?
3
0
Odyssey34
10 Messages
1 month ago
I took a trip to the store and replaced the router. The issue is still there.
2
0
Odyssey34
10 Messages
22 days ago
The issue went away for about a week and it has now returned.
0
0
Odyssey34
10 Messages
22 days ago
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 10.0.0.1
2 11 ms 9 ms 8 ms 96.120.25.177
3 13 ms 8 ms 12 ms po-309-1210-rur302.wchicago.il.chicago.comcast.net [69.139.184.29]
4 11 ms 9 ms 9 ms po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
5 * * * Request timed out.
6 16 ms 22 ms 14 ms be-501-ar01.area4.il.chicago.comcast.net [96.216.150.114]
7 34 ms 27 ms 18 ms c-50-171-101-226.unallocated.comcastbusiness.net [50.171.101.226]
8 17 ms 12 ms 12 ms 142.250.209.27
9 14 ms 15 ms 15 ms 142.251.60.201
10 17 ms 12 ms 12 ms dns.google [8.8.8.8]
Trace complete.
C:\Users\richa>tracert 8.8.8.8
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 10.0.0.1
2 18 ms 8 ms 17 ms 96.120.25.177
3 12 ms 8 ms 10 ms po-309-1210-rur302.wchicago.il.chicago.comcast.net [69.139.184.29]
4 14 ms 10 ms 9 ms po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
5 * * 77 ms be-309-arsc1.area4.il.chicago.comcast.net [162.151.45.109]
6 13 ms 13 ms 12 ms be-501-ar01.area4.il.chicago.comcast.net [96.216.150.114]
7 18 ms 13 ms 17 ms c-50-171-101-226.unallocated.comcastbusiness.net [50.171.101.226]
8 13 ms 11 ms 12 ms 142.250.209.27
9 15 ms 14 ms 14 ms 142.251.60.201
10 16 ms 16 ms 17 ms dns.google [8.8.8.8]
0
0
Odyssey34
10 Messages
22 days ago
This same node is continually causing issues.
be-309-arsc1.area4.il.chicago.comcast.net [162.151.45.109]
1
0