Web Squad ISP

Status
Not open for further replies.
websquadza said:
If you can get me some more IPs to look at.
Click to expand...

London latency dropped to 150ms now. This is now the lowest with Paris sitting at 155ms.

London server IP: 162.249.72.1

A list of all the IP's that the Valorant client connected to:
Code: 
99.83.175.244
162.249.72.1
172.64.151.88
104.18.36.168
162.247.241.1
104.16.55.40
104.16.56.40
22a:f026:e0:a503::a01b
75.2.116.77
99.83.189.58
75.2.31.169
75.2.105.73
99.83.199.240
43.229.65.1
197.80.130.128
22a:f026:e0:8003::a01b
26:1614:a0:8a01::a01b
197.80.130.64
23.54.159.145
 
I much appreciate the help with the latency changes for Valorant, @websquadza. Thank you so much. I'm enjoying the drop to 150ms to London.

Just asking because I have no idea, but why can I get 144ms to some speedtest.net servers in London, while majority of the others are at 150ms, along with Valorant London Region?

Edited for stats:

Valorant London:
Code: 
as-vuma.cp-gwf-4-01.za.ws.net.za (160.119.236.65)  13.598 ms  21.799 ms  4.891 ms
core.as-01.cp1.za.ws.net.za (160.119.233.161)  0.992 ms  1.028 ms  0.834 ms
core.pe-xe-ip01.cp1.za.ws.net.za (160.119.232.19)  1.147 ms  1.170 ms  1.148 ms
249-68-148-197.as37497.za.net (197.148.68.249)  1.303 ms  1.306 ms  1.152 ms
54-71-148-197.as37497.za.net (197.148.71.54)  141.285 ms  141.273 ms  141.406 ms
197.148.66.41 (197.148.66.41)  141.338 ms  141.362 ms  141.370 ms
linx-j.riotdirect.net (195.66.226.186)  150.622 ms  148.619 ms  148.456 ms

Speedtest local - Vodacom:
13456733931.png


Low latency examples:
EOH Network Solutions
13456730161.png


Vodafone UK
13456750445.png


Higher latency examples:
Coreix Ltd
13456726009.png


31173 Services AB
13456743643.png
 
Last edited:
JustAnotherSouthAfrican said:
I much appreciate the help with the latency changes for Valorant, @websquadza. Thank you so much. I'm enjoying the drop to 150ms to London.

Just asking because I have no idea, but why can I get 144ms to some speedtest.net servers in London, while majority of the others are at 150ms, along with Valorant London Region?

Edited for stats:

Valorant London:
Code: 
as-vuma.cp-gwf-4-01.za.ws.net.za (160.119.236.65)  13.598 ms  21.799 ms  4.891 ms
core.as-01.cp1.za.ws.net.za (160.119.233.161)  0.992 ms  1.028 ms  0.834 ms
core.pe-xe-ip01.cp1.za.ws.net.za (160.119.232.19)  1.147 ms  1.170 ms  1.148 ms
249-68-148-197.as37497.za.net (197.148.68.249)  1.303 ms  1.306 ms  1.152 ms
54-71-148-197.as37497.za.net (197.148.71.54)  141.285 ms  141.273 ms  141.406 ms
197.148.66.41 (197.148.66.41)  141.338 ms  141.362 ms  141.370 ms
linx-j.riotdirect.net (195.66.226.186)  150.622 ms  148.619 ms  148.456 ms

Speedtest local - Vodacom:
13456733931.png


Low latency examples:
EOH Network Solutions
13456730161.png


Vodafone UK
13456750445.png


Higher latency examples:
Coreix Ltd
13456726009.png


31173 Services AB
13456743643.png
Click to expand...
Thank you, appreciate the feedback

Don’t worry, we’re still working on some optimisation. Our AS path out of paris is shorter than London, which means some traffic is going via Paris to SA. We’re still adjusting this a little to maximise the value of being in both locations. Will use the above to assist
 
websquadza said:
Thank you, appreciate the feedback

Don’t worry, we’re still working on some optimisation. Our AS path out of paris is shorter than London, which means some traffic is going via Paris to SA. We’re still adjusting this a little to maximise the value of being in both locations. Will use the above to assist
Click to expand...

Thank you, I am still sitting with over 200ms ping to any EU destination in Tarkov, anyway you guys could help and optimize for me? Thanks a mill. All my friends are able to play Tarkov abroad and I am affected by the 190ms ping lock.
 
Zodiak said:
Thank you, I am still sitting with over 200ms ping to any EU destination in Tarkov, anyway you guys could help and optimize for me? Thanks a mill. All my friends are able to play Tarkov abroad and I am affected by the 190ms ping lock.
Click to expand...
According to this, Tarkov has 2 IPs in each location. Not sure if this information will make much of a difference, just noticed that you only sent through the one IP.

London: 95.168.177.233, 185.59.221.36

I also noticed that out of the JHB looking glass there is a massive difference between leaseweb and CDN77:

Code: 
1 core.as-01.jb1.za.ws.net.za        0%    5   3.7ms     1.2     0.5     3.7
2 core.pe-xe-ip01.jb1.za.ws.net.za   0%    5   3.7ms     1.2     0.5     3.7
3 gi0-0-1-0.agr11.jnb01.atlas.c...   0%    5   6.2ms     2.6     1.4     6.2
4 be2355.ccr51.jnb01.atlas.coge...   0%    5   4.7ms     2.5       1     4.7
5 be2385.ccr21.lon01.atlas.coge...   0%    5 168.8ms   169.2   168.7   170.3
6 leaseweb.demarc.cogentco.com       0%    4 158.5ms   157.8   157.5   158.5
7 po-2.ce02.lon-12.uk.leaseweb.net   0%    4 157.2ms   157.8   157.2     159
8 95.168.177.233                     0%    4 157.1ms   157.3   157.1   157.4

Code: 
1 core.as-01.jb1.za.ws.net.za        0%    4   0.4ms     0.6     0.4     1.1
2 core.pe-xe-ip01.jb1.za.ws.net.za   0%    4   0.5ms     1.2     0.5     2.6
3 gi0-0-1-0.agr11.jnb01.atlas.c...   0%    4   3.6ms     2.2     1.6     3.6
4 be2355.ccr51.jnb01.atlas.coge...   0%    4   1.9ms     1.7     0.9     2.8
5 be2389.ccr22.lon01.atlas.coge...   0%    4 169.4ms   168.3   167.9   169.4
6 be2870.ccr41.lon13.atlas.coge...   0%    4 168.1ms   169.3   168.1   170.6
7 be2572.ccr21.lon02.atlas.coge...   0%    4 179.2ms   180.6   179.2   184.2
8 149.6.148.194                      0%    4 226.3ms   226.6   226.3   226.9
9 vl204.lon-cyx2-dist-2.cdn77.com    0%    3 227.6ms   226.7   226.1   227.6
10 unn-185-59-221-36.datapacket.com   0%    3 225.9ms     226   225.9   226.1


Reverse trace from CDN77 looks like it's routing through New York

Code: 
1  unn-185-59-221-61.cdn77.com (185.59.221.61)  0.107 ms unn-185-59-221-60.cdn77.com (185.59.221.60)  0.061 ms unn-185-59-221-61.cdn77.com (185.59.221.61)  0.081 ms
2  vl202.lon-tel-core-2.cdn77.com (138.199.0.78)  0.153 ms vl201.lon-tel-core-1.cdn77.com (138.199.0.74)  0.202 ms vl203.lon-tel-core-1.cdn77.com (138.199.0.76)  0.202 ms
3  ae22-407.lon10.core-backbone.com (81.95.2.141)  0.529 ms  0.515 ms ae22-401.lon10.core-backbone.com (5.56.17.177)  0.610 ms
4  ae5-2092.nyk10.core-backbone.com (5.56.18.94)  68.680 ms  68.690 ms  68.692 ms
5  unassigned243.nyiix.net (198.32.160.243)  198.737 ms  198.799 ms  198.773 ms
6  81-71-148-197.as37497.za.net (197.148.71.81)  217.139 ms  217.223 ms  217.174 ms
7  206.249.0.202 (206.249.0.202)  225.552 ms  225.571 ms  225.409 ms
8  core.cr-01.jb1.za.ws.net.za (160.119.224.21)  225.811 ms  225.722 ms  225.646 ms
9  100.99.198.6 (100.99.198.6)  215.001 ms  214.796 ms  215.844 ms
 
Last edited:
Well... according to this list they moved exclusively to CDN77 on different IPs (195.181.164.139, 195.181.164.135; @Zodiak can you confirm this?), so what I said above is half hogwash, still the same results however. @websquadza I got in touch with Datapacket support but they told me that "the latency is normal given the vast distance between the two regions", and to eff off unless I was a customer.
 
JustAnotherSouthAfrican said:
Well... according to this list they moved exclusively to CDN77 on different IPs (195.181.164.139, 195.181.164.135; @Zodiak can you confirm this?), so what I said above is half hogwash, still the same results however. @websquadza I got in touch with Datapacket support but they told me that "the latency is normal given the vast distance between the two regions", and to eff off unless I was a customer.
Click to expand...
I previously recorded this IP while connecting to London servers a few weeks ago - 51.89.235.21

So they do use another provider but like 9 out of 10 times it's CDN77.
 
is there any known issues in the alberton / openserve area? my cousin is on Websquad, and seems to have very limited access to everything, she can access the websquad website, she has logged a ticket @websquadza , very technically challenged
 
Last edited:
ijacobs3 said:
is there any known issues in the alberton / openserve area? my cousin is on Websquad, and seems to have very limited access to everything, she can access the websquad website, she has logged a ticket @websquadza , very technically challenged
Click to expand...
Nothing that we’re aware of… Sounds more like an MTU issue. Let me know if you need me to get that ticket checked out?
 
any ideas on when amazon will stop soaking the connection to middle eastern servers, seems like its been like this for a while now, I know they soak for a while after a fault but this has been for a while now and its making me sad :(

1 <1 ms <1 ms <1 ms ARCHER_D2 [192.168.1.2]
2 2 ms 4 ms 2 ms 160.119.237.161
3 1 ms <1 ms <1 ms core.as-01.db1.za.ws.net.za [160.119.233.225]
4 8 ms 8 ms 8 ms 160.119.232.122
5 8 ms 8 ms 8 ms 196-60-9-105.ixp.joburg [196.60.9.105]
6 10 ms 12 ms 9 ms 52.93.56.120
7 8 ms 9 ms 8 ms 52.93.56.135
8 * * * Request timed out.
9 231 ms 231 ms 232 ms 52.93.225.24
10 231 ms 231 ms 231 ms 52.93.225.37
11 232 ms 231 ms 246 ms 52.93.225.2
12 231 ms 232 ms 232 ms 52.93.224.253
13 232 ms 232 ms 235 ms 52.93.227.54
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 231 ms 231 ms 231 ms ec2-157-175-31-202.me-south-1.compute.amazonaws.com [157.175.31.202]

Trace complete.
 
FumblesOne said:
any ideas on when amazon will stop soaking the connection to middle eastern servers, seems like its been like this for a while now, I know they soak for a while after a fault but this has been for a while now and its making me sad :(

1 <1 ms <1 ms <1 ms ARCHER_D2 [192.168.1.2]
2 2 ms 4 ms 2 ms 160.119.237.161
3 1 ms <1 ms <1 ms core.as-01.db1.za.ws.net.za [160.119.233.225]
4 8 ms 8 ms 8 ms 160.119.232.122
5 8 ms 8 ms 8 ms 196-60-9-105.ixp.joburg [196.60.9.105]
6 10 ms 12 ms 9 ms 52.93.56.120
7 8 ms 9 ms 8 ms 52.93.56.135
8 * * * Request timed out.
9 231 ms 231 ms 232 ms 52.93.225.24
10 231 ms 231 ms 231 ms 52.93.225.37
11 232 ms 231 ms 246 ms 52.93.225.2
12 231 ms 232 ms 232 ms 52.93.224.253
13 232 ms 232 ms 235 ms 52.93.227.54
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 231 ms 231 ms 231 ms ec2-157-175-31-202.me-south-1.compute.amazonaws.com [157.175.31.202]

Trace complete.
Click to expand...
Which games do you want to play on ME servers?
Edit: There's a workaround to get back to ~125ms
 
Last edited:
Zodiak said:
Thank you, I am still sitting with over 200ms ping to any EU destination in Tarkov, anyway you guys could help and optimize for me? Thanks a mill. All my friends are able to play Tarkov abroad and I am affected by the 190ms ping lock.
Click to expand...
Can you give this a shot again for us? Thanks for your patience here We adjusted some outbound advertisements and seeing significantly better latency on 185.59.221.36..
JustAnotherSouthAfrican said:
Well... according to this list they moved exclusively to CDN77 on different IPs (195.181.164.139, 195.181.164.135; @Zodiak can you confirm this?), so what I said above is half hogwash, still the same results however. @websquadza I got in touch with Datapacket support but they told me that "the latency is normal given the vast distance between the two regions", and to eff off unless I was a customer.
Click to expand...
Yup, this kind of response is par for the course sadly. A lot of these guys don't see the value in latency centric routing.. On that note, we've made some minor changes on the advertisements to Lon and Paris, so you should see some refinement on these paths.
 
FumblesOne said:
any ideas on when amazon will stop soaking the connection to middle eastern servers, seems like its been like this for a while now, I know they soak for a while after a fault but this has been for a while now and its making me sad :(

1 <1 ms <1 ms <1 ms ARCHER_D2 [192.168.1.2]
2 2 ms 4 ms 2 ms 160.119.237.161
3 1 ms <1 ms <1 ms core.as-01.db1.za.ws.net.za [160.119.233.225]
4 8 ms 8 ms 8 ms 160.119.232.122
5 8 ms 8 ms 8 ms 196-60-9-105.ixp.joburg [196.60.9.105]
6 10 ms 12 ms 9 ms 52.93.56.120
7 8 ms 9 ms 8 ms 52.93.56.135
8 * * * Request timed out.
9 231 ms 231 ms 232 ms 52.93.225.24
10 231 ms 231 ms 231 ms 52.93.225.37
11 232 ms 231 ms 246 ms 52.93.225.2
12 231 ms 232 ms 232 ms 52.93.224.253
13 232 ms 232 ms 235 ms 52.93.227.54
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 231 ms 231 ms 231 ms ec2-157-175-31-202.me-south-1.compute.amazonaws.com [157.175.31.202]

Trace complete.
Click to expand...
This has taken them quite a while. I'll ask the team to reach out and see what is happening there.
 
Hi @websquadza

Hoping you can assist me. I am without fibre internet (openserve) but support keeps telling me I have to pre-pay the unnecessary call out fee but they don't know how I must do it and they are still waiting for feedback.

In the meantime a technician has not even been requested to come out.

My ticket # is 232079
 
tm458 said:
Which games do you want to play on ME servers?
Edit: There's a workaround to get back to ~125ms
Click to expand...
It's between Overwatch, Valorant and fortnite, well those are the ones that I'm used to playing with half decent connection at least.
websquadza said:
This has taken them quite a while. I'll ask the team to reach out and see what is happening there.
Click to expand...
okay awesome I appreciate it a lot, thank you :)
 
lestoran said:
Hi @websquadza

Hoping you can assist me. I am without fibre internet (openserve) but support keeps telling me I have to pre-pay the unnecessary call out fee but they don't know how I must do it and they are still waiting for feedback.

In the meantime a technician has not even been requested to come out.

My ticket # is 232079
Click to expand...
Morning - looking at this ticket, they didn't request you to pay any unnecessary callout fee, the question was simply to confirm everything is 100% before escalating to Openserve, as they charge an unnecessary callout fee should the issue be client side. And to make you aware of that charge. However, we have escalated to Openserve maintenance who will investigate and dispatch a tech. I've asked the team to keep you updated on the ticket
 
websquadza said:
Morning - looking at this ticket, they didn't request you to pay any unnecessary callout fee, the question was simply to confirm everything is 100% before escalating to Openserve, as they charge an unnecessary callout fee should the issue be client side. And to make you aware of that charge. However, we have escalated to Openserve maintenance who will investigate and dispatch a tech. I've asked the team to keep you updated on the ticket
Click to expand...
Think there was a miscommunication then - I checked everything my side, changed cables, even used a different router.

Thank you for your help.
 
FumblesOne said:
It's between Overwatch, Valorant and fortnite, well those are the ones that I'm used to playing with half decent connection at least.
Click to expand...
You can try chubscvpn for valorant and fortnite to get lower ping to ME or you can try exitlag (i think) but it's ~R100 per month.
If you're a technical person and you like some typing then you can also set up your own vpn as well.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X