[horseman]

Originally Posted by craigj2k12

So are you saying the SH2 responds to pings from TBB at lower priority, or that TBB send SH2 pings at low priority?

He may not want to say that, but I will! However if/when Seph re-engages he'll no doubt quite correctly point out that he conversely does not currently experience that level of jitter in RouterMode.
I believe that may be explained and dependent on combination of T patch level and concurrent utilisation/load on DOCSIS chipset and thus the overhead of subsequent line conditioning on individual connections.

De-prioritising ICMP/traffic targeted specifically at a router rather than "beyond it" is after all not uncommon.

Like no doubt yourself and many others I don't rely on a single diagnostic either - I run other BQM/ping plotters in parallel in addition to SK monitors (I use the plural deliberately as perversely for a short period over last week or so I am literally running two seperate SK units in parallel! )

That's in addition to also monitoring typically a minimum of 2 or 3 other CMTS subscribers TBB/BQM monitors remotely in my Brighton cluster.

Just for your further amusement, early in May I was stress testing my first SH2(yes I'm now on my second) by saturating my upstream (that I knew had an open utilisation fault on both d/s & u/s) with following colourful result: