Afrihost - Pure Fibre Feedback Thread

Status
Not open for further replies.
jadiwolv said:
Are you insinuating I am lying, wasting my time moaning on a forum (because i just am not getting any support)?

Jeez I feel sorry for the people that dont have access to this thread/Afri guys and have to resort to the support ticket system. It is really bad.
Click to expand...

Dude.. where in my response did I say that or insinuate that.
I’m on Vuma trenched and it’s working fine for me. At least the last time I checked. More information helps so they can track down your issue and assist you.
 
Pho3nix said:
Dude.. where in my response did I say that or insinuate that.
I’m on Vuma trenched and it’s working fine for me. At least the last time I checked. More information helps so they can track down your issue and assist you.
Click to expand...

Apologies.

Yeah i am on frogfoot trenched. Its not consistently bad, and i have tested everything even my router, different Ethernet cables. It must be their network.

I did not experience this on my previous 50/50mbps 100gb capped package. I upgraded to the pure fibre package (same line, same speed) and now twitch is not working.
 
Fjorko said:
Trace from my USG 1Gbps Network switch to 87.117.247.206 from Afrihost PF Account

traceroute to 87.117.247.206 (87.117.247.206), 30 hops max, 38 byte packets
1 USG (192.168.1.1) 0.818 ms 1.162 ms 1.259 ms
2 * * *
3 cpt-tx2.ip.adsl.co.za (169.1.5.81) 27.761 ms 27.283 ms 29.675 ms
4 cpt-rx1.ip.adsl.co.za (169.1.5.94) 37.889 ms 29.082 ms 29.152 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 22.696 ms 22.181 ms 28.719 ms
6 77.246.59.84.liquidtelecom.net (77.246.59.84) 29.289 ms 28.649 ms 30.863 ms
7 te-0-0-0-7.luk-p1-tho.liquidtelecom.net (5.11.10.156) 170.757 ms te-0-0-0-15.luk-p1-tho.liquidtelecom.net (5.11.10.220) 173.555 ms te-0-0-0-12.luk-p1-tho.liquidtelecom.net (5.11.10.222) 172.562 ms
8 be-3.luk-pe1-tho.liquidtelecom.net (5.11.10.103) 171.480 ms 177.372 ms 178.322 ms
9 xe-0-1-1.0.luk-pr3-tho.liquidtelecom.net (5.11.10.183) 186.645 ms 168.710 ms 5.11.10.95.liquidtelecom.net (5.11.10.95) 172.792 ms
10 be20.asr01.ld5.as20860.net (195.66.226.230) 167.440 ms 169.996 ms 164.667 ms
11 be10.asr02.dc5.as20860.net (130.180.202.47) 178.112 ms 179.436 ms 175.396 ms
12 po4-30.bor2.dc5.as20860.net (212.84.162.156) 181.474 ms 179.054 ms 181.854 ms
13 e1-41.lea101.1uf.dc5.as20860.net (212.84.179.89) 174.887 ms e1-42.lea101.1uf.dc5.as20860.net (212.84.180.249) 176.599 ms e1-41.lea101.1uf.dc5.as20860.net (212.84.179.89) 168.243 ms
14 87.117.247.1 (87.117.247.1) 168.618 ms 169.676 ms 168.569 ms
15 87.117.247.206 (87.117.247.206) 168.120 ms 169.961 ms 170.184 ms

Test to same server from CISP account from same device

traceroute to 87.117.247.206 (87.117.247.206), 30 hops max, 38 byte packets
1 USG (192.168.1.1) 1.556 ms 1.660 ms 2.057 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 23.954 ms 23.175 ms 22.840 ms
4 192.168.11.6 (192.168.11.6) 20.099 ms 26.908 ms 26.468 ms
5 uwx-cust.coolideas.co.za (154.0.4.161) 32.614 ms 32.671 ms 26.538 ms
6 uvu-cust.coolideas.co.za (154.0.4.122) 166.437 ms 168.303 ms 167.799 ms
7 u102-cust.coolideas.co.za (154.0.5.18) 173.939 ms 171.994 ms 172.248 ms
8 be20.asr01.thn.as20860.net (195.66.224.207) 173.670 ms 169.631 ms 166.810 ms
9 be10.asr01.dc5.as20860.net (130.180.202.45) 161.474 ms 162.965 ms 167.836 ms
10 po2-30.bor2.dc5.as20860.net (212.84.162.158) 175.599 ms 173.058 ms 175.324 ms
11 e1-42.lea101.1uf.dc5.as20860.net (212.84.180.249) 169.519 ms e1-46.lea201.north.dc5.as20860.net (212.84.188.10) 167.120 ms 167.083 ms
12 87.117.247.1 (87.117.247.1) 169.636 ms 167.370 ms 169.116 ms
13 87.117.247.206 (87.117.247.206) 169.389 ms 167.583 ms 174.808 ms

You can see Hop 11 ( AH ) and hop 9 ( CISP ) has a diffs of about 17ms. To a gamer i assume this is the difference between a headshot and a shot in $ass.
Click to expand...
i'm sure it's just the last hop you have to concentrate on, they both look pretty similar.
 
jadiwolv said:
Ditto. I am chatting privateley to @AfriFella for the past week supplying traceroutes upon traceroutes and looking here in the actual thread it seems like the same thing.

Is anything going to get done? I was told the latency on the last liquidtelecom hop shows a routing issue on their side. I am unable to stream twitch higher than 160p on 50/50mbps connection which is just unacceptable.
Click to expand...
my issue is only the luckypacket RD performance.
 
Loppas said:
@Fjorko Compare 151.106.5.253, 85.195.114.189 and 88.202.177.96
Click to expand...

CISP -> 151.106.5.253

traceroute to 151.106.5.253 (151.106.5.253), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.532 ms 0.516 ms 0.578 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 27.317 ms 21.279 ms 27.292 ms
4 192.168.11.6 (192.168.11.6) 20.603 ms 20.648 ms 20.477 ms
5 154.0.4.162 (154.0.4.162) 20.713 ms 20.488 ms 20.495 ms
6 usi-cust.coolideas.co.za (154.0.4.2) 159.884 ms 166.035 ms 160.066 ms
7 v1000.core1.lon3.he.net (216.66.80.169) 165.999 ms 165.808 ms 165.799 ms
8 100ge14-1.core1.lon2.he.net (184.105.64.237) 188.603 ms 188.389 ms 188.218 ms
9 ae1.cr-sargas.lon1.core.heg.com (195.66.225.173) 166.192 ms 171.716 ms 165.783 ms
10 ae0.cr-merak.lon5.bb.godaddy.com (87.230.113.
1) 166.473 ms 161.561 ms 161.943 ms
11 ae0.cr-nunki.sxb1.bb.godaddy.com (87.230.113.3) 180.800 ms 180.666 ms 174.455 ms
12 gw-heg.newton.router.fr.velia.net (87.230.112.15) 180.723 ms 180.104 ms 186.027 ms
13 sxb13ahB.strasbourg.fr.velia.net (134.119.212.3) 202.553 ms 176.232 ms 187.004 ms
14 151.106.5.253 (151.106.5.253) 178.596 ms 181.086 ms 174.870 ms

CISP -> 85.195.114.189

traceroute to 85.195.114.189 (85.195.114.189), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.530 ms 0.479 ms 0.564 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 20.329 ms 23.064 ms 30.097 ms
4 192.168.11.6 (192.168.11.6) 22.383 ms 28.261 ms 22.349 ms
5 154.0.4.162 (154.0.4.162) 28.277 ms 28.198 ms 28.195 ms
6 uvu-cust.coolideas.co.za (154.0.4.122) 173.477 ms 171.670 ms 165.671 ms
7 v1000.core1.lon3.he.net (216.66.80.169) 159.986 ms 159.610 ms 166.096 ms
8 100ge14-1.core1.lon2.he.net (184.105.64.237) 172.015 ms 171.764 ms 166.156 ms
9 ae1.cr-sargas.lon1.core.heg.com (195.66.225.173) 172.887 ms 172.702 ms 172.782 ms
10 ae9.cr-polaris.fra1.bb.godaddy.com (87.230.113.29) 176.682 ms 178.548 ms 178.276 ms
11 gw-heg.meitner.router.frankfurt.de.velia.net (87.230.115.5) 178.701 ms 173.960 ms 173.246 ms
12 dabuieg17.frankfurt.de.velia.net (85.195.113.12) 206.841 ms 225.975 ms 221.143 ms
13 85.195.114.189 (85.195.114.189) 178.474 ms 177.633 ms 183.300 ms

CISP -> 88.202.177.96

traceroute to 88.202.177.96 (88.202.177.96), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.504 ms 0.472 ms 0.537 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 28.157 ms 28.127 ms 22.022 ms
4 192.168.11.6 (192.168.11.6) 27.258 ms 21.310 ms 21.216 ms
5 154.0.4.162 (154.0.4.162) 21.409 ms 21.260 ms 21.103 ms
6 usi-cust.coolideas.co.za (154.0.4.2) 166.334 ms 160.979 ms 160.693 ms
7 u102-cust.coolideas.co.za (154.0.5.18) 172.811 ms 165.513 ms 165.437 ms
8 linx-224.as13213.net (195.66.224.19) 172.357 ms 172.445 ms 172.410 ms
9 te0-0-0-5.ccr22.lon01.atlas.cogentco.com (149.6.3.157) 171.847 ms 172.620 ms 172.231 ms
10 be2869.ccr42.lon13.atlas.cogentco.com (154.54.57.161) 172.269 ms 174.559 ms 179.127 ms
11 be12194.ccr41.ams03.atlas.cogentco.com (154.54.56.94) 177.952 ms be12488.ccr42.ams03.atlas.cogentco.com (130.117.51.42) 181.085 ms 177.382 ms
12 be3433.rcr21.ams06.atlas.cogentco.com (154.54.58.202) 171.921 ms 171.344 ms 179.014 ms
13 uk2.net.demarc.cogentco.com (149.14.92.130) 183.411 ms 175.781 ms 178.609 ms
14 10.125.4.7 (10.125.4.7) 172.769 ms 10.125.4.9 (10.125.4.9) 187.450 ms 167.837 ms
15 58cab160.setaptr.net (88.202.177.96) 179.302 ms 173.493 ms *

==================================

AH -> 151.106.5.253

traceroute to 151.106.5.253 (151.106.5.253), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.522 ms 0.482 ms 0.561 ms
2 * * *
3 cpt-tx2.ip.adsl.co.za (169.1.5.81) 31.435 ms 31.252 ms 31.332 ms
4 169-1-21-54.ip.afrihost.co.za (169.1.21.54) 33.566 ms 28.413 ms 28.341 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 22.116 ms 21.957 ms 21.769 ms
6 77.246.59.84.liquidtelecom.net (77.246.59.84) 29.742 ms 23.470 ms 29.818 ms
7 te-0-3-0-19.lza-p4-jhb.liquidtelecom.net (77.246.57.39) 200.648 ms te-0-3-0-7.lza-p4-jhb.liquidtelecom.net (41.60.135.94) 207.854 ms 208.283 ms
8 xe-0-1-5-0.lfr-pe2-mrs.liquidtelecom.net (46.17.232.25) 197.097 ms 202.706 ms te-0-1-0-2.lfr-pe1-mrs.liquidtelecom.net (5.11.10.252) 201.123 ms
9 et-7-0-0-u100.cr-polaris.fra1.core.heg.com (80.81.192.239) 218.088 ms 217.317 ms 214.987 ms
10 ae0.cr-antares.fra10.bb.godaddy.com (87.230.115.1) 221.306 ms 226.469 ms 225.170 ms
11 ae0.cr-vega.sxb1.bb.godaddy.com (87.230.115.3) 222.586 ms 231.200 ms 243.723 ms
12 gw-heg.curie.router.fr.velia.net (87.230.112.17) 215.853 ms 222.443 ms 221.781 ms
13 sxb13ahB.strasbourg.fr.velia.net (134.119.212.3) 226.264 ms 230.515 ms 227.239 ms
14 151.106.5.253 (151.106.5.253) 217.676 ms 216.379 ms 221.676 ms

AH -> 85.195.114.189

traceroute to 85.195.114.189 (85.195.114.189), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.527 ms 0.456 ms 0.550 ms
2 * * *
3 cpt-tx2.ip.adsl.co.za (169.1.5.81) 24.061 ms 28.681 ms 23.915 ms
4 cpt-rx1.ip.adsl.co.za (169.1.5.94) 34.615 ms 29.398 ms 34.245 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 29.279 ms 23.436 ms 28.989 ms
6 77.246.59.84.liquidtelecom.net (77.246.59.84) 29.397 ms 29.082 ms 28.913 ms
7 Te-0-3-0-11.lza-p3-jhb.liquidtelecom.net (77.246.57.37) 203.971 ms 211.657 ms 46.17.232.91 (46.17.232.91) 211.373 ms
8 te-0-1-0-2.lfr-pe1-mrs.liquidtelecom.net (5.11.10.252) 200.227 ms 192.535 ms 205.303 ms
9 et-7-0-0-u100.cr-polaris.fra1.core.heg.com (80.81.192.239) 220.674 ms 220.519 ms 219.096 ms
10 gw-heg.meitner.router.frankfurt.de.velia.net (87.230.115.5) 221.334 ms 225.141 ms 221.947 ms
11 dabuieg17.frankfurt.de.velia.net (85.195.113.12) 250.753 ms 233.452 ms 250.675 ms
12 85.195.114.189 (85.195.114.189) 219.203 ms 220.998 ms 215.576 ms

AH -> 88.202.177.96

traceroute to 88.202.177.96 (88.202.177.96), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.508 ms 0.498 ms 0.523 ms
2 * * *
3 cpt-tx2.ip.adsl.co.za (169.1.5.81) 23.675 ms 27.482 ms 23.613 ms
4 cpt-rx1.ip.adsl.co.za (169.1.5.94) 30.269 ms 33.613 ms 30.192 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 22.003 ms 28.259 ms 28.089 ms
6 77.246.59.84.liquidtelecom.net (77.246.59.84) 28.617 ms 23.405 ms 31.066 ms
7 te-0-2-0-16.luk-pe1-gsw.liquidtelecom.net (5.11.10.216) 179.073 ms te-0-2-0-17.luk-pe1-gsw.liquidtelecom.net (5.11.10.218) 174.761 ms te-0-3-0-5.luk-p1-tho.liquidtelecom.net (5.11.10.170) 163.752 ms
8 be-5.luk-pe1-tcy.liquidtelecom.net (5.11.10.191) 176.557 ms be-1.luk-pe1-tcy.liquidtelecom.net (5.11.10.189) 172.766 ms 170.678 ms
9 be5656.rcr21.b015534-1.lon01.atlas.cogentco.com (149.14.250.177) 179.483 ms 179.600 ms 174.765 ms
10 be2186.ccr22.lon01.atlas.cogentco.com (154.54.61.70) 177.989 ms be2185.ccr21.lon01.atlas.cogentco.com (154.54.61.62) 176.215 ms 165.746 ms
11 be2870.ccr41.lon13.atlas.cogentco.com (154.54.58.173) 182.945 ms be2869.ccr42.lon13.atlas.cogentco.com (154.54.57.161) 171.097 ms be2870.ccr41.lon13.atlas.cogentco.com (154.54.58.173) 178.223 ms
12 be12488.ccr42.ams03.atlas.cogentco.com (130.117.51.42) 182.775 ms 180.886 ms 177.044 ms
13 be3434.rcr21.ams06.atlas.cogentco.com (154.54.59.50) 180.096 ms 180.718 ms be3433.rcr21.ams06.atlas.cogentco.com (154.54.58.202) 179.675 ms
14 uk2.net.demarc.cogentco.com (149.14.92.58) 178.677 ms uk2.net.demarc.cogentco.com (149.14.92.130) 184.635 ms 184.548 ms
15 10.125.4.5 (10.125.4.5) 174.089 ms 10.125.4.7 (10.125.4.7) 184.568 ms 10.125.4.9 (10.125.4.9) 182.499 ms
16 58cab160.setaptr.net (88.202.177.96) 179.119 ms 179.142 ms *
 
shakes1 said:
So, is this an acknowledgement that there is an issue with poor wifi performance on the DIR825? Just clarifying...
Click to expand...
Even though my CC issue seems to be better, I do think the wifi performance of this router is a bit funky.

Connecting to it with my phone (Pixel 3a) is a mixed bag, sometimes the 2.4 or 5Ghz SSID's show up and dissapear at random if you look up the available networks, sometimes it doesn't want to connect automatically or when prompted or I struggle to switch between 2.4 and 5Ghz.

Will see if this persists on auto channel settings, as I'd like to continue using it considering it has AC wifi which my previous router does not and also can run at a higher Mbps rate on the 5Ghz band.
 
Latency is about 7ms between Amsterdam and London when I test it from my seedbox hosted in Amsterdam to Coreix.net in London.

So if Afrihost gives ~ 168ms to London then surely Amsterdam should be around 178ms or so. Liquid Telecom still has an issue with routing or maybe they are not at the right exchanges to produce the low latency because a ~25ms or so from London to Amsterdam means the connection is going to another country. Maybe via France.
 
cavedog said:
Latency is about 7ms between Amsterdam and London when I test it from my seedbox hosted in Amsterdam to Coreix.net in London.

So if Afrihost gives ~ 168ms to London then surely Amsterdam should be around 178ms or so. Liquid Telecom still has an issue with routing or maybe they are not at the right exchanges to produce the low latency because a ~25ms or so from London to Amsterdam means the connection is going to another country. Maybe via France.
Click to expand...
exactly what we are all saying, last month my ping to RD was in the 170's and is what is causing my issues.
 
wingnut771 said:
exactly what we are all saying, last month my ping to RD was in the 170's and is what is causing my issues.
Click to expand...

Give me a link to test my side. Your line seems like an issue or Vumatel handover issue on Afrihost side not sure but not latency related. Cybersmart has the worst latency to EU with 190ms to London but very stable and fast.
 
cavedog said:
Give me a link to test my side. Your line seems like an issue or Vumatel handover issue on Afrihost side not sure but not latency related. Cybersmart has the worst latency to EU with 190ms to London but very stable and fast.
Click to expand...
that's a seperate issue that happens on occasion so lets ignore that for now and just focus on RD performance.
 
cavedog said:
So if Afrihost gives ~ 168ms to London then surely Amsterdam should be around 178ms or so. Liquid Telecom still has an issue with routing or maybe they are not at the right exchanges to produce the low latency because a ~25ms or so from London to Amsterdam means the connection is going to another country. Maybe via France.
Click to expand...

It looks like its taking the east coast route (essay) to some places in eu and hence that is causing the higher latency. E.g. On forjko's trace to 85.195.114.189:

7 te-0-3-0-19.lza-p4-jhb.liquidtelecom.net (77.246.57.39) 200.648 ms te-0-3-0-7.lza-p4-jhb.liquidtelecom.net (41.60.135.94) 207.854 ms 208.283 ms
8 xe-0-1-5-0.lfr-pe2-mrs.liquidtelecom.net (46.17.232.25) 197.097 ms 202.706 ms te-0-1-0-2.lfr-pe1-mrs.liquidtelecom.net (5.11.10.252) 201.123 ms
9 et-7-0-0-u100.cr-polaris.fra1.core.heg.com (80.81.192.239) 218.088 ms 217.317 ms 214.987 ms
 
cavedog said:
Give me a link to test my side. Your line seems like an issue or Vumatel handover issue on Afrihost side not sure but not latency related. Cybersmart has the worst latency to EU with 190ms to London but very stable and fast.
Click to expand...
pm'd you but seems i can't post the link, as you have to be logged in.
 
cavedog said:
Give me a link to test my side. Your line seems like an issue or Vumatel handover issue on Afrihost side not sure but not latency related. Cybersmart has the worst latency to EU with 190ms to London but very stable and fast.
Click to expand...
702381
 
Loppas said:
It looks like its taking the east coast route (essay) to some places in eu and hence that is causing the higher latency. E.g. On forjko's trace to 85.195.114.189:

7 te-0-3-0-19.lza-p4-jhb.liquidtelecom.net (77.246.57.39) 200.648 ms te-0-3-0-7.lza-p4-jhb.liquidtelecom.net (41.60.135.94) 207.854 ms 208.283 ms
8 xe-0-1-5-0.lfr-pe2-mrs.liquidtelecom.net (46.17.232.25) 197.097 ms 202.706 ms te-0-1-0-2.lfr-pe1-mrs.liquidtelecom.net (5.11.10.252) 201.123 ms
9 et-7-0-0-u100.cr-polaris.fra1.core.heg.com (80.81.192.239) 218.088 ms 217.317 ms 214.987 ms
Click to expand...

I don't see 200ms+ on that IP. I get about 177ms

702391
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X