Frequent Visitor
•
15 Messages
high ping and packet loss
Hi,
The last several days I have been experiencing high ping and sometimes packet loss. The problem is more obvious if I ping bing.com. Pinging google.com gives better results. My modem signals seem to be ok. Appreciate any help here.
Thanks.
Xiaofeng_Xu
Frequent Visitor
•
15 Messages
3 years ago
Ping results below. As you can see, the results are vastly different.
PING bing.com (13.107.21.200): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 13.107.21.200: icmp_seq=0 ttl=118 time=2025.828 ms
64 bytes from 13.107.21.200: icmp_seq=1 ttl=118 time=1145.836 ms
64 bytes from 13.107.21.200: icmp_seq=2 ttl=118 time=143.030 ms
64 bytes from 13.107.21.200: icmp_seq=3 ttl=118 time=102.859 ms
64 bytes from 13.107.21.200: icmp_seq=4 ttl=118 time=16.007 ms
64 bytes from 13.107.21.200: icmp_seq=5 ttl=118 time=12.954 ms
64 bytes from 13.107.21.200: icmp_seq=6 ttl=118 time=968.728 ms
64 bytes from 13.107.21.200: icmp_seq=7 ttl=118 time=732.121 ms
64 bytes from 13.107.21.200: icmp_seq=8 ttl=118 time=1593.017 ms
64 bytes from 13.107.21.200: icmp_seq=9 ttl=118 time=764.634 ms
64 bytes from 13.107.21.200: icmp_seq=10 ttl=118 time=306.109 ms
64 bytes from 13.107.21.200: icmp_seq=11 ttl=118 time=337.326 ms
64 bytes from 13.107.21.200: icmp_seq=12 ttl=118 time=46.328 ms
64 bytes from 13.107.21.200: icmp_seq=13 ttl=118 time=2116.417 ms
64 bytes from 13.107.21.200: icmp_seq=14 ttl=118 time=2316.318 ms
PING google.com (172.217.0.174): 56 data bytes
64 bytes from 172.217.0.174: icmp_seq=0 ttl=56 time=11.249 ms
64 bytes from 172.217.0.174: icmp_seq=1 ttl=56 time=10.499 ms
64 bytes from 172.217.0.174: icmp_seq=2 ttl=56 time=10.661 ms
64 bytes from 172.217.0.174: icmp_seq=3 ttl=56 time=11.709 ms
64 bytes from 172.217.0.174: icmp_seq=4 ttl=56 time=16.021 ms
64 bytes from 172.217.0.174: icmp_seq=5 ttl=56 time=10.707 ms
64 bytes from 172.217.0.174: icmp_seq=6 ttl=56 time=10.744 ms
64 bytes from 172.217.0.174: icmp_seq=7 ttl=56 time=10.837 ms
64 bytes from 172.217.0.174: icmp_seq=8 ttl=56 time=12.385 ms
64 bytes from 172.217.0.174: icmp_seq=9 ttl=56 time=16.718 ms
64 bytes from 172.217.0.174: icmp_seq=10 ttl=56 time=10.851 ms
64 bytes from 172.217.0.174: icmp_seq=11 ttl=56 time=13.541 ms
64 bytes from 172.217.0.174: icmp_seq=12 ttl=56 time=12.240 ms
64 bytes from 172.217.0.174: icmp_seq=13 ttl=56 time=10.708 ms
64 bytes from 172.217.0.174: icmp_seq=14 ttl=56 time=10.801 ms
64 bytes from 172.217.0.174: icmp_seq=15 ttl=56 time=11.012 ms
64 bytes from 172.217.0.174: icmp_seq=16 ttl=56 time=10.386 ms
64 bytes from 172.217.0.174: icmp_seq=17 ttl=56 time=10.548 ms
64 bytes from 172.217.0.174: icmp_seq=18 ttl=56 time=10.806 ms
64 bytes from 172.217.0.174: icmp_seq=19 ttl=56 time=14.160 ms
0
0
EG
Expert
•
110.3K Messages
3 years ago
It's very likely that two different routes are being traversed to get to those two different server destinations. Posting the output of a traceroute to the IP address of that first host's server will perhaps reveal where the excessive latency / packet loss is occuring.
1
0
user_9e8af1
Visitor
•
1 Message
3 years ago
I've been having the same issue for months. I've had several Xfinity technicians come out. They think it's an issue on the poll out on the street. I can't seem to get help resolving the issue.
2
0
EG
Expert
•
110.3K Messages
3 years ago
Ok so the *alleged* excessive latency is in the Comcast regional router / webspace (hop number 4) but it does not carry through to the farther upstream routers or the destination server, so it is likely to be only ICMP packet based deprioritization / rate limiting that is being done by this router and is not true latency.
(edited)
2
0
EG
Expert
•
110.3K Messages
3 years ago
That could be due to a more local RF signal / connection quality / upstream impairment problem with the system rather than a being transit routing problem.
What do the modem's signal stats look like ? Try getting them here; http://192.168.100.1 or here http://10.0.0.1
Please copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.
What is the exact make and model number of the modem / gateway device ?
Is this with a WiFi connection ?
1
0
EG
Expert
•
110.3K Messages
3 years ago
Those are all good but you didn't include the upstream power level values ?
And are there any modem RF error log entries being shown ? If so, please post them as well in their entirety (copy and paste them, don't post a screenshot) but redact the CM MAC and the CMTS MAC addresses for your privacy. They are considered to be personal information. The posting of personally identifying information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically.
1
0
EG
Expert
•
110.3K Messages
3 years ago
@Xiaofeng_Xu
Ok so even though the signal status values looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) / an upstream channel / return path impairment somewhere.
There are other signal stat values that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
1
0
EG
Expert
•
110.3K Messages
3 years ago
@Xiaofeng_Xu Quite welcome !
0
0