Status
Not open for further replies.
Did a quick test from my side, have to say, quite impressive :cool:

Tracing route to 187.120.30.6 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 18 ms 22 ms 18 ms 192.168.10.1
4 14 ms 17 ms 20 ms 192.168.11.2
5 17 ms 18 ms 17 ms 154.0.4.209
6 32 ms 31 ms 32 ms 154.0.1.62
7 35 ms 38 ms 37 ms 154.0.4.162
8 32ms 34 ms 33 ms 102.130.64.13
9 69 ms 68 ms 75 ms pe2-nc029.ang.sgn.as37468.angolacables.ao [197.149.151.198]
10 130 ms 131 ms 151 ms 170.238.232.149
11 127 ms 128 ms 134 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
12 130 ms 129 ms 130 ms 170.238.235.18
13 124 ms 124 ms 124 ms 187.120.30.6

Trace complete.

https://hastebin.com/udaxijebev.css
 
WACS died briefly in Cape Town last night, we are still awaiting feedback from the carrier. JHB didn't seem to be affected.
 
Did a quick test from my side, have to say, quite impressive :cool:

Tracing route to 187.120.30.6 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 18 ms 22 ms 18 ms 192.168.10.1
4 14 ms 17 ms 20 ms 192.168.11.2
5 17 ms 18 ms 17 ms 154.0.4.209
6 32 ms 31 ms 32 ms 154.0.1.62
7 35 ms 38 ms 37 ms 154.0.4.162
8 32ms 34 ms 33 ms 102.130.64.13
9 69 ms 68 ms 75 ms pe2-nc029.ang.sgn.as37468.angolacables.ao [197.149.151.198]
10 130 ms 131 ms 151 ms 170.238.232.149
11 127 ms 128 ms 134 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
12 130 ms 129 ms 130 ms 170.238.235.18
13 124 ms 124 ms 124 ms 187.120.30.6

Trace complete.

You in JHB?
Looking better here (CT)

traceroute to 187.120.30.6 (187.120.30.6), 64 hops max
1 10.23.23.1 (router.ibox.za.net) 0.550ms 0.536ms 0.499ms
2 154.0.15.178 (u33m-cust.coolideas.co.za) 3.177ms 2.541ms 3.003ms
3 154.0.15.177 (u33l-cust.coolideas.co.za) 2.979ms 3.254ms 2.705ms
4 154.0.4.162 (uwy-cust.coolideas.co.za) 2.701ms 2.549ms 2.964ms
5 102.130.64.13 (102.130.64.13) 2.971ms 2.905ms 2.683ms
6 197.149.151.198 (pe2-nc029.ang.sgn.as37468.angolacables.ao) 37.640ms 37.149ms 37.556ms
7 170.238.232.149 (170.238.232.149) 99.044ms 98.003ms 101.357ms
8 170.238.232.81 (pe1-nc013.br.ftz.as37468.angolacables.ao) 98.224ms 97.958ms 97.994ms
9 170.238.235.18 (170.238.235.18) 98.493ms 99.077ms 98.902ms
10 187.120.30.6 (187.120.30.6) 98.233ms 98.457ms 97.975ms
 
So got Jacques on site checking the line regarding the poor international upload performance. Appointment was for 11am and he was here at 11am. Impressive.
 
You in JHB?
Looking better here (CT)

traceroute to 187.120.30.6 (187.120.30.6), 64 hops max
1 10.23.23.1 (router.ibox.za.net) 0.550ms 0.536ms 0.499ms
2 154.0.15.178 (u33m-cust.coolideas.co.za) 3.177ms 2.541ms 3.003ms
3 154.0.15.177 (u33l-cust.coolideas.co.za) 2.979ms 3.254ms 2.705ms
4 154.0.4.162 (uwy-cust.coolideas.co.za) 2.701ms 2.549ms 2.964ms
5 102.130.64.13 (102.130.64.13) 2.971ms 2.905ms 2.683ms
6 197.149.151.198 (pe2-nc029.ang.sgn.as37468.angolacables.ao) 37.640ms 37.149ms 37.556ms
7 170.238.232.149 (170.238.232.149) 99.044ms 98.003ms 101.357ms
8 170.238.232.81 (pe1-nc013.br.ftz.as37468.angolacables.ao) 98.224ms 97.958ms 97.994ms
9 170.238.235.18 (170.238.235.18) 98.493ms 99.077ms 98.902ms
10 187.120.30.6 (187.120.30.6) 98.233ms 98.457ms 97.975ms

I'm in Bloemfontein, hence the extra delay on my side. I had a feeling you guys in Cpt will have lower latency. Still, 120ms for me is still more than playable games wise :)
 
I'm in Bloemfontein, hence the extra delay on my side. I had a feeling you guys in Cpt will have lower latency. Still, 120ms for me is still more than playable games wise :)

Only problem is there are few, if any game servers (that i know of) that are hosted in fortaleza. Most of the servers are in sao paulo which is +44ms~ and therefore its identical to the ping we get to london. Such a shame really, i would love to play with 96ms on international servers.
 
Only problem is there are few, if any game servers (that i know of) that are hosted in fortaleza. Most of the servers are in sao paulo which is +44ms~ and therefore its identical to the ping we get to london. Such a shame really, i would love to play with 96ms on international servers.

Bah, you're right. I tried out PUBG mobile last night, thinking that I would see a lower latency with the South America, but yeah.. no dice. Still had a 350ms latency.
 
Bah, you're right. I tried out PUBG mobile last night, thinking that I would see a lower latency with the South America, but yeah.. no dice. Still had a 350ms latency.

I had a similar experience with fortnite, but i did manage to get on sao paulo servers with 140ms when i selected squads. The routing still needs to be updated/changed for it to use sacs on all the aws servers, right now only some of them do.
 
Only problem is there are few, if any game servers (that i know of) that are hosted in fortaleza. Most of the servers are in sao paulo which is +44ms~ and therefore its identical to the ping we get to london. Such a shame really, i would love to play with 96ms on international servers.

Twitch has been better than ever for me since cisp sorted out their routing through SACS and started drawing from the rio twitch servers. Even with low latency mode. For games at least now we have an alternative to EU even if the ping is the same. Choice here can only be a good thing.

Now we wait for the next undersea cable to be built :D

-fs-Seaborn-Networks-Map-2018.xl.jpg
 
Just had a chat with someone there they will let me know if it’s maintence or just all separate isps apart from them issue again. Will update this message once I get a message

Metro Fibre
Please note we are getting complaints of no connectivity on MetroFibre.
Our technicians are looking into the issue.
We apologise for any inconvenience
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X