Seeing the exact same issue nowHere you go:
Code:|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 95 | 95 | 0 | 0 | 3 | 2 | | 165-73-101-65.ip.afrihost.co.za - 0 | 95 | 95 | 0 | 0 | 4 | 1 | | 169-1-21-1.ip.afrihost.co.za - 2 | 91 | 90 | 0 | 1 | 4 | 1 | | 196.25.26.65 - 2 | 91 | 90 | 1 | 2 | 56 | 1 | | 10.189.30.2 - 2 | 91 | 90 | 159 | 159 | 165 | 159 | |ge-0-1-0-68.peering1.the.lon1.coreix.net - 2 | 91 | 90 | 146 | 146 | 149 | 146 | | xe-5-1.edge4.enf.lon5.coreix.net - 2 | 91 | 90 | 159 | 160 | 178 | 160 | | 85.13.221.178.reverse.coreix.net - 0 | 95 | 95 | 146 | 146 | 148 | 147 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
This isn't as bad as it sometimes gets - it will also shoot to 15% PL before coming back down.
Beforehand, when my WAN address was 102.x.x.x it was taking the exact same path out to the net and there wasn't any issue at all with the beloved 169.1.21.1 hop.


