Visitor
•
2 Messages
lag and packet loss
I’m seeing consistent packet loss and latency instability upstream of my local network in central MA, confirmed with repeatable testing on a wired PC.
• Ping to my gateway (192.168.0.1) is 0% loss, sub-1 ms.
• Ping to 8.8.8.8 shows ~4% packet loss with intermittent timeouts and jitter.
• Traceroute shows normal latency through local and regional Comcast hops in MA and NY, terminating at be-3212-pe12.111eighthave.ny.ibone.comcast.net (111 8th Ave, NYC), followed by a non-responsive hop at the Comcast → Google peering/aggregation point, after which traffic resumes on Google’s network.
This indicates packet loss occurring at or immediately after the Comcast backbone peering handoff at 111 8th Ave, not within my LAN, modem, or premises wiring. This is severely impacting real-time traffic (gaming/voice).
BruceW
Gold Problem Solver
•
27K Messages
17 hours ago
Please post the complete traceroute (or tracert) for a path that includes this router. From origin to target, include the statistics (IP address, hostname, RTT, packet loss, etc.) for each 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
•
27K Messages
10 hours ago
All the packets sent appear to have reached the target, meaning the "loss" is more apparent than real. Apparent loss at a hop along the way is probably not significant.
Please see https://web.archive.org/web/20230802010554/https://www.dslreports.com/faq/14068:
The fact that hops after the "loss" hop are receiving packets indicates that the router at hop #8 is doing its job: forwarding data packets. The occasional delay in or failure to respond to trace packets, while annoying, is most likely not actually disrupting data transfer. If it was we'd see high RTT values and/or packet loss in the following hops, and we don't. You may indeed have a communication problem, but the trace posted does not show that.
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 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):
If you are using a rented Comcast/Xfinity device, you may need to follow the steps in https://www.xfinity.com/support/articles/admin-tool-access to get access to the device
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.
Are you connecting via Wifi or Ethernet? If Wifi, it's best to switch to an Ethernet cable connection if possible for testing. That would allow you to determine whether the problem is the Wifi signal or the link between your modem or gateway and Comcast's network. Network connection problems that affect both Ethernet and Wifi devices are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power.
The Internet Troubleshooting Tips post may be helpful.
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.
(edited)
0