Web Squad ISP

Status
Not open for further replies.
What happened to the WS Speedtest.net server in JHB?

We attached two other speedtest daemons (Ubiquity and nperf) to this host as well as enabled IPv6 and something caused the Ookla Daemon to hang. Reset that and it’s back up. Will take a few hours for Ookla to clear the server and load it back up.
 
Hi guys, is there a possible routing issue to EU tonight? Getting 220ms ping to the EU PUBG servers all of a sudden, always get 170 - 180ms. My friends on Cool Ideas are still getting 180 in the same matches as me so it can't be PUBG.
 
@Zodiak Not sure if related, but I've been having similar the past month to the US. Using WinMTR it always seems to be at 41.78.188.* that the packets get lost and the connection gets laggy. Also with Websquad.
 
@Zodiak Not sure if related, but I've been having similar the past month to the US. Using WinMTR it always seems to be at 41.78.188.* that the packets get lost and the connection gets laggy. Also with Websquad.
Can you give me an MTR or a source and destination address?
 
Hi guys, is there a possible routing issue to EU tonight? Getting 220ms ping to the EU PUBG servers all of a sudden, always get 170 - 180ms. My friends on Cool Ideas are still getting 180 in the same matches as me so it can't be PUBG.

Seeing elevated latency to EU tonight. AWS transits traffic to SA on their own network and we have direct connects in CPT and JHB in addition to peering. Very hard to drain AWS locally because most transit providers use peering on local exchanges too. Will continue monitoring. Probably just a blip on the AWS network this evening.
 
Seeing elevated latency to EU tonight. AWS transits traffic to SA on their own network and we have direct connects in CPT and JHB in addition to peering. Very hard to drain AWS locally because most transit providers use peering on local exchanges too. Will continue monitoring. Probably just a blip on the AWS network this evening.

Unfortunately the issues are persisting today as well with the ping, still on 212+ ms ping in PUBG
 
Unfortunately the issues are persisting today as well with the ping, still on 212+ ms ping in PUBG
Our latency (ping) monitors on Amazon Web Services (AWS) are showing levels are back to normal with results in the <165ms region. https://pubgserverping.com also confirms this. As I mentioned yesterday, AWS transits ALL their own data to South Africa, so unless you're able to drain that out closer to source, say at a POP in the EU, then you can't really affect their transit. I've checked forward traces from all 3 SA regions and reverse traces from 2 EU regions (Ireland and London) and all are flowing correctly via AWS transit.

If you have a server IP for the affected server(s) and an MTR that would help if the issue persists.
 
I'm getting the following to London and Ireland, I don't think this is normal on pubgserverping.com

713465
 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.100.1 - 0 | 78 | 78 | 0 | 0 | 3 | 0 |
| core.as-02.jb1.za.ws.net.za - 0 | 78 | 78 | 2 | 21 | 29 | 24 |
| core.cr-xe-01.jb1.za.ws.net.za - 0 | 78 | 78 | 2 | 4 | 26 | 3 |
| core.pe-xe-ix01.jb1.za.ws.net.za - 0 | 78 | 78 | 2 | 3 | 7 | 3 |
| 196-60-9-105.ixp.joburg - 0 | 78 | 78 | 2 | 4 | 23 | 3 |
| 52.93.56.88 - 0 | 78 | 78 | 3 | 8 | 127 | 4 |
| 52.93.56.101 - 0 | 78 | 78 | 2 | 4 | 49 | 3 |
| 54.239.46.76 - 0 | 78 | 78 | 162 | 170 | 249 | 167 |
| 54.239.46.85 - 0 | 78 | 78 | 162 | 168 | 248 | 164 |
| 54.239.101.40 - 0 | 78 | 78 | 163 | 168 | 243 | 164 |
| 52.94.33.149 - 0 | 78 | 78 | 161 | 166 | 265 | 163 |
| 52.94.33.76 - 0 | 78 | 78 | 162 | 166 | 211 | 166 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| 52.94.56.52 - 0 | 77 | 77 | 163 | 167 | 196 | 166 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )
 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.100.1 - 0 | 78 | 78 | 0 | 0 | 3 | 0 |
| core.as-02.jb1.za.ws.net.za - 0 | 78 | 78 | 2 | 21 | 29 | 24 |
| core.cr-xe-01.jb1.za.ws.net.za - 0 | 78 | 78 | 2 | 4 | 26 | 3 |
| core.pe-xe-ix01.jb1.za.ws.net.za - 0 | 78 | 78 | 2 | 3 | 7 | 3 |
| 196-60-9-105.ixp.joburg - 0 | 78 | 78 | 2 | 4 | 23 | 3 |
| 52.93.56.88 - 0 | 78 | 78 | 3 | 8 | 127 | 4 |
| 52.93.56.101 - 0 | 78 | 78 | 2 | 4 | 49 | 3 |
| 54.239.46.76 - 0 | 78 | 78 | 162 | 170 | 249 | 167 |
| 54.239.46.85 - 0 | 78 | 78 | 162 | 168 | 248 | 164 |
| 54.239.101.40 - 0 | 78 | 78 | 163 | 168 | 243 | 164 |
| 52.94.33.149 - 0 | 78 | 78 | 161 | 166 | 265 | 163 |
| 52.94.33.76 - 0 | 78 | 78 | 162 | 166 | 211 | 166 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 78 | 0 | 0 | 0 | 0 | 0 |
| 52.94.56.52 - 0 | 77 | 77 | 163 | 167 | 196 | 166 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )
Looks to me like there are large spikes on the AWS network at 52.93.56.88 - 54.239.46.76 (remember, this could be because the devices don't respond to ICMP or de-prioritise ICMP).. so this could mean nothing.

What we're seeing is on the last hop, an average latency of 167 (which is good) and a peak of 196, and on my test, 238 - which points to an AWS issue.

Like I said to you, we hand over to AWS at the 5th hop here, and they hand back to us at the exact same location.

Their NOC are extremely slow to respond to any tickets (if they do at all), though I have sent them a ticket with our MTR results.
 
@Zodiak I know AWS' SA terrestrial routes have given issues before (JHB-CPT). I have drained AWS out of JHB now, so we are only visible to them and them to us in Cape Town (using our own terrestrial route between JHB and CPT). Let me know if you see any improvement? (Just want to eliminate their JHB handover being the issue).
 
@Zodiak I know AWS' SA terrestrial routes have given issues before (JHB-CPT). I have drained AWS out of JHB now, so we are only visible to them and them to us in Cape Town (using our own terrestrial route between JHB and CPT). Let me know if you see any improvement? (Just want to eliminate their JHB handover being the issue).

Thank you, tested now after restarting the router and the ping is still 215ms in game.... Weirdly I checked Resource Manager to see which AWS servers PUBG is connecting to and looking at the below it appears to be AP (Asia Pacific I believe) instead of EU, probably because EU ping is too high but I'm not sure:

713485
 
Guys, I just tried Battlefield V and I am getting closest servers listed as Malaysia at 236ms ping and no London servers showing up, this tells me that I am on some new link/routing that is bypassing EU, specifically London side. There must have been some change
 
Apex Legends also connects me to Singapore as the closest server?! Something is fundamentally wrong if it thinks that Singapore is 140ms ping when it should be more like 368ms. Something is definitely not right.

713499
 
Extreme buffering with Real Debrid. Nuff said.

When will this be resolved?

I have to agree.... Every weekend there seems to be some sort of internet problem lately, not sure what is going on but getting quite tired of this also
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X