2 Messages
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????
BruceW
Gold Problem Solver
•
26.3K Messages
13 days ago
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.
1
0
BruceW
Gold Problem Solver
•
26.3K Messages
13 days ago
Please see https://web.archive.org/web/20230802010554/https://www.dslreports.com/faq/14068:
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)
0
0