Afrihost - Pure Fibre Feedback Thread

[cavedog]

Ohh and Cloudflare JHB Peering back online!

 

[cavedog]

Quad9 DNS is so so so fast

 

[cavedog]

View attachment 789423

Mine is still gucci, but I did tell everyone to not share accounts but rather regen new ones...

You using wireguard or unsafe?

Mine is stuffed no matter what config I use.

 

[cavedog]

Wireguard.

Was your config shared? I've had my session open for a long time so it could be that. I won't reconnect to find out.

My paid config was shared. That I cancelled and then used the config you sent me. Traffic still going to LHR. Being dynamic IP on Afrihost I can't see they blocked my IP unless they blocked the entire Openserve Afrihost range but that does not seem right.

 

[luckystrike]

Mine also runs over LHR and i am on frogfoot. And i did not share my paid account with anybody.

I will not reconnect if i am you

 

[VegOtter]

Anyone else in the Durban area that is just dead? Fibre is green, but not connecting to afrihost...

UPDATE: it is openserve having issues again. Ont is red for fibre link.

 

[Syk]

No Internet again.... FFS

 

[Grynne]

Same here from Cool Ideas. Westville KZN.

 

[VegOtter]

Same here from Cool Ideas. Westville KZN.

Same area as me. You also on openserve. Guessing they must be having issues... Again.

 

[wingnut771]

ok on vuma trenched durban.

 

[Vernon]

Lost connection since about a half hour ago. Possible Vuma outage?

 

[VegOtter]

Hey @AfriMan , @AfriFella , @AfriGuy
Why has PUBG latency stayed absolutely terrible even after the cables have been fixed? Some nights the pings are actually worse on the fixed cables than it was when you guys were on SEACOM. Every other european service runs perfectly fine at 170-180ms, but PUBG barely manages 200ms.

This is on Openserve, Durban.

 

[cavedog]

Hey @AfriMan
Why has PUBG latency stayed absolutely terrible even after the cables have been fixed? Some nights the pings are actually worse on the fixed cables than it was when you guys were on SEACOM. Every other european service runs perfectly fine at 170-180ms, but PUBG barely manages 200ms.

This is on Openserve, Durban.

Some traffic is going via WACS and other Seacom. So if you use a european looking glass you will see incoming traffic is with Seacom still.

So what is happening in your case because you are from KZN the traffic goes to JHB to CPT to EU. Those ones would give you 200ms.

Other EU locations will go over Seacom cable giving you the lower latency.

 

[VegOtter]

Some traffic is going via WACS and other Seacom. So if you use a european looking glass you will see incoming traffic is with Seacom still.

So what is happening in your case because you are from KZN the traffic goes to JHB to CPT to EU. Those ones would give you 200ms.

Other EU locations will go over Seacom cable giving you the lower latency.

Thanks for the insight, appreciate it.

Yeah, but it is either congested or really badly routed. Those tests were during off-peak. In the evenings and now it sits around 240-250ms, which is terrible. Before the whole cable break debacle my ping would never push past 190 even during peak times.
I got a test account from CoolIdeas and the latency is pegged at 180.

 

[cavedog]

Thanks for the insight, appreciate it.

Yeah, but it is either congested or really badly routed. Those tests were during off-peak. In the evenings and now it sits around 240-250ms, which is terrible. Before the whole cable break debacle my ping would never push past 190 even during peak times.
I got a test account from CoolIdeas and the latency is pegged at 180.

Yeah I know patiently waiting for them to switch back to their Telkom transit for incoming data. Maybe then the latency will stabilize.

 

[cavedog]

TRACEROUTE:

traceroute to 169.1.226.93 (169.1.226.93), 15 hops max, 60 byte packets

 1  Blizzard Blizzard  0.603 ms  0.590 ms  0.590 ms
 2  37.244.24.3 (37.244.24.3)  1.917 ms  1.944 ms  1.948 ms
 3  Blizzard Blizzard  1.434 ms  1.470 ms  1.577 ms
 4  137.221.66.44 (137.221.66.44)  1.435 ms  1.552 ms  1.559 ms
 5  137.221.78.68 (137.221.78.68)  1.920 ms  1.921 ms  1.921 ms
 6  137.221.78.32 (137.221.78.32)  1.224 ms  1.249 ms  1.231 ms
 7  seacom.equinix-am1.nl-ix.net (193.239.117.234)  2.402 ms  2.407 ms  2.815 ms
 8  ae-5-0.er-01-ams.nl.seacomnet.com (105.16.9.13)  171.481 ms  171.521 ms  171.528 ms
 9  xe-0-1-0-7.cr-01-lhr.uk.seacomnet.com (105.16.13.205)  169.111 ms  169.156 ms  167.898 ms
10  xe-0-7-0-1.cr-01-cpt.za.seacomnet.com (105.16.14.13)  178.874 ms  176.672 ms  175.661 ms
11  xe-1-0-0-0.er-01-cpt.za.seacomnet.com (105.16.31.9)  175.312 ms  175.603 ms  175.583 ms
12  105.22.67.102 (105.22.67.102)  219.058 ms  218.915 ms  218.848 ms
13  vlan1222.terjhb-igw2.net.echosp.link (102.67.176.10)  216.432 ms  207.700 ms  207.659 ms
14  * * *
15  * * *


23/02/2020 16:34:39 UTC
--------------------

This is the issue with latency. Traffic is incoming via Seacom and outgoing via Telkom. Should be sorted one they switch back to Telkom transit for both up and down traffic.

 

[wingnut771]

TRACEROUTE:

traceroute to 169.1.226.93 (169.1.226.93), 15 hops max, 60 byte packets

1  Blizzard Blizzard  0.603 ms  0.590 ms  0.590 ms
2  37.244.24.3 (37.244.24.3)  1.917 ms  1.944 ms  1.948 ms
3  Blizzard Blizzard  1.434 ms  1.470 ms  1.577 ms
4  137.221.66.44 (137.221.66.44)  1.435 ms  1.552 ms  1.559 ms
5  137.221.78.68 (137.221.78.68)  1.920 ms  1.921 ms  1.921 ms
6  137.221.78.32 (137.221.78.32)  1.224 ms  1.249 ms  1.231 ms
7  seacom.equinix-am1.nl-ix.net (193.239.117.234)  2.402 ms  2.407 ms  2.815 ms
8  ae-5-0.er-01-ams.nl.seacomnet.com (105.16.9.13)  171.481 ms  171.521 ms  171.528 ms
9  xe-0-1-0-7.cr-01-lhr.uk.seacomnet.com (105.16.13.205)  169.111 ms  169.156 ms  167.898 ms
10  xe-0-7-0-1.cr-01-cpt.za.seacomnet.com (105.16.14.13)  178.874 ms  176.672 ms  175.661 ms
11  xe-1-0-0-0.er-01-cpt.za.seacomnet.com (105.16.31.9)  175.312 ms  175.603 ms  175.583 ms
12  105.22.67.102 (105.22.67.102)  219.058 ms  218.915 ms  218.848 ms
13  vlan1222.terjhb-igw2.net.echosp.link (102.67.176.10)  216.432 ms  207.700 ms  207.659 ms
14  * * *
15  * * *


23/02/2020 16:34:39 UTC
--------------------

This is the issue with latency. Traffic is incoming via Seacom and outgoing via Telkom. Should be sorted one they switch back to Telkom transit for both up and down traffic.

why do i see angola cables on blizzard reverse trace?

 

[cavedog]

why do i see angola cables on blizzard reverse trace?

Because they also have some Angola Cables transit on certain routes. It would depend what server you were using.

 

[WaltonsZA]

With Vumatel 100/10 and internet has been extremely unstable with latency even after the cable has been fix. Also getting like only 2.5Mbps download to a servers in EU. Just want my 180ms+ back.

 

[cavedog]

Just ordered Frogfoot for my sisters house in KZN. Hope all these complaints about poor speed on Frogfoot won't affect them. Vodacom fibre has been waiting for 1 and half month no installation so let's try Afrihost and Frogfoot KZN