Afrihost - Pure Fibre Feedback Thread Part 2

2 are down at the same time, that's the issue.
WACS is the one I'm referring to. SAT3 is a tiny 20+ year old cable that should be obsolete by now. Why are we even dependent on it still. Look at this and tell me why we're even sitting with this issue...

1000013314.png
 
Funnily, a backup 5G Rain SIM I had has been positively perfect this entire time, and became a primary for me.
Not sure what transit they are using.
 
WACS is the one I'm referring to. SAT3 is a tiny 20+ year old cable that should be obsolete by now. Why are we even dependent on it still. Look at this and tell me why we're even sitting with this issue...

View attachment 1571258
It costs ISP's millions to buy capacity on the cables. If they did it for more cables that would be very costly.
 
My Frankfurt ping keeps going down, this is amazing.

46.165.240.201

Before cable break: 204ms
Today: 177ms
 
Last edited:
My Frankfurt ping keeps going down, this is amazing.

46.165.240.201

Before cable break: 204ms
Today: 177ms

I can see and it's taking a very long route via Liquid Telecoms.

JHB <> Harare ZW <> Nairobi KE <> Marseille <> London <> Amsterdam <> Paris <> Frakfurt
 
It comes at a cost though. Higher latency to EU West like London and the US and even higher to South America.

I can see and it's taking a very long route via Liquid Telecoms.

JHB <> Harare ZW <> Nairobi KE <> Marseille <> London <> Amsterdam <> Paris <> Frakfurt
So you've said both that lower latency to Frankfurt was coming at the cost of higher latency to EU West, but are now showing that traffic to Frankfurt is passing through EU West on it's way to Frankfurt? Those statements seem somewhat inconsistent.
 
I can see and it's taking a very long route via Liquid Telecoms.

JHB <> Harare ZW <> Nairobi KE <> Marseille <> London <> Amsterdam <> Paris <> Frakfurt
The last time I saw this latency to that server was with ExitLag.

--- 46.165.240.201 ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 176.431/176.586/176.899 ms

Take away the Openserve overhead, 166ms to Frankfurt is top tier.
 
So you've said both that lower latency to Frankfurt was coming at the cost of higher latency to EU West, but are now showing that traffic to Frankfurt is passing through EU West on it's way to Frankfurt? Those statements seem somewhat inconsistent.
Because instead of landing in England and having a London ping of 165ms it goes via France/Europe at ~175ms.
 
So you've said both that lower latency to Frankfurt was coming at the cost of higher latency to EU West, but are now showing that traffic to Frankfurt is passing through EU West on it's way to Frankfurt? Those statements seem somewhat inconsistent.

From JHB over Liquid telecoms there are multiple paths.

JHB to DUR then Marseille
JHB to Zimbabwe to Nairobi to Marseille

From JHB these routes are about ~164ms landed. From Marseille to London on Liquid is another 22ms+ so that is 186-189ms to London vs WACS JHB to London is 161ms but then from London to Germany or France takes a hit and is around 198 -205ms.

JHB to Marseille is an ever worse route to the East coast of the US as latency is then around 295ms where with WACS JHB to LON to NY is 236ms
 
Because instead of landing in England and having a London ping of 165ms it goes via France/Europe at ~175ms.

And it's impossible to take the map and say half of this via WACS and half of this via EASSy because BGP doesn't use that for route selection. As soon as WACS come online traffic will switch back to via London and as you can see from the trace routes that is where Leaseweb announces all their European prefixes. That is the shortest bgp path. Not the lowest latency especially when it comes to Cogent I don't think they peer with Leaseweb at Linx maybe at AMS-ix.
 
And unfortunately, Cape Town clients are the hardest hit as they need to go via JHB or DUR to Marseille so they went from 145-147ms to London to 200-230ms
 
And it's impossible to take the map and say half of this via WACS and half of this via EASSy because BGP doesn't use that for route selection. As soon as WACS come online traffic will switch back to via London and as you can see from the trace routes that is where Leaseweb announces all their European prefixes. That is the shortest bgp path. Not the lowest latency especially when it comes to Cogent I don't think they peer with Leaseweb at Linx maybe at AMS-ix.
Leaseweb is the worst, but that's a story for another day, for now I'm just enjoying this ping.

We might just have had an on day and it's placebo but it felt really good to me.
 
And unfortunately, Cape Town clients are the hardest hit as they need to go via JHB or DUR to Marseille so they went from 145-147ms to London to 200-230ms
Yeah I spoke to someone from Cape Town yesterday that also plays Hunt Showdown and they said their normal 150-160ms is now 200ms
 
Any issue in Midrand with MFN and Afrihost, logged a call with AH and got told working on a possible issue?
 
Top
Sign up to the MyBroadband newsletter
X