Skip to main content
silvaro
1st Topic

Visitor

 • 

2 Messages

Thursday, December 18th, 2025 2:14 AM

>60% packet loss on hop 9

While I am streaming and especially playing games I start noticing the packet loss. I did multiple traceroutes and on hop 9 it loses over 60% of the packets (c-50-170-111-230.unallocated.comcastbusiness) right after it reaches  Cloudflare. This is an ongoing issue and it seems like many users have encountered the same issue. What are the possible solutions.
Thanks

Question

 • 

Updated 

19 hours ago

25

3

0

Oldest First
Selected Oldest First
BruceW

Gold Problem Solver

 • 

27K Messages

4 days ago

... on hop 9 it loses over 60% of the packets ...

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.

0

0

XfinityChelseaB

Official Employee

 • 

2.1K Messages

2 days ago

Hello @silvaro, Thanks so much for taking a moment out of your day to leave a post on our community forum and we would be happy to help. Are you still having issues with packet loss? 

2

BruceW

Gold Problem Solver

 • 

27K Messages

19 hours ago

... packet loss ...

All the packets sent appear to have reached the target (0.0% loss), meaning the "loss" is more apparent than real. The 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:

Why am I seeing so much packet loss in my provider's network?

If you are also seeing packet loss from these points all the way to the final hop of your test, that points to a problem on the device first showing packet loss or on the inbound connection to that device. However, if you are not seeing packet loss all the way to the final hop, this apparent packet loss may not be an issue.
Some providers are rate-limiting how often they respond with the TTL-exceeded ICMP packets used by traceroute and similar tools like the Packet Loss Test. This is done to prevent attacks against these routers, since responding to these packets requires much more CPU time than simply forwarding the packet does. If the router is set up to rate-limit, it will respond to a certain number of traceroute packets per second, and once that many have been received, it will stop responding to them for that second -- which will appear as packet loss. You are not losing any "real" traffic, assuming the final hop of your traceroute isn't showing any loss.

The fact that hops after the "loss" hop are receiving packets indicates that the routers are doing their job: forwarding data packets. The 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 the following hops, and we don't. You may indeed have a communication problem, but the trace 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 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

forum icon

New to the Community?

Start Here