Terrible internet routing

---

@proxos666 wrote:

@Drakodemus 

if you are truely interested in your tracert results read page 29 and 32 in this document 

a tracert only displays the forward path and the return path can be totally different , the hops in-between are irrelevant if the final destination is fine.

---

from your document page 29 The Infamous BGP Scanner The Infamous BGP Scanner•On many platforms the slow-path data plane and the control-plane share the same resources.•And often don’t have the best schedulers for the CPU •As a result, control-plane activity such as BGP churn, CLI use, and periodic software processes can consume CPU and **slow the generation** of ICMP TTL Exceeds CPU and slow the generation of ICMP TTL Exceeds.•This results in random “spikes” in traceroute **latency**, which is often misinterpreted as a network issue.
it will add latency NOT DROP Packets.
Rate Limited ICMP Generation
Rate Limited ICMP Generation •Most routers also rate limit their ICMP generation •Often with arbitrary hard-coded limits. •Which may be insufficient under heavy traceroute load. •Juniper •Hard limit of 50pps per interface, 250pps on FPC3s •Hard limit of 500pps per PFE as of JUNOS 8.3+ •Foundry •Hard limit of 400pps per interface •Force10 •Hard limit of 200pps or 600pps per interface

If its hitting any of these limits then again its Overloaded or Dying.