Cool Ideas not so Cool anymore

[CrypticZA]

24.105.62.129 is the one I initially grabbed from the Blizz support forums and stuck with to try keep some consistency in testing. A large challenge was finding a friend with a similar setup(Vuma/CISP/NorthJHB/IPPool) to compare and present tests. The closest I got was a mate using MTR to that IP.
I found one, his IP assigned in the 102.132.139.x pool, mine has remained the same in the 102.132.136.x pool. Vuma/CISP/5km's of each other. The below two MTR's done within an hour of each other, and frustratingly weird and different indicators.

View attachment 865117
View attachment 865121

Second image the average to the router is 18ms... Plus that second MTR is very messy drop 18ms to get the router 249-18 is 231. Going to take a wild guess and say it was done on WiFi and not great WiFi signal

 

[EvilSurd]

Nope, no wifi used in the majority of the tests, excepting when I performed the tests on a MacBook, MacOS, MacWoW to eliminate application as a root.
Screenie from that time when I still had name res on, before we started using the Blizz LookingGlass tool and plugging direct into CPE

 

[TheMightyQuin]

It's almost like this guy knows the origin story of the likes of AH, Openweb, CISP.
Just because the trolls like to be fed.

View attachment 865093
Good work on the dirty dangle upvotes boys, way to snipe mad emoji celly boys, boost ranks ferda boys boys.
Forget where I mentioned frags or blaming lag

At least you didn't have too much packetloss when ripping Letterkenny....

If this epic pi$$ and moan session isn't about lag, WTF are you complaining about?

 

[DeatheCore]

24.105.62.129 is the one I initially grabbed from the Blizz support forums and stuck with to try keep some consistency in testing. A large challenge was finding a friend with a similar setup(Vuma/CISP/NorthJHB/IPPool) to compare and present tests. The closest I got was a mate using MTR to that IP.
I found one, his IP assigned in the 102.132.139.x pool, mine has remained the same in the 102.132.136.x pool. Vuma/CISP/5km's of each other. The below two MTR's done within an hour of each other, and frustratingly weird and different indicators.

View attachment 865117
View attachment 865121

That MTR of yours does not look kosher, 18ms average to your router via cable? 4% packet loss to Blizzard which looks to be originating between your router and the Vuma gateway. I know they have limited icmp in some cases, but not to that extent imo. This is less about optimal routes and more about loss on your line it seems.

 

[EvilSurd]

That MTR of yours does not look kosher, 18ms average to your router via cable? 4% packet loss to Blizzard which looks to be originating between your router and the Vuma gateway. I know they have limited icmp in some cases, but not to that extent imo. This is less about optimal routes and more about loss on your line it seems.

I'm not on that SACS route anymore and only have that one screenie of an MTR. When I plugged direct into CPE we switched to comparing using the LookingGlass tool.

When I was plugged into the CPE direct, I had the same in game experience as default setup, and when switched to the London route, I had the same new experience when direct to CPE or via router.
Unfortunately it's hard to control the tests when unable to easily switch through the testing variable, but up until then I tried to keep it as standardised as possible.
As Example, before even making noise, or while doing it, I have the ability to provide 1x PC, Win10, 2 diff LAN ports, 1xLaptop, Win10, LAN to router, wifi to rouuter, LAN to CPE, 1x MacBook, wifi only, MacOS and Mac version of WoW.

I figure for the most part if I get similar experience with that variety of hardware, software OS, software App and networking, it goes a big way to excluding variable on my end.
That being said though, crazy **** still happens