U

Friday, March 21st, 2025 6:05 PM

70% packet loss.

HOP 6 -     be-36141-cs04.seattle.wa.ibone.comcast.net

HOP 7 -     be-2411-pe11.seattle.wa.ibone.comcast.net

Ive replaced ethernet cables, had a tech come out to replace line outside. and heard about pingplotter and im showing 70% packet loss is there anyway we can get this resolved????

Gold Problem Solver

 • 

26.3K Messages

13 days ago

...  im showing 70% packet loss ...

Please post the complete trace from origin to target, including the statistics (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.

2 Messages

@BruceW​  1     *       <1 ms     *     GT-BE98_Pro-FD98 [192.168.50.1]
  2    12 ms     8 ms     9 ms  10.138.221.67
  3     9 ms    10 ms    11 ms  po-322-328-rur402.tacoma.wa.seattle.comcast.net [96.108.165.57]
  4     9 ms     9 ms     8 ms  po-400-xar02.tacoma.wa.seattle.comcast.net [24.124.128.57]
  5    12 ms    11 ms    12 ms  be-303-arsc1.seattle.wa.seattle.comcast.net [24.124.128.253]
  6     *        *       12 ms  be-36141-cs04.seattle.wa.ibone.comcast.net [68.86.93.13]
  7     *        *       12 ms  be-2411-pe11.seattle.wa.ibone.comcast.net [96.110.32.238]
  8     *        *        *     Request timed out.
  9    13 ms    11 ms    12 ms  142.251.70.103
 10    13 ms    12 ms    12 ms  209.85.254.237
 11    12 ms    11 ms    11 ms  dns.google [8.8.8.8]

Gold Problem Solver

 • 

26.3K Messages

13 days ago

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 6-8 received trace packets indicates that those 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.

(edited)

forum icon

New to the Community?

Start Here