Visitor
•
2 Messages
IP re-route help, severe packet loss
I am having an issue with a specific comcast server in my pathway. The IP is 96.110.42.177. My upload and download speed are great but I am having severe packet loss exclusively related to this one server and I have been unable to force my gateway into a new IP for a new path. When I have tried to release and renew through command prompt my pathway remains the same. Chat agents and phone agents do not seem to understand what data packet loss is and have not been able to offer a solution. I have just been asking for an IT ticket to be opened and they do not seem able to do that successfully. There is no issue at my house or with any of the local server connections, only the one server in Chicago with the IP shown above. Any help is welcome, thank you.
BruceW
Gold Problem Solver
•
26.7K Messages
2 days 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.
2
0
BruceW
Gold Problem Solver
•
26.7K Messages
2 days ago
If your editor window doesn't have an "insert image" icon, you can post text, like so:
C>tracert -4 www.xfinity.com
Tracing route to e10994.dscx.akamaiedge.net [104.72.119.40] over a maximum of 30 hops:
1 3 ms 3 ms 3 ms router1 [192.168.1.1]
2 11 ms 8 ms 9 ms 96.120.9.181
3 10 ms 9 ms 8 ms po-301-1203-rur01.york.pa.pitt.comcast.net [24.124.216.181]
4 11 ms 10 ms 9 ms be-87-rar01.lowerpaxton.pa.pitt.comcast.net [96.110.25.9]
5 19 ms 18 ms 18 ms be-33-ar01.pittsburgh.pa.pitt.comcast.net [69.139.168.185]
6 18 ms 17 ms 18 ms 50.233.178.118
7 18 ms 18 ms 20 ms lo1.r02.stem01.pit01.fab.netarch.akamai.com [23.213.207.25]
8 18 ms 18 ms 18 ms lo1.r02.spine02.pit01.fab.netarch.akamai.com [23.213.207.13]
9 18 ms 17 ms 17 ms lo1.r02.leaf01.pit01.fab.netarch.akamai.com [23.213.207.5]
10 24 ms 17 ms 18 ms lo1.r03.tor01.pit01.fab.netarch.akamai.com [23.213.207.30]
11 18 ms 17 ms 18 ms a104-72-119-40.deploy.static.akamaitechnologies.com [104.72.119.40]
Trace complete.
ETA: The other thing you could so is post the image on a site like http://imgur.com/, and then post a link to it here.
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)
1
0
BruceW
Gold Problem Solver
•
26.7K Messages
1 day ago
@Zaphod_Joe: Your traces for this site show no packet loss at the destination. The apparent loss at hops along the way are probably not significant.
Please see https://web.archive.org/web/20230802010554/https://www.dslreports.com/faq/14068:
The fact that hops after the "loss" hops 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 traces do 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)
1