Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
A crude method is using traceroute, watching for unexpected latency jumps between hops. If you control devices along the path, and enable SLA responders, your timing information would be much more accurate. (Also, do I recall some Cisco IP SLA has something like traceroute?)
A common cause of latency spikes is queuing congestion. Remediation can be difficult and expensive although if not all traffic needs same service level performance, using QoS might be sufficient for the critical traffic.
