Afrihost - Pure Fibre Feedback Thread

Status
Not open for further replies.
Ok I'll do that. But let me ask you something since you didn't bring it up even once, even though I mentioned it several times.

How is it possible that I can still have a fully working but apparently "cancelled" CISP line and yet have Afrihost tell me in the Client Zone that my AH Fibre line is "active"? Two Fibre lines on one ONT. It shouldn't be possible. Correct?
So then doesn't that tell you that there's a screw up somewhere at VUMA?

Most definitely, this is why I suggested a phone call so that we can clear this mess as quickly as possible.
 
100%.... tested 1000/100 Pure Fibre Account...

View attachment 697499

Previous results with CISP 200/200 and Vox 200/200...
https://mybroadband.co.za/forum/threads/cool-ideas-fibre-isp-feedback.793061/page-518#post-22382977

https://mybroadband.co.za/forum/threads/cool-ideas-fibre-isp-feedback.793061/page-518#post-22383037

Trying to find the tests I did on Home-connect 1000/100 but I don't think I did any, which is disappointing...
Not bad at all compared to your test from last year and the year before. :D
 
up to 2.5MB/s but still yoyo, even the ping is yoyo, i'll post a shot now now.
Can we test this issue using a faster line? Please drop me a PM with your clientzone username if you are keen on this.
 
@AfriFella @AfriMan would the Vuma fibre break affect Openserve clients?

I would think not however, my speeds have dropped to 1Mbps on 100Mbps line

8495444294.png

Wired connection
 
Last edited:
The latency is the first clue that something is wrong. Maybe a trace route to 8.8.8.8 or 1.1.1.1 to see where the latency is coming from.

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 43 ms 44 ms 44 ms dbn-up1.ip.adsl.co.za [.]
4 45 ms 42 ms 43 ms 169-1-21-122.ip.afrihost.co.za []
5 44 ms 42 ms 43 ms dbn-in1.ip.adsl.co.za []
6 51 ms 52 ms 52 ms vlan1131.terjhb-igw1.net.echosp.link []
7 51 ms 52 ms 52 ms 169-1-5-243.ip.afrihost.co.za []
8 53 ms 52 ms 52 ms 74.125.245.193
9 * 52 ms 52 ms 172.253.65.253
10 52 ms 53 ms 52 ms dns.google [8.8.8.8]
 
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 43 ms 44 ms 44 ms dbn-up1.ip.adsl.co.za [.]
4 45 ms 42 ms 43 ms 169-1-21-122.ip.afrihost.co.za []
5 44 ms 42 ms 43 ms dbn-in1.ip.adsl.co.za []
6 51 ms 52 ms 52 ms vlan1131.terjhb-igw1.net.echosp.link []
7 51 ms 52 ms 52 ms 169-1-5-243.ip.afrihost.co.za []
8 53 ms 52 ms 52 ms 74.125.245.193
9 * 52 ms 52 ms 172.253.65.253
10 52 ms 53 ms 52 ms dns.google [8.8.8.8]

Do you have a spare account to test? Looks like an ipc issue. If it's on Openserve side changing ISPs won't fix it obviously. That would probably be best to know who to point the finger at.
 
Do you have a spare account to test? Looks like an ipc issue. If it's on Openserve side changing ISPs won't fix it obviously. That would probably be best to know who to point the finger at.

VOX
8495535474.png


Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 43 ms 43 ms * 41.193.72.125
4 42 ms 43 ms 43 ms 41.193.72.126
5 42 ms 44 ms 44 ms 41.193.72.132
6 44 ms 43 ms 43 ms 41.193.72.98
7 51 ms 52 ms 53 ms 41.193.72.142
8 53 ms 52 ms 53 ms 41.193.119.106
9 54 ms 52 ms 52 ms 72.14.220.136
10 57 ms 53 ms 52 ms 74.125.245.209
11 52 ms 53 ms 52 ms 172.253.65.255
12 54 ms 53 ms 51 ms dns.google [8.8.8.8]

Trace complete.
 
VOX
8495535474.png


Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 43 ms 43 ms * 41.193.72.125
4 42 ms 43 ms 43 ms 41.193.72.126
5 42 ms 44 ms 44 ms 41.193.72.132
6 44 ms 43 ms 43 ms 41.193.72.98
7 51 ms 52 ms 53 ms 41.193.72.142
8 53 ms 52 ms 53 ms 41.193.119.106
9 54 ms 52 ms 52 ms 72.14.220.136
10 57 ms 53 ms 52 ms 74.125.245.209
11 52 ms 53 ms 52 ms 172.253.65.255
12 54 ms 53 ms 51 ms dns.google [8.8.8.8]

Trace complete.

Openserve outage or issue
 
@AfriFella @AfriGuy

Hi please see twitch tracert, speedtest is perfect - cant stream higher than 180p without buffering

Tracing route to twitch.map.fastly.net [151.101.122.167]
over a maximum of 30 hops:

1 3 ms 2 ms <1 ms 192.168.0.1
2 116 ms 104 ms 120 ms 102-182-112-1.ip.afrihost.co.za [102.182.112.1]
3 62 ms 138 ms 164 ms 169-1-21-201.ip.afrihost.co.za [169.1.21.201]
4 64 ms 45 ms 110 ms 77.246.59.84.liquidtelecom.net [77.246.59.84]
5 257 ms 275 ms 295 ms te-0-0-0-15.luk-p1-tho.liquidtelecom.net [5.11.10.220]
6 156 ms 158 ms 154 ms be-3.luk-pe1-tho.liquidtelecom.net [5.11.10.103]
7 154 ms 150 ms 154 ms xe-0-0-10-2.a01.londen12.uk.bb.gin.ntt.net [83.231.146.209]
8 158 ms 160 ms 222 ms ae-7.r05.londen12.uk.bb.gin.ntt.net [129.250.2.184]
9 155 ms 156 ms 158 ms ae-8.r25.londen12.uk.bb.gin.ntt.net [129.250.4.246]
10 163 ms 160 ms 157 ms ae-3.r02.parsfr02.fr.bb.gin.ntt.net [129.250.4.25]
11 162 ms 162 ms 164 ms 185.84.18.246
12 161 ms 166 ms 163 ms 151.101.122.167

Trace complete.


Tracing route to twitch.map.fastly.net [151.101.122.167]
over a maximum of 30 hops:

1 <1 ms 4 ms 2 ms 192.168.0.1
2 9 ms 11 ms * 102-182-112-1.ip.afrihost.co.za [102.182.112.1]
3 18 ms 7 ms 9 ms 169-1-21-201.ip.afrihost.co.za [169.1.21.201]
4 7 ms 8 ms 11 ms 77.246.59.84.liquidtelecom.net [77.246.59.84]
5 159 ms 156 ms 155 ms te-0-0-0-15.luk-p1-tho.liquidtelecom.net [5.11.10.220]
6 159 ms 159 ms * be-3.luk-pe1-tho.liquidtelecom.net [5.11.10.103]
7 154 ms 155 ms 155 ms xe-0-0-10-2.a01.londen12.uk.bb.gin.ntt.net [83.231.146.209]
8 159 ms 159 ms 159 ms ae-7.r05.londen12.uk.bb.gin.ntt.net [129.250.2.184]
9 157 ms 155 ms 157 ms ae-8.r25.londen12.uk.bb.gin.ntt.net [129.250.4.246]
10 158 ms 159 ms 158 ms ae-3.r02.parsfr02.fr.bb.gin.ntt.net [129.250.4.25]
11 165 ms 165 ms 165 ms 185.84.18.246
12 166 ms 162 ms 164 ms 151.101.122.167

Trace complete.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X