South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Downdetector does seem a bit higher than the norm too
View attachment 1523021
Please test nowCan this be related to my issue as well
1462 does seem a bit on the low side but it workable. Sometimes on the mobile networks the MTU drop well below 1400.Set to 1462,everything's happy now
Cheers @r00igev@@r
Any chance you can get me an MTR?Severe packet loss/packet burst since last night, Vuma Randpark, anyone else having issues? Especially for gaming
You can switch back; LNS has a large packet overhead, so Openserve run Jumbo frame to allow for this. However, for some reason, the port had been set back to 1500 bytes. All sorted now.Set to 1462,everything's happy now
Cheers @r00igev@@r
Confirmed this has recovered,may hours and grey hairs trying to work out what I broke laterYou can switch back; LNS has a large packet overhead, so Openserve run Jumbo frame to allow for this. However, for some reason, the port had been set back to 1500 bytes. All sorted now.
Any chance you can get some ping plotter or mtrs. Sounds like you're seeing PL on your line again.3 days now major packet loss/packet burst specifically in COD Modern Warfare 2 when playing EU and international servers. Basically rubber banding all the time
Sure, screen shot below, getting severe packet loss even on local matches, really really bad:
View attachment 1523553
No losses on either of these (last hop is 0%)- hop 2 is just not responding to ping; this is normal. It's only loss if it's visible on the last hop. However, second screen is showing some jitter (those grey areas).Here is Ping Plotter to Google.com, seems on both examples, 2nd hop is at 100% packet loss?
View attachment 1523559
Loss here, but 4 samples is too little.PING google.com (172.217.170.46): 56 data bytes
64 bytes from 172.217.170.46: seq=0 ttl=59 time=4.393 ms
64 bytes from 172.217.170.46: seq=1 ttl=59 time=4.460 ms
64 bytes from 172.217.170.46: seq=2 ttl=59 time=4.356 ms
--- google.com ping statistics ---
4 packets transmitted, 3 packets received, 25% packet loss
round-trip min/avg/max = 4.356/4.403/4.460 ms
That's generally the issue yes,a particular upstream provider in the chain has an issueBtw interesting development, I used ExitLag now and 0 packet loss or packet burst, which means if running through a gaming VPN the issue is resolved. Would I be guessing correctly then that is a pathing issue?
