New Poster
•
2 Messages
Extreme Latency Issues
Posted this on the reddit, but I thought I'd post here as well since the reddit appears to be completely ignored.
This is happening again this morning as it has happened throughout the day periodically for the last few days. Would you please address the faulty node at cm-1-acr02.castlerock.co.denver.comcast.net
ASA-CR# sh ip
System IP Addresses:
Vlan2 outside 24.9.46.33255.255.254.0
ASA-CR# sh route
Gateway of last resort is 24.9.46.1 to network 0.0.0.0
ASA-CR# ping outside 24.9.46.1
Sending 5, 100-byte ICMP Echos to 24.9.46.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 10/16/30 ms
C:\Users\auser>tracert 8.8.8.8
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 2 ms 2 ms 4 ms 172.30.254.254
2 1057 ms 692 ms 263 ms cm-1-acr02.castlerock.co.denver.comcast.net [96.120.13.57]
3 66 ms 13 ms 13 ms ae-252-1210-rur02.castlerock.co.denver.comcast.net [96.110.194.109]
4 73 ms 12 ms 15 ms ae-2-rur01.castlerock.co.denver.comcast.net [68.85.89.233]
5 16 ms 17 ms 17 ms ae-10-ar01.denver.co.denver.comcast.net [68.86.104.97]
6 16 ms 12 ms 20 ms be-36021-cs02.1601milehigh.co.ibone.comcast.net [96.110.43.245]
Responses
BruceW
Gold Problem Solver
•
22.4K Messages
6 m ago
The high RTT at hop #2 doesn't extend to later hops, so it's probably not significant. See https://www.dslreports.com/faq/14068. The device at hop #2 is most likely giving low priority to ping and trace packets and higher priority to actual data packets. If it was dropping data packets you would see high RTT and/or packet loss at all the hops beyond that one.
0
ColoHikerGuy
New Poster
•
2 Messages
6 m ago
If it's shedding packets, ICMP or otherwise, for any reason that reason is not a good one. ICMP packets aren't normally dropped or showing high latency, so clearly there is an intermittent resource issue with the node either causing some pretty harsh queuing to kick in or straight packet hemorraghing.
There was a scheduled maintenance for our area last week. It doesn't appear to have solved the problem:
0
0