Web Squad ISP

Status
Not open for further replies.
You can try exit points local to the area you're connecting. Blizzard is notorious for issues on Cogent so you hop to New York to bypass as an example
 
You can try exit points local to the area you're connecting. Blizzard is notorious for issues on Cogent so you hop to New York to bypass as an example
Just tried a local match in Johannesburg and also getting severe packet bursts, I honestly don't know what to do anymore.... it's basically unplayable
 
WinMTR to the Johannesburg server:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.10.1 - 0 | 275 | 275 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| 160.119.224.102 - 0 | 275 | 275 | 2 | 8 | 140 | 3 |
| 160.119.224.133 - 1 | 271 | 270 | 1 | 1 | 2 | 1 |
| core.pe-ge-inx.jnb.za.ws.net.za - 1 | 271 | 270 | 2 | 2 | 4 | 2 |
| optinet-2.jinx.net.za - 0 | 275 | 275 | 2 | 4 | 370 | 3 |
| 197-80-7-79.jhb.mweb.co.za - 2 | 263 | 260 | 6 | 11 | 376 | 10 |
| bu-ether3.mca-pe-1.optinet.net - 2 | 259 | 255 | 4 | 11 | 377 | 11 |
| 197-80-96-14.jhb.mweb.co.za - 1 | 267 | 265 | 3 | 3 | 6 | 3 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Well now getting packet bursts even with ExitLag, I guess it depends on the server but found a German COD server through Exit Lag and the IP address. Did a WinMTR to that IP and it is not pretty:

View attachment 1524009

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.10.1 - 0 | 231 | 231 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| 160.119.224.102 - 0 | 231 | 231 | 3 | 5 | 70 | 6 |
| 160.119.224.133 - 0 | 232 | 232 | 1 | 1 | 4 | 2 |
| core.pe-xe-ix01.jb1.za.ws.net.za - 1 | 224 | 222 | 1 | 1 | 18 | 2 |
| 197-159-37-201-c9.Hymax.CPT.eoh-ns.net - 1 | 228 | 227 | 2 | 2 | 14 | 2 |
|core.100g-1-0-0-gp-id-ter-scp-2.za.africainx.net - 0 | 231 | 231 | 2 | 4 | 17 | 3 |
| 80.84.20.30 - 45 | 83 | 46 | 2 | 2 | 3 | 2 |
| 10.246.114.149 - 94 | 48 | 3 | 0 | 176 | 176 | 176 |
| te7-5.br03.ldn01.pccwbtn.net - 3 | 208 | 202 | 169 | 169 | 185 | 169 |
| hu0-0-0-2.br03.frf05.pccwbtn.net - 1 | 227 | 226 | 185 | 185 | 202 | 185 |
| hu0-0-0-2.br03.frf05.pccwbtn.net - 1 | 227 | 226 | 185 | 185 | 202 | 185 |
| 63-218-231-106.static.pccwglobal.net - 0 | 231 | 231 | 253 | 257 | 292 | 254 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Both these MTRs show no PL through the traces - look at hop 13 with 0% loss on both traces. Just a reminder here; PL needs to carry through from a hop to the end to begin to point to a possible issue. Anything in between is just ICMP rate limiting or no ICMP response and is perfectly normal, and will not result in any issues... It sounds more like you are getting some fragmentation issues from broken packets or packet rebuilds/retransmits which translate into PL in game - which is why maybe something like exitlag has less perceived loss (smaller packets, less likely to be fragmented). Based on the above, FNO isn't dropping packets (not to say we don't have a MTU issue). First port of call is to eliminate potential router bottlenecks (dropping packets, CPU bottlenecks etc). Based on the isolated nature, and Exitlag not fixing the issue, it's less likely routing and more likely something isolated (MTU or hardware). We hand over to Exitlag locally and on different hardware to our own transit paths.
 
Both these MTRs show no PL through the traces - look at hop 13 with 0% loss on both traces. Just a reminder here; PL needs to carry through from a hop to the end to begin to point to a possible issue. Anything in between is just ICMP rate limiting or no ICMP response and is perfectly normal, and will not result in any issues... It sounds more like you are getting some fragmentation issues from broken packets or packet rebuilds/retransmits which translate into PL in game - which is why maybe something like exitlag has less perceived loss (smaller packets, less likely to be fragmented). Based on the above, FNO isn't dropping packets (not to say we don't have a MTU issue). First port of call is to eliminate potential router bottlenecks (dropping packets, CPU bottlenecks etc). Based on the isolated nature, and Exitlag not fixing the issue, it's less likely routing and more likely something isolated (MTU or hardware). We hand over to Exitlag locally and on different hardware to our own transit paths.
So what can we try then? Because nobody else is having this issues (my friends for example with other ISPs) and I don't seem to have issue with other games etc.
 
WinMTR to the Johannesburg server:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.10.1 - 0 | 275 | 275 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| 160.119.224.102 - 0 | 275 | 275 | 2 | 8 | 140 | 3 |
| 160.119.224.133 - 1 | 271 | 270 | 1 | 1 | 2 | 1 |
| core.pe-ge-inx.jnb.za.ws.net.za - 1 | 271 | 270 | 2 | 2 | 4 | 2 |
| optinet-2.jinx.net.za - 0 | 275 | 275 | 2 | 4 | 370 | 3 |
| 197-80-7-79.jhb.mweb.co.za - 2 | 263 | 260 | 6 | 11 | 376 | 10 |
| bu-ether3.mca-pe-1.optinet.net - 2 | 259 | 255 | 4 | 11 | 377 | 11 |
| 197-80-96-14.jhb.mweb.co.za - 1 | 267 | 265 | 3 | 3 | 6 | 3 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Code:
|                   optinet-2.jinx.net.za -    0 |  275 |  275 |    2 |    4 |  370 |    3 |
Can you share the server IP so we can trace this side too? Reaching MWEB here with 0% loss... and some losses present past this point. However, not able to see endpoint, so this could be rate limiting. I see we're routing forward via JINX, would be interesting to see reverse path
 
Which games specifically?
The issue is specifically Call of Duty Modern Warfare II, was perfectly find until about 4 days ago, and then I am literally having packet bursts every 20 seconds on every server, local, international etc.

The IP address for the local Jhb server is: 197.80.200.88 I believe
The IP address for an EU server in Frankfurt is 45.32.152.91
 
Just tried a local match in Johannesburg and also getting severe packet bursts, I honestly don't know what to do anymore.... it's basically unplayable
Joburg? Odd,and you're sure it's network?
Reason I ask is Apex for instance has an issue with Geforce experience that randomly just jitters the performance to hell,had to uninstall it to even play. It "felt" like Lag

Wanna try on my surfshark account using Joburg node?
 
Joburg? Odd,and you're sure it's network?
Reason I ask is Apex for instance has an issue with Geforce experience that randomly just jitters the performance to hell,had to uninstall it to even play. It "felt" like Lag

Wanna try on my surfshark account using Joburg node?
Would be awesome to try, if you don't mind, thanks a mill.

So the reason I don't think it is graphical jitters/stutters because on top the packet loss/packet burst warning pops up in game, so I would imagine it is network related
 
The issue is specifically Call of Duty Modern Warfare II, was perfectly find until about 4 days ago, and then I am literally having packet bursts every 20 seconds on every server, local, international etc.

The IP address for the local Jhb server is: 197.80.200.88 I believe
The IP address for an EU server in Frankfurt is 45.32.152.91
Thanks, let me see if we can try route around JINX for an A/B test. I've asked the team to drain JINX; please test again in the next 5-10 mins. Will keep digging on this side. Let's see if JINX change / surfshark helps and then troubleshoot from there. Not that there's anything wrong with JINX (we currently see about 15-25% of our traffic carrying over this point without issues and we are big fans of JINX's JHB fabric) but this would assist with narrowing down potential bottlenecks upstream. Draining this one point just moves traffic to other points and helps speed up the diagnostic process.

Update: JINX is drained
 
Thanks, let me see if we can try route around JINX for an A/B test. I've asked the team to drain JINX; please test again in the next 5-10 mins. Will keep digging on this side. Let's see if JINX change / surfshark helps and then troubleshoot from there

Update: JINX is drained
Great let me try and give it a go
 
Would be awesome to try, if you don't mind, thanks a mill.

So the reason I don't think it is graphical jitters/stutters because on top the packet loss/packet burst warning pops up in game, so I would imagine it is network related
Yeah Apex would also pop up the Icons,but it was bullshit,it was just guessing :laugh:
 
Ok so some good news it seems, not sure what did it (I reinstalled my GPU drivers with DDU without Geforce Experience) or if it was the changes that you guys made/flush but had 2 matches now without any packet bursts! Will keep monitoring but if it was Geforce Experience I have literally seen everything then lol
 
Ok so something new and interesting is happening, Speedtest to any server in London is between 300 - 370ms ping and terrible download speed, the rest of EU is fine though and US is fine.....

 
I'm in CPT, not seeing anything to that effect:

14735728557.png


Tested to Vodafone UK

I'm seeing pings in Apex to EU servers are generally higher these days.
Mine regularly sits around 210 - 250 ms, while friends are around 170 to 200 ms...
 
Ok so something new and interesting is happening, Speedtest to any server in London is between 300 - 370ms ping and terrible download speed, the rest of EU is fine though and US is fine.....

Make sure you using a server where WS peers in London

1684089046649.png
^ This goes via Vox telecom from CT

1684089118986.png
^ This CISP carry to UK
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X