3 Messages
Packet loss to a specific node 68.86.93.13
Hi,
Like the title says, I get packet loss at hop 6 of my tracert to 192.207.0.1. Is there a specific reason why this is happening? I have posted a picture of my tracert. Please let me know if anyone else is having this issue as well. I am located in Seattle/ Renton Washington.
BruceW
Gold Problem Solver
•
26K Messages
3 months ago
The next hop received all of the trace packets, so the "loss" 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 the hop beyond than one you are concerned about received the trace packets indicates that the router at that address is doing its job: forwarding data packets. That means the router's occasional 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 the next hop.
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
3 months ago
Quite a list!
I'm not sure what you mean by "packet loss at all hops with an average ping of 70ms on all hops to reddit.com". Could you describe what you are seeing there? What does a tracert (Windows) or traceroute (everything else) to Reddit look like? Here's mine:
If you have access to the Comcast/Xfinity equipment your service is connected to, consider buying a cable with factory installed F connectors and, just for testing, using it to connect directly from that equipment to your modem or gateway. If you can do that and still see the problem, then you've demonstrated that, whatever the problem is, it's up to them to fix it.
If you can't do that, try connecting as directly as possible to the farthest point you can reach, bypassing all splitters, surge protectors, and amplifiers they may be in the path, as these can cause problems.
And if that's not possible, please post your Internet plan speed and the following information from your modem or gateway (from http://192.168.100.1 or http://10.0.0.1):
Copy and pasted text is preferred over images. Be aware that, if you post any images, your message will be made Private for a time, as all images must be approved by the Forum Moderators before the messages containing them become generally visible.
Don't focus so much on packet "loss" at one intermediate hop. Unless the loss carries forward to later hops, it is probably not significant. It often means that the router at that hop was too busy to reply, or perhaps rate-limited to ignore most trace and ping packets.
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