Forum Discussion
BrianM
6 years agoModerator
This looks to be resolved now. I am not seeing any further packet loss to your modem.
Brian
Cox Support
yolesnoobs
6 years agoNew Contributor III
I'm running ping tests and still seeing packet loss. May need to run the test for 5+ min to see it.
- Allan6 years agoModeratorHello. We are unable to replicate this packet loss issue from our side and are not seeing any unusual latency from the modem. Please have a device perform an additional ping plotter test and post back with the results. Thanks. -Allan Cox Support Forums Moderator.
- yolesnoobs6 years agoNew Contributor III
- yolesnoobs6 years agoNew Contributor III
Games are unplayable at the moment rubberbanding everywhere. Just ran another pingplotter with packet loss: https://imgur.com/a/o9sufco. I really need this fixed please.
- Becky6 years agoModeratorHi Xuboji, Hop 5 is the last hop on the Cox network. Since Hop 5 completes with zero packet loss, the minor packet loss shown in Hops 2 through 4 is interpreted as ICMP deprioritization instead of packet loss. If the packets were really being lost in Hops 2 through 4, how would they get to Hop 5? Some servers and routers down-prioritize ICMP echo requests. The traceroute hop that corresponds to a server down-prioritizing an ICMP echo request may show packet loss and/or latency. If the destination isn't affected, all latency and packet loss is an artifact of router configuration (or other device configuration) and is not a problem. This is called ICMP deprioritization. Hop 6 through the end of the trace are on Amazon’s network. The timeouts once the trace reaches the Amazon network are to be expected. Not all Amazon Web Services servers return ping requests; they block ICMP packets for network security reasons. Your PingPlotter doesn’t show any abnormalities on the Cox network. -Becky, Cox Support Forums Moderator
Related Content
- 7 months ago
- 12 years ago
- 6 years ago