ICMP response time from a router/device is not a great way to judge if there is an issue or not. The devices generally have control plane policing and responding to ICMP is not prioritized at all. I would suggest your engineer setup something on their end of the connection that you can ping, and start there. Leverage something like smoke ping to something on their LAN, or even the public IP on their RG/Modem. Kevin On Tue, Feb 7, 2023 at 15:01 Austin Ayers via NANOG <nanog@nanog.org> wrote:
Hello all,
One of my NetOps engineers resides in Lima, Ohio and they are receiving terrible bufferbloat, packet loss, and random disconnects.
I have been pinging 24.33.160.213 (Lima, OH Spectrum/Chart Node) and it's rejecting a ton of packets. This has been going on for weeks.
Node having problems: lag-1.limaohid01h.netops.charter.com
NOC seems like they don't care, same with OSP in the field.
There is no reason why this hop (#13) should have up to 613ms ping times.
Thank you, Austin