https://community.hpe.com/t5/communications-and-wireless/wan-latency/m-p/3895740#M5318 Get a copy of netperf - <A href="http://www.netperf.org/ftp.netperf.org" target="_blank">www.netperf.org/ftp.netperf.org</A> and configure it for histograms --enable-histograms, then run a TCP_RR test with a verbosity level of 2 and look at the resulting histogram and transaction per second rate. Pick a request/response size similar to that of the pings you were sending.<BR /><BR />Or... on the client, run tcpdump and look at the packet trace Fri, 10 Nov 2006 10:24:18 GMT rick jones 2006-11-10T10:24:18Z https://community.hpe.com/t5/communications-and-wireless/wan-latency/m-p/3895739#M5317 Hi,<BR />We have a 'private' WAN link between two sites. Recently I noticed the ping trip times have increased by around 70%. Our service provide tells me that a ping has a lower priority than interactive traffic so I should not judge the circuit latency using ping. Does anyone have any ideas as to how I could confirm the telnet latency times between client on the remote site and the host hp-ux box?<BR />Many thanks. Thu, 09 Nov 2006 14:19:00 GMT https://community.hpe.com/t5/communications-and-wireless/wan-latency/m-p/3895739#M5317 Michael Poland_3 2006-11-09T14:19:00Z https://community.hpe.com/t5/communications-and-wireless/wan-latency/m-p/3895740#M5318 Get a copy of netperf - <A href="http://www.netperf.org/ftp.netperf.org" target="_blank">www.netperf.org/ftp.netperf.org</A> and configure it for histograms --enable-histograms, then run a TCP_RR test with a verbosity level of 2 and look at the resulting histogram and transaction per second rate. Pick a request/response size similar to that of the pings you were sending.<BR /><BR />Or... on the client, run tcpdump and look at the packet trace Fri, 10 Nov 2006 10:24:18 GMT https://community.hpe.com/t5/communications-and-wireless/wan-latency/m-p/3895740#M5318 rick jones 2006-11-10T10:24:18Z