Web Squad ISP

Status
Not open for further replies.
Hi Web Squad, can I please ask, lately I've been getting 180+ ms ping to London/EU where before it was always around 167 from Joburg. Has something fundamentally changed with the routing of late?
 
Zodiak said:
Hi Web Squad, can I please ask, lately I've been getting 180+ ms ping to London/EU where before it was always around 167 from Joburg. Has something fundamentally changed with the routing of late?
Click to expand...
noticed the same on the majority of the EU rust servers i play on
 
Zodiak said:
Hi Web Squad, can I please ask, lately I've been getting 180+ ms ping to London/EU where before it was always around 167 from Joburg. Has something fundamentally changed with the routing of late?
Click to expand...
ijacobs3 said:
noticed the same on the majority of the EU rust servers i play on
Click to expand...
If you can drop me a traceroute/MTR to a server, I'll be happy to take a look from this side and see what we can do
 
... just wanna say thanks, had my line drop on Thursday afternoon 16:00'ish... one second it worked, the next not so much, noticed my ONT shown a red led on alarm... rebooted the ONT, rebooted my Router (pfSense), eventually opened a ticket with Websquad support, they opened a back to back with MFN, got called at 09:00 Friday morning, by 11:00 fixed... seems my pigtail on the incoming fiber going into the TP was not properly fitted originally and it came off.
MFN have also phoned twice to confirm all good and I'm happy. well done guys.
G
 
@websquadza recently got back into playing Valorant, and I'm feeling the hit on the routing change that you mentioned a while ago. London - the server that I used to play on - has gone from 144ms to 166ms, with Paris now being my best bet with 158ms. It's only a 14ms increase, but for some reason it's perceivably much laggier feeling than when I played on London servers. Wondering if there's any way I could possibly get the old latency to London?
 
JustAnotherSouthAfrican said:
@websquadza recently got back into playing Valorant, and I'm feeling the hit on the routing change that you mentioned a while ago. London - the server that I used to play on - has gone from 144ms to 166ms, with Paris now being my best bet with 158ms. It's only a 14ms increase, but for some reason it's perceivably much laggier feeling than when I played on London servers. Wondering if there's any way I could possibly get the old latency to London?
Click to expand...
Get the IP or server name to WebsquadZA, run a tracert to the IP send that info to WS
 
JustAnotherSouthAfrican said:
@websquadza recently got back into playing Valorant, and I'm feeling the hit on the routing change that you mentioned a while ago. London - the server that I used to play on - has gone from 144ms to 166ms, with Paris now being my best bet with 158ms. It's only a 14ms increase, but for some reason it's perceivably much laggier feeling than when I played on London servers. Wondering if there's any way I could possibly get the old latency to London?
Click to expand...
Happy to take a look at this. If you can get me an IP, I'll see how we're reaching it and see what we can do to optimise paths
 
websquadza said:
Following up on an IP here?
Click to expand...
Hi, sorry I'm not too technical when it comes to Tracerout and MTR, please can you let me know the command prompts to use and I will share the results. I can for sure say that my game pings are 180 - 190 to London and Ireland when they used to be 160 previously, so I am definitly seeing an ongoing change.
 
Here is an example from the Tarkov server selector with Pings, best ping to EU is 188ms for Ireland (their ping cap is at 190ms so it kicks me out of the raid when it goes over) and London is 236ms:

1658413511784.png
 
Code: 
|------------------------------------------------------------------------------------------|
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              10.10.10.1 -    0 |   32 |   32 |    0 |    0 |    0 |    0 |
|        as-vuma.cp-gwf-4-01.za.ws.net.za -    0 |   32 |   32 |    2 |   14 |   78 |   12 |
|             core.as-01.cp1.za.ws.net.za -    0 |   32 |   32 |    0 |    0 |    1 |    1 |
|        core.pe-xe-ip01.cp1.za.ws.net.za -    0 |   32 |   32 |    1 |    1 |    1 |    1 |
|                          102.220.216.18 -    0 |   32 |   32 |  148 |  148 |  149 |  148 |
|            riotgames-2.par.franceix.net -    0 |   32 |   32 |  148 |  148 |  153 |  148 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
 
Hi, finally found the Tarkov London IP address and Googled how to do a TraceRT, below is the result, as you can see 245ms not really great to London:

Tracing route to unn-185-59-221-36.datapacket.com [185.59.221.36]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TUF-AX5400-0388 [192.168.50.1]
2 2 ms 2 ms 2 ms core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
3 4 ms 3 ms 3 ms 100.99.198.1
4 3 ms 3 ms 3 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
5 6 ms 5 ms 4 ms gi0-0-1-0.agr11.jnb01.atlas.cogentco.com [206.249.0.201]
6 5 ms 3 ms 3 ms be2355.ccr51.jnb01.atlas.cogentco.com [154.54.43.37]
7 179 ms 178 ms 178 ms be2389.ccr22.lon01.atlas.cogentco.com [154.54.80.201]
8 197 ms 198 ms 197 ms be2869.ccr42.lon13.atlas.cogentco.com [154.54.57.161]
9 178 ms 178 ms 179 ms be2573.ccr21.lon02.atlas.cogentco.com [154.54.62.6]
10 247 ms 247 ms 246 ms datacamp.demarc.cogentco.com [149.6.149.234]
11 244 ms 250 ms 245 ms vl203.lon-cyx2-dist-2.cdn77.com [138.199.0.77]
12 244 ms 244 ms 245 ms unn-185-59-221-36.datapacket.com [185.59.221.36]
 
Zodiak said:
Hi, finally found the Tarkov London IP address and Googled how to do a TraceRT, below is the result, as you can see 245ms not really great to London:

Tracing route to unn-185-59-221-36.datapacket.com [185.59.221.36]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TUF-AX5400-0388 [192.168.50.1]
2 2 ms 2 ms 2 ms core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
3 4 ms 3 ms 3 ms 100.99.198.1
4 3 ms 3 ms 3 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
5 6 ms 5 ms 4 ms gi0-0-1-0.agr11.jnb01.atlas.cogentco.com [206.249.0.201]
6 5 ms 3 ms 3 ms be2355.ccr51.jnb01.atlas.cogentco.com [154.54.43.37]
7 179 ms 178 ms 178 ms be2389.ccr22.lon01.atlas.cogentco.com [154.54.80.201]
8 197 ms 198 ms 197 ms be2869.ccr42.lon13.atlas.cogentco.com [154.54.57.161]
9 178 ms 178 ms 179 ms be2573.ccr21.lon02.atlas.cogentco.com [154.54.62.6]
10 247 ms 247 ms 246 ms datacamp.demarc.cogentco.com [149.6.149.234]
11 244 ms 250 ms 245 ms vl203.lon-cyx2-dist-2.cdn77.com [138.199.0.77]
12 244 ms 244 ms 245 ms unn-185-59-221-36.datapacket.com [185.59.221.36]
Click to expand...

Thanks for this, from what I can see, the latency here is on the server host's side (look at hop 10 - traffic goes from our upstream to datacamp's peering router and adds 70 odd ms).

I've asked our network team to see if they can get a reverse trace, so we can see why that latency is induced (as these servers are in London). Will see what they pick up and try get this resolved ASAP

JustAnotherSouthAfrican said:
Here's the IP to the London server: 162.249.72.1
Thank you!
Click to expand...

This looks like it's favouring the Paris path, which adds about 10ms each way, so will see if we can steer away from this. I've sent this to our network team.
 
websquadza said:
Thanks for this, from what I can see, the latency here is on the server host's side (look at hop 10 - traffic goes from our upstream to datacamp's peering router and adds 70 odd ms).

I've asked our network team to see if they can get a reverse trace, so we can see why that latency is induced (as these servers are in London). Will see what they pick up and try get this resolved ASAP



This looks like it's favouring the Paris path, which adds about 10ms each way, so will see if we can steer away from this. I've sent this to our network team.
Click to expand...

Thanks guys
 
Here is one to Tarkov German servers as well if it helps:

Tracing route to 146.0.254.136 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms TUF-AX5400-0388 [192.168.50.1]
2 3 ms 3 ms 2 ms core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
3 5 ms 3 ms 3 ms 100.99.198.1
4 32 ms 5 ms 3 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
5 5 ms 5 ms 3 ms gi0-0-1-0.agr11.jnb01.atlas.cogentco.com [206.249.0.201]
6 6 ms 9 ms 14 ms be2355.ccr51.jnb01.atlas.cogentco.com [154.54.43.37]
7 177 ms 178 ms 178 ms be2485.ccr21.lon01.atlas.cogentco.com [154.54.88.205]
8 160 ms 159 ms 160 ms ldn-b3-link.ip.twelve99.net [62.115.9.28]
9 * 172 ms * ldn-bb4-link.ip.twelve99.net [62.115.122.180]
10 185 ms 185 ms 185 ms prs-bb2-link.ip.twelve99.net [62.115.133.239]
11 176 ms 179 ms 175 ms ffm-bb2-link.ip.twelve99.net [62.115.114.99]
12 194 ms 193 ms 195 ms ffm-b1-link.ip.twelve99.net [62.115.121.7]
13 175 ms 174 ms 199 ms ae5.cr-antares.fra10.bb.godaddy.com [62.115.152.95]
14 175 ms 174 ms 175 ms ae0.fra7-pe-bellatrix.bb.gdinf.net [87.230.115.31]
15 193 ms 194 ms 194 ms ae0.fra7.sr-left.dcn.gdinf.net [87.230.115.27]
16 196 ms 194 ms 193 ms et-51.ds1-left.aog207.frankfurt.de.velia.net [85.195.111.57]
17 et-51.ds1-left.aog207.frankfurt.de.velia.net [85.195.111.57] reports: Destination host unreachable.
 
I've also noticed now that my Hong Kong option at 150ms ping is now gone entirely from the server selector, which means I can't play EU or ASIA servers now at all. Most of my friends can play EU no problem from Johannesburg with other ISPs in the 160 - 170s.
 
Zodiak said:
I've also noticed now that my Hong Kong option at 150ms ping is now gone entirely from the server selector, which means I can't play EU or ASIA servers now at all. Most of my friends can play EU no problem from Johannesburg with other ISPs in the 160 - 170s.
Click to expand...
So it looks like Tarkov uses Datapacket (CDN77) to host their London servers, a reverse trace from these servers shows the following:
Code: 
HOST: 10g-lon-kvm-1-185-59-221-51 Loss%   Snt   Last   Avg  Best  Wrst StDev

  1. AS60068  185.59.221.61        0.0%    10    0.1   0.3   0.1   2.4   0.7

  2. AS???    138.199.0.76         0.0%    10    0.3   0.2   0.1   0.3   0.0

  3. AS201011 81.95.2.141          0.0%    10    0.7   1.0   0.3   4.7   1.2

  4. AS201011 5.56.18.94           0.0%    10   68.8  68.8  68.6  69.4   0.0

  5. AS???    198.32.160.243       0.0%    10  198.8 198.9 198.8 198.9   0.0

  6. AS37497  197.148.71.81        0.0%    10  215.5 215.4 215.4 215.6   0.0

  7. AS174    206.249.0.202        0.0%    10  237.5 233.9 233.4 237.5   1.2

  8. AS328137 160.119.224.21       0.0%    10  214.9 215.0 214.9 215.6   0.0

  9. AS328137 160.119.230.1       10.0%    10  234.2 235.1 233.6 239.7   2.0

The 4th hop (AS201011) seems to be an issue here, adding +- 70ms. I've seen on other threads this is a common issue across transit paths. We have mailed CDN77 to look into this route, as we have other, shorter paths they can reach us at.

Zodiak said:
I've also noticed now that my Hong Kong option at 150ms ping is now gone entirely from the server selector, which means I can't play EU or ASIA servers now at all. Most of my friends can play EU no problem from Johannesburg with other ISPs in the 160 - 170s.
Click to expand...

This will generally be because of server host selection. If the host doesn't peer with PCCW or at Singapore IX, then the path will be longer, even though we have shorter paths. I know one of the hosts uses HE, who only have the long path from Singapore to SA.

Will update you on the CDN77 issue ASAP
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X