WebAfrica - Evening Latency issues (from Cape Town)

Joker said:
Trace to www.news24.com:

Code: 
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  router.asus.com [192.168.10.1]
  2     *        *        *     Request timed out.
  3     4 ms     5 ms     6 ms  196.38.75.121
  4     *       20 ms    21 ms  196.38.75.122
  5    23 ms    27 ms    25 ms  196.38.77.88
  6     5 ms     5 ms     5 ms  mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.13]
[B]  7   419 ms   475 ms   665 ms  168.209.2.131[/B]
  8     6 ms     4 ms     5 ms  mweb-2.cinx.net.za [196.223.22.25]
  9     7 ms     7 ms     5 ms  197-84-7-54.cpt.mweb.co.za [197.84.7.54]
 10    13 ms    11 ms    10 ms  197-84-247-89.cpt.mweb.co.za [197.84.247.89]
 11     7 ms     6 ms     4 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
[B] 12   420 ms   579 ms   531 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146]
 13   494 ms   567 ms   540 ms  41-86-110-200.mweb.co.za [41.86.110.200][[/B]
Click to expand...


hop 7, peering device. what you are observing, control-plane policing puts icmp packets directed at the nexus supervisor inside a policer which shows up as a spike in a traceroute. its a predefined cisco template and they don't recommend tweaking it. forwarding plane is not affected at all.

i know what this peering device in ctn will be replaced soon which will take that spike away.

still waiting to hear from the optinet peeps re 12,13.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X