This read-only counter tallies the number of times packets have been delayed because a pipe, or a specific user within it, has used up its allotted bandwidth, noting per its own description that a single packet may be counted as delayed more than once. A high or fast-rising value indicates that pipe is actively throttling traffic rather than just carrying it unimpeded. For example, a spike in clvPipeDelayedPackets on "Guest-WiFi-Shaping" during a busy evening confirms the shaping rule is actively holding back guest traffic to enforce its bandwidth cap.