5 Messages
Packet Loss on a Specific Node in the Chicago Area
I have been experiencing packet loss for the past week and want to report it. This is the hop on my tracert that keeps getting dropped: be-314-arsc1.area4.il.chicago.comcast.net [96.108.34.137]
Please look into this.
XfinityRaul
Official Employee
•
1.9K Messages
2 years ago
Hello, @user_f70f70. I appreciate you making us aware of the packet loss issue you've been experiencing. Don't worry, you're definitely in the right place to figure out a solution to this problem. Have you by any chance attempted to reset the modem by using the amazing Xfinity app? How about power cycling the modem, have you tried that?
3
0
BruceW
Gold Problem Solver
•
26.4K Messages
2 years ago
Please post the complete tracert output.
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
0
EG
Expert
•
110.3K Messages
2 years ago
Concern moved here to the Home Networking help section.
0
0
BruceW
Gold Problem Solver
•
26.4K Messages
2 years ago
The target received and replied to all of the tracert packets and tracert received all of the replies, so the "loss" or "delay" at the intermediate hop is likely more apparent than real, and probably not significant. Please see https://www.dslreports.com/faq/14068.
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.
The fact that hops past than one you are concerned about respond quickly indicates that the router at that address is doing its job: forwarding data packets. That means the 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 subsequent hops.
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
0
user_smrz1x
2 Messages
1 year ago
I have correlated the same issue to the same node independently 90%+ packet loss at that hop. During spikes in latency it has the highest latency by 10x
0
0