Afrihost - Pure Fibre Feedback Thread Part 2

What is happening with the COD MW2 profile not loading? Is there a solution to fix this? I was the one who brought this up when I found I get instant prile load if I use Vodacom hot spot. My fibre was down for a few days, so I was forced to use my Vodacom hotspot for a few days and the only problem was high latency, making it nearly impossible to play.

Have you found out what is causing the COD MW2 profile loading problem only on Afrihost?

Is there a solution?

For me warp+ is the only way to play and get past the disconnection notices and the loooong profile loading

Hi

I'm still trying to figure this issue out.
 
What is happening with the COD MW2 profile not loading? Is there a solution to fix this? I was the one who brought this up when I found I get instant prile load if I use Vodacom hot spot. My fibre was down for a few days, so I was forced to use my Vodacom hotspot for a few days and the only problem was high latency, making it nearly impossible to play.

Have you found out what is causing the COD MW2 profile loading problem only on Afrihost?

Is there a solution?
Yes, pm me in the morning, I may have a solution.
 
BTW our capacity on Equiano went live and we have routed clients accordingly. Cape Town is back to 145ms CPT <> LON
how can I see if I'm routing over the equiano route? I am in CPT and my trace to LDN is 160-170 - this is a hard wired trace from my nas

Code:
traceroute to 193.62.157.66 (193.62.157.66), 30 hops max, 60 byte packets
 1  router.lan (192.168.88.1)  0.945 ms  0.782 ms  0.909 ms
 2  * * *
 3  165-73-14-113.ip.afrihost.co.za (165.73.14.113)  7.437 ms 165-73-14-137.ip.afrihost.co.za (165.73.14.137)  6.659 ms  7.322 ms
 4  169-1-21-148.ip.afrihost.co.za (169.1.21.148)  3.796 ms 169-1-21-132.ip.afrihost.co.za (169.1.21.132)  4.321 ms 169-1-21-148.ip.afrihost.co.za (169.1.21.148)  3.727 ms
 5  169-1-21-133.ip.afrihost.co.za (169.1.21.133)  3.531 ms 169-1-21-132.ip.afrihost.co.za (169.1.21.132)  4.251 ms  4.267 ms
 6  wdcnw-os-cer-1-wan.osnet.co.za (196.25.158.241)  3.501 ms  4.766 ms  2.730 ms
 7  wdcnw-os-cer-1-wan.osnet.co.za (196.25.158.241)  3.662 ms * *
 8  213.242.116.161 (213.242.116.161)  160.104 ms  161.024 ms  160.929 ms
 9  * 213.242.116.161 (213.242.116.161)  161.006 ms  160.457 ms
10  * * JANET.ear3.London2.Level3.net (212.187.216.238)  169.513 ms
11  JANET.ear3.London2.Level3.net (212.187.216.238)  169.208 ms  170.788 ms 146.97.35.193 (146.97.35.193)  170.468 ms
12  ae24.londtt-sbr1.ja.net (146.97.35.193)  173.228 ms  170.327 ms ae25.londtt-ban1.ja.net (146.97.35.18)  169.905 ms
13  ae20-100.londtt-gw1.ja.net (146.97.35.86)  169.813 ms  169.794 ms  169.961 ms
14  * ae20-100.londtt-gw1.ja.net (146.97.35.86)  169.435 ms *
15  * * *
16  * * *
 
For KZN the lowest latency route is still EASSy or Equiano up the East Coast so KZN has reached the lowest pings it can for now.
So if i understood this correctly. Some of JHB traffic has been diverted through the new Liquid Equiano express route. But as of yet your unable to send all the traffic from JHB through the express route.

Will this change and eventually and all of JHB goes through Liquid Equiano?

Wouldn't this result in even better ping latency for KZN users using EASSy Cable with less traffic?
 
So if i understood this correctly. Some of JHB traffic has been diverted through the new Liquid Equiano express route. But as of yet your unable to send all the traffic from JHB through the express route.

Will this change and eventually and all of JHB goes through Liquid Equiano?

Wouldn't this result in even better ping latency for KZN users using EASSy Cable with less traffic?
The traffic is still split because of capacity. Once WACS is back online, we will review and discuss with our providers the way forward.
 
Leon Thevenin (Fibre Repair Vessel) is almost in CPT. Then the next leg is up to the fibre break near Cameroon.

Track Here

Screenshot_2023-08-18-17-39-35-447_com.xbrowser.play-edit.jpg
 
Hi

I'm still trying to figure this issue out.
Maybe try port forwarding or is the nat type possibly not set to open?

Cod Mw2 Ports:
  • Ports To Forward On PC – Windows. TCP: 3074,27014-27050. UDP: 3478,4379-4380,27000-27031,27036.
  • Ports To Forward On PlayStation 4. TCP: 1935,3478-3480. UDP: 3074,3478-3479.
  • Ports To Forward On Xbox One. TCP: 3074. UDP: 88,500,3074-3075,3544,4500.
 
Hi @AfriNatic @Afrigirl,

I have another credit request for RDQ-994-18524.

Went down on the 3rd of August. Connectivity was finally restored on the 18th of August.

This ticket can be marked as closed.
 
The JHB to Lisbon PT express route is :cool:

From our JHB core to a peer in Lisbon

View attachment 1573930
Centurion to a peer in Lisbon


View attachment 1573926


apTqYPh.png


Where else does this express route go?
 
Yes it's about ~139ms from JHB Core to Lisbon on our new Liquid Equiano express route :) So some traffic might still go via EASSy on the East Coast due to traffic volumes we cannot send all traffic via this express route.

Once the two subsea cables are fixed in the months to come, will traffic still be routed through Equiano or will all types of traffic fall back onto the original cables?
 
Once the two subsea cables are fixed in the months to come, will traffic still be routed through Equiano or will all types of traffic fall back onto the original cables?
Once WACS is back online, we will review and discuss with our providers the way forward.
 
Once the two subsea cables are fixed in the months to come, will traffic still be routed through Equiano or will all types of traffic fall back onto the original cables?
It makes sense to stick with the cables that don’t break.
 
I'm doing some testing to Brazilian servers out of curiosity and learning purposes and saw this, can anyone tell me the route traffic is taking for latency to be this low?

1692609039773.png

Surely it can't be going through EU and NA, if it's actually using SACS then I'd be shook.
 
Top
Sign up to the MyBroadband newsletter
X