High Ping is normal on VOX FIBRE ?

[RedHotChilli]

Hello all, so i have been with vox for about 2 years now. I have the 40mbps package on openserve. As of lately i have started to play Some international games such as League of Legends mostly,I of course did alot of reasearch of the lowest ping we could get here in SA that would be around 140 for the CT peeps. sadly i live in Pretoria. to get to the point i play with around 220 ping constant. I do not believe that this is acceptatble for fibre.
--------------------------------------------------------------------------------------
Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=220ms TTL=52
Reply from 104.160.141.3: bytes=32 time=219ms TTL=52
Reply from 104.160.141.3: bytes=32 time=220ms TTL=52
Reply from 104.160.141.3: bytes=32 time=220ms TTL=52

Ping statistics for 104.160.141.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 219ms, Maximum = 220ms, Average = 219ms
--------------------------------------------------------------------------------------

I also do know that the ping command is not always correct but this is my actual ping ingame as well.
as said lets say any blizzard title like overwatch i get around 230+ ping.
i did message Vox and got this response.
"
Good day,

Trust you are well.

I have escalated this to this our advanced team and they have confirmed that the ping time you are getting is normal for international servers on our network.
"

could some of you guys maybe post ISP and pings for LOL or overwatch ?

 

[Soul Assassin]

Move ISPs.

Vox refuses to use WACS for anyone in the North, they use EASSy, I've been through the emailing them and everything.

When I want to play any EU games on Vox I turn my VPN on first and my ping goes down 30-40ms to 166ms.

 

[RedHotChilli]

Move ISPs.

Vox refuses to use WACS for anyone in the North, they use EASSy, I've been through the emailing them and everything.

When I want to play any EU games on Vox I turn my VPN on first and my ping goes down 30-40ms to 166ms.

What VPN do you use at the moment ?
i am also fed up with this they also charged me for a 100mb line for 2 years now even being only on 40mbps package
which ISP could you recommend ?

 

[Soul Assassin]

What VPN do you use at the moment ?
i am also fed up with this they also charged me for a 100mb line for 2 years now even being only on 40mbps package
which ISP could you recommend ?

Cloudflare Warp and I recommend Web Squad.

I'll ping that IP on the morning with and without VPN and post the results.

 

[Soul Assassin]

With:

Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=186ms TTL=57
Reply from 104.160.141.3: bytes=32 time=186ms TTL=57
Reply from 104.160.141.3: bytes=32 time=186ms TTL=57
Reply from 104.160.141.3: bytes=32 time=186ms TTL=57

Ping statistics for 104.160.141.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 186ms, Maximum = 186ms, Average = 186ms

Without:

Pinging 104.160.141.3 with 32 bytes of data:
Reply from 104.160.141.3: bytes=32 time=223ms TTL=52
Reply from 104.160.141.3: bytes=32 time=223ms TTL=52
Reply from 104.160.141.3: bytes=32 time=223ms TTL=52
Reply from 104.160.141.3: bytes=32 time=225ms TTL=52

Ping statistics for 104.160.141.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 225ms, Average = 223ms

 

[mikewazar]

@LouisGomes

Do a traceroute or MTR to the destination to look at the path taken, from there I can assist in identifying where the latency is added and where you can cut latency.

Mike

 

[mikewazar]

Please @ my username so I see a notification if you need assistance.

Mike

 

[Soul Assassin]

@LouisGomes

Do a traceroute or MTR to the destination to look at the path taken, from there I can assist in identifying where the latency is added and where you can cut latency.

Mike

It's definitely a EASSy vs WACS thing.

 

[RedHotChilli]

@WAZAR
Tracing route to 104.160.131.3 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 3 ms 3 ms 3 ms 41.193.164.85
4 3 ms 3 ms 3 ms 41.193.164.86
5 4 ms 3 ms 3 ms 41.193.164.92
6 5 ms 4 ms 4 ms 41.193.119.29
7 19 ms 19 ms 19 ms 41.193.118.141
8 21 ms 21 ms 21 ms 41.193.120.38
9 209 ms 209 ms 209 ms nyiix.riotdirect.net [198.32.160.32]
10 211 ms 211 ms 211 ms 104.160.132.35
11 225 ms 225 ms 225 ms 104.160.131.3

this is my foundigs, these are actually the fewest hops i got.

have to agree with Soul Assasin that this is a EASSy vs WACS thing. I also saw that seacom has launched their own ISP wondernet here in SA wonder how their ping would be like.

 

[mikewazar]

@WAZAR
/snip

Does seem to be the case, you're routing JHB -> CPT -> NY (?) via west coast.

On Afrihost:

1  * * *
 2  165.73.14.17  5.213 ms  4.137 ms  4.076 ms
 3  169.1.21.232  6.235 ms  3.815 ms  3.579 ms
 4  169.1.21.233  4.072 ms  3.732 ms  3.674 ms
 5  196.25.153.41  9.846 ms  8.104 ms  10.470 ms
 6  10.189.30.6  166.134 ms  166.313 ms  165.916 ms
 7  149.14.126.225  166.377 ms  166.515 ms  166.386 ms
 8  62.115.179.96  233.407 ms  233.692 ms  233.724 ms
 9  * * *
10  * * *
11  62.115.112.244  257.060 ms * *
12  80.91.246.162  239.571 ms  239.807 ms  239.815 ms
13  62.115.63.66  239.768 ms  239.851 ms  239.046 ms
14  104.160.131.3  239.778 ms  239.709 ms  242.427 ms

On Vox:

 1  * * *
 2  41.193.164.85  3.590 ms  3.379 ms  3.561 ms
 3  41.193.164.86  3.289 ms  3.440 ms  3.239 ms
 4  41.193.164.92  4.173 ms  3.375 ms  3.750 ms
 5  41.193.119.29  4.364 ms  3.967 ms  4.092 ms
 6  41.193.118.141  19.502 ms  19.795 ms  19.561 ms
 7  41.193.120.38  19.010 ms  18.977 ms  53.841 ms
 8  198.32.160.32  213.348 ms  211.524 ms  213.162 ms
 9  104.160.132.35  212.441 ms  212.513 ms *
10  104.160.131.3  227.854 ms  225.233 ms  227.278 ms

@Soul Assassin mind dropping a trace on Vox and on Warp to see the difference in routing? on Warp (via JNB) I get comparable performance to both Vox and Afrihost

 

[Soul Assassin]

Vox:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms     8 ms     8 ms  41.193.3.101
  4     8 ms     9 ms     8 ms  41.193.3.102
  5     9 ms    12 ms    13 ms  196.41.12.0
  6    10 ms    10 ms    10 ms  41.193.119.21
  7    25 ms    25 ms    25 ms  41.193.118.141
  8    24 ms    24 ms    24 ms  41.193.120.38
  9   214 ms   214 ms   217 ms  nyiix.riotdirect.net [198.32.160.32]
 10   218 ms   214 ms   218 ms  104.160.132.35
 11   230 ms   231 ms   231 ms  104.160.131.3

Warp+:

  1     9 ms     9 ms    11 ms  172.16.0.1
  2    10 ms    10 ms    10 ms  197.234.241.1
  3    10 ms    10 ms     9 ms  ae-2-113.er-01-jnb.za.seacomnet.com [105.22.32.217]
  4   180 ms   183 ms   182 ms  ce-0-2-0-0.cr-01-jnb.za.seacomnet.com [105.16.28.1]
  5   165 ms   167 ms   167 ms  xe-0-0-0-2.cr-01-cpt.za.seacomnet.com [105.16.8.226]
  6   168 ms   167 ms   167 ms  xe-0-0-0-1.cr-01-lhr.uk.seacomnet.com [105.16.8.234]
  7   169 ms   169 ms   172 ms  ae-3-0.pp-01-lhr.uk.seacomnet.com [105.16.34.8]
  8   167 ms   190 ms   165 ms  ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
  9   243 ms     *        *     ae4.cs3.lhr11.uk.eth.zayo.com [64.125.28.194]
 10   243 ms     *        *     ae5.cs3.lga5.us.eth.zayo.com [64.125.29.126]
 11   243 ms   243 ms   242 ms  ae1.mcs1.lga5.us.eth.zayo.com [64.125.29.201]
 12     *      242 ms   242 ms  ae10.mpr3.lga7.us.zip.zayo.com [64.125.20.77]
 13   243 ms   242 ms   242 ms  128.177.169.158.IPYX-089814-970-ZYO.zip.zayo.com [128.177.169.158]
 14   243 ms   243 ms   243 ms  104.160.132.35
 15   263 ms   264 ms   263 ms  104.160.131.3

This one is not very Warp friendly at all

 

[mikewazar]

Vox seems to be going direct from west coast ZA to NY (USA) while Warp uses the POP in LON (UK) first - so I doubt you'll find much better pings to US east from ZA.

 

[mikewazar]

IIRC Vox peers in NY directly, too.

 

[Soul Assassin]

Vox would be so amazing if they just let us use WACS, it's such a shame.

 

[mikewazar]

Vox would be so amazing if they just let us use WACS, it's such a shame.

Throw a few traceroutes to some IPs that go via the eastern cables (usually ZA -> FR -> DE) for me please, I can try to ask someone at their NOC about it. The problem is, a lot of traffic from ZA comes from Europe, where WACS (which lands in UK) has to travel further than the Eastern cables that land in FR.

 

[mikewazar]

Vox peers directly at LINX, NY, BR and all major ZA POPs.

 

[Soul Assassin]

Throw a few traceroutes to some IPs that go via the eastern cables (usually ZA -> FR -> DE) for me please, I can try to ask someone at their NOC about it. The problem is, a lot of traffic from ZA comes from Europe, where WACS (which lands in UK) has to travel further than the Eastern cables that land in FR.

There is really just the one IP I want and it's only a couple of ms:

With:

Ping statistics for 217.147.89.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 172ms, Average = 172ms

Without:

Ping statistics for 217.147.89.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 188ms, Maximum = 188ms, Average = 188ms

With:

  1     9 ms    10 ms    10 ms  172.16.0.1
  2    11 ms    10 ms    11 ms  197.234.241.1
  3    10 ms    10 ms    10 ms  ae-2-113.er-01-jnb.za.seacomnet.com [105.22.32.217]
  4   167 ms   173 ms   167 ms  ce-0-3-0-0.cr-02-jnb.za.seacomnet.com [105.16.29.2]
  5   168 ms   168 ms   166 ms  xe-0-0-0-8.cr-02-cpt.za.seacomnet.com [105.16.9.182]
  6   175 ms   167 ms   169 ms  xe-0-1-0-3.cr-02-lhr.uk.seacomnet.com [105.16.11.25]
  7   166 ms   166 ms   166 ms  xe-1-0-0-0.er-05-lhr.uk.seacomnet.com [105.16.9.30]
  8   166 ms   166 ms   166 ms  ae-1.pp-02-lhr.uk.seacomnet.com [105.16.11.6]
  9   174 ms   173 ms   173 ms  be20.asr01.ld5.as20860.net [195.66.226.230]
10   173 ms   173 ms   173 ms  be98.asr01.thn.as20860.net [62.128.211.137]
11   169 ms   170 ms   169 ms  be10.asr01.dc5.as20860.net [130.180.202.45]
12   173 ms   173 ms   174 ms  1717.g1.1ug.dc5.as20860.net [87.117.210.26]
13   170 ms   171 ms   172 ms  217.147.89.101

Without:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     8 ms  41.193.3.101
  4    10 ms     9 ms     9 ms  41.193.3.102
  5    10 ms    11 ms    10 ms  196.41.12.0
  6    10 ms    14 ms    12 ms  41.193.119.21
  7   196 ms   188 ms   187 ms  196.41.24.122
  8   188 ms   188 ms   189 ms  be20.asr01.thn.as20860.net [195.66.224.207]
  9   188 ms   189 ms   188 ms  be10.asr01.dc5.as20860.net [130.180.202.45]
 10   189 ms   190 ms   189 ms  1717.g1.1ug.dc5.as20860.net [87.117.210.26]
 11   188 ms   188 ms   188 ms  217.147.89.101

 

[mikewazar]

There is really just the one IP I want and it's only a couple of ms:

With:

Ping statistics for 217.147.89.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 172ms, Average = 172ms

Without:

Ping statistics for 217.147.89.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 188ms, Maximum = 188ms, Average = 188ms

With:

  1     9 ms     9 ms     9 ms  172.16.0.1
  2    10 ms    12 ms    10 ms  197.234.241.1
  3    12 ms    10 ms     9 ms  ae-2-113.er-01-jnb.za.seacomnet.com [105.22.32.217]
  4   173 ms   172 ms   175 ms  ce-0-3-0-0.cr-01-jnb.za.seacomnet.com [105.16.29.1]
  5   183 ms   187 ms   182 ms  xe-0-1-0-4.cr-01-cpt.za.seacomnet.com [105.16.11.90]
  6   171 ms   170 ms   168 ms  xe-0-0-0-4.cr-01-lhr.uk.seacomnet.com [105.16.13.38]
  7   170 ms   172 ms   170 ms  xe-0-0-0-0.er-05-lhr.uk.seacomnet.com [105.16.9.26]
  8   168 ms   168 ms   168 ms  ae-1.pp-02-lhr.uk.seacomnet.com [105.16.11.6]
  9   168 ms   168 ms   168 ms  be20.asr01.ld5.as20860.net [195.66.226.230]
10   169 ms   169 ms   169 ms  be10.asr02.dc5.as20860.net [130.180.202.47]
11   168 ms   168 ms   169 ms  1718.g2.1ug.dc5.as20860.net [87.117.210.30]
12   170 ms   172 ms   169 ms  87.117.210.61
13   175 ms   174 ms   176 ms  217.147.89.101

Without:

  1     9 ms    10 ms    10 ms  172.16.0.1
  2    11 ms    10 ms    11 ms  197.234.241.1
  3    10 ms    10 ms    10 ms  ae-2-113.er-01-jnb.za.seacomnet.com [105.22.32.217]
  4   167 ms   173 ms   167 ms  ce-0-3-0-0.cr-02-jnb.za.seacomnet.com [105.16.29.2]
  5   168 ms   168 ms   166 ms  xe-0-0-0-8.cr-02-cpt.za.seacomnet.com [105.16.9.182]
  6   175 ms   167 ms   169 ms  xe-0-1-0-3.cr-02-lhr.uk.seacomnet.com [105.16.11.25]
  7   166 ms   166 ms   166 ms  xe-1-0-0-0.er-05-lhr.uk.seacomnet.com [105.16.9.30]
  8   166 ms   166 ms   166 ms  ae-1.pp-02-lhr.uk.seacomnet.com [105.16.11.6]
  9   174 ms   173 ms   173 ms  be20.asr01.ld5.as20860.net [195.66.226.230]
10   173 ms   173 ms   173 ms  be98.asr01.thn.as20860.net [62.128.211.137]
11   169 ms   170 ms   169 ms  be10.asr01.dc5.as20860.net [130.180.202.45]
12   173 ms   173 ms   174 ms  1717.g1.1ug.dc5.as20860.net [87.117.210.26]
13   170 ms   171 ms   172 ms  217.147.89.101

These both follow the same path, and both look like Warp+ paths, are you 100% sure?

 

[Soul Assassin]

These both follow the same path, and both look like Warp+ paths, are you 100% sure?

I copied the wrong thing, fixed now.

 

[mikewazar]

Looks like Vox is using Cogent (transit) to that destination, while Warp is using Seacom - do you know a network with better routes to that destination I can send along?

 

[RedHotChilli]

I need the ping mostly to be low to EU, I also played Fortnite just for ping reasons and saw that i got a 155ms from JHB on vox, not sure how this works, but mostly servers to FR and Amsterdam is where most my traffic is going. Is there any ISP in JHB that uses WACS, i spoke to Websquad and used theyre looking glass and got pretty good MS

Web Squad Connect AS328137 - Looking Glass

lg.as328137.net

via websquad ::
[joburg.lg.as328137.net] ping to 104.160.141.3
SEQ HOST SIZE TTL TIME STATUS
0 104.160.141.3 56 55 167ms
1 104.160.141.3 56 55 167ms
2 104.160.141.3 56 55 167ms
3 104.160.141.3 56 55 167ms
4 104.160.141.3 56 55 167ms
sent=5 received=5 packet-loss=0% min-rtt=167ms avg-rtt=167ms
max-rtt=167ms

if i could get this Ping lower this ping goes to Amsterdam if i am correct.
via vox:
Tracing route to 104.160.141.3 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 3 ms 4 ms 4 ms 41.193.164.85
4 3 ms 3 ms 6 ms 41.193.164.86
5 4 ms 4 ms 5 ms 41.193.164.92
6 4 ms 4 ms 4 ms 41.193.119.29
7 181 ms 181 ms 181 ms 196.41.24.122
8 181 ms 181 ms 189 ms ldn-b3-link.telia.net [213.248.100.161]
9 * * * Request timed out.
10 182 ms 182 ms 183 ms adm-bb4-link.telia.net [62.115.113.238]
11 190 ms 182 ms 183 ms adm-b1-link.telia.net [62.115.137.65]
12 * * 218 ms riot-ic-310545-adm-b7.c.telia.net [62.115.54.126]
13 * * * Request timed out.
14 219 ms 218 ms 220 ms 104.160.141.3

Trace complete.

 

[Soul Assassin]

Looks like Vox is using Cogent (transit) to that destination, while Warp is using Seacom - do you know a network with better routes to that destination I can send along?

Afrihost:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    11 ms     9 ms     9 ms  165-73-14-17.ip.afrihost.co.za [165.73.14.17]
  4     9 ms     8 ms     8 ms  169-1-21-232.ip.afrihost.co.za [169.1.21.232]
  5     9 ms     9 ms     8 ms  169-1-21-233.ip.afrihost.co.za [169.1.21.233]
  6    10 ms     9 ms    10 ms  196.25.153.41
  7   171 ms   171 ms   171 ms  10.189.30.2
  8   174 ms   173 ms   172 ms  be20.asr01.ld5.as20860.net [195.66.226.230]
  9   172 ms   172 ms   176 ms  be10.asr02.dc5.as20860.net [130.180.202.47]
 10   173 ms   172 ms   172 ms  be65535.asr01.dc5.as20860.net [130.180.203.8]
 11   173 ms   173 ms   174 ms  1717.g1.1ug.dc5.as20860.net [87.117.210.26]
 12   177 ms   176 ms   176 ms  217.147.89.101

Webafrica:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  102-65-64-25.ftth.web.africa [102.65.64.25]
  4     8 ms     8 ms     8 ms  102-65-64-10.ftth.web.africa [102.65.64.10]
  5     9 ms     8 ms     7 ms  vlan4042.terjhb-dist-sw2.net.echosp.link [102.67.177.15]
  6     9 ms     9 ms     9 ms  100.67.222.6
  7     8 ms     8 ms     8 ms  ethernet51/1-100.terjhb-igw2.net.echosp.link [102.67.177.7]
  8    11 ms    18 ms    16 ms  rndf-ip-ll-1-wan.telkom-ipnet.co.za [196.25.199.141]
  9   171 ms   171 ms   172 ms  10.189.30.2
 10   172 ms   172 ms   173 ms  be20.asr01.ld5.as20860.net [195.66.226.230]
 11   177 ms   176 ms   176 ms  be10.asr02.dc5.as20860.net [130.180.202.47]
 12   172 ms   172 ms   172 ms  be65535.asr01.dc5.as20860.net [130.180.203.8]
 13   172 ms   173 ms   173 ms  1717.g1.1ug.dc5.as20860.net [87.117.210.26]
 14   171 ms   172 ms   172 ms  217.147.89.101

 

[Soul Assassin]

I need the ping mostly to be low to EU, I also played Fortnite just for ping reasons and saw that i got a 155ms from JHB on vox, not sure how this works, but mostly servers to FR and Amsterdam is where most my traffic is going. Is there any ISP in JHB that uses WACS, i spoke to Websquad and used theyre looking glass and got pretty good MS

Web Squad Connect AS328137 - Looking Glass

lg.as328137.net

via websquad ::
[joburg.lg.as328137.net] ping to 104.160.141.3
SEQ HOST SIZE TTL TIME STATUS
0 104.160.141.3 56 55 167ms
1 104.160.141.3 56 55 167ms
2 104.160.141.3 56 55 167ms
3 104.160.141.3 56 55 167ms
4 104.160.141.3 56 55 167ms
sent=5 received=5 packet-loss=0% min-rtt=167ms avg-rtt=167ms
max-rtt=167ms

if i could get this Ping lower this ping goes to Amsterdam if i am correct.
via vox:
Tracing route to 104.160.141.3 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 3 ms 4 ms 4 ms 41.193.164.85
4 3 ms 3 ms 6 ms 41.193.164.86
5 4 ms 4 ms 5 ms 41.193.164.92
6 4 ms 4 ms 4 ms 41.193.119.29
7 181 ms 181 ms 181 ms 196.41.24.122
8 181 ms 181 ms 189 ms ldn-b3-link.telia.net [213.248.100.161]
9 * * * Request timed out.
10 182 ms 182 ms 183 ms adm-bb4-link.telia.net [62.115.113.238]
11 190 ms 182 ms 183 ms adm-b1-link.telia.net [62.115.137.65]
12 * * 218 ms riot-ic-310545-adm-b7.c.telia.net [62.115.54.126]
13 * * * Request timed out.
14 219 ms 218 ms 220 ms 104.160.141.3

Trace complete.

The reason your ping in Fortnite with Vox is so good is because of AWS Direct Connect.

 

[RedHotChilli]

The reason your ping in Fortnite with Vox is so good is because of AWS Direct Connect.

I also see that Riot Games use AWS, isnt it possible to also then use AWS direct Connect to them ?

 

[Soul Assassin]

I also see that Riot Games use AWS, isnt it possible to also then use AWS direct Connect to them ?

I have no idea, I've never played any of their games, I always thought they have their own servers and I'm pretty sure they don't have a London server, if I had to guess I'd say it's Frankfurt or Maybe Amsterdam.

 

[RedHotChilli]

I have no idea, I've never played any of their games, I always thought they have their own servers and I'm pretty sure they don't have a London server, if I had to guess I'd say it's Frankfurt or Maybe Amsterdam.

Yes thats correct only those to locations sadly, they used to have their own servers but moved to AWS recently

 

[virus786]

<Random_Comment>
Out of pure curiosity, here is Rain LTE vs Warp+.
Location: CPT
Destination: 217.147.89.101

Rain LTE:

Rain LTE with Warp+:

</Random_Comment>