Seems like this was just another lie - your support staff confirmed today that the line has still not been migrated.
Line upgrade also still not done due to the above.
3 weeks and counting
@AfriMan
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Seems like this was just another lie - your support staff confirmed today that the line has still not been migrated.
Line upgrade also still not done due to the above.
3 weeks and counting
I (also from Durban) was on Openserve Home with Afrihost and had no problems. 1 September moved to Pure Fibre and immediately problems started. The routing is effed, packet loss is ridiculous and best of all is, I can't even log into my hosting at Afrihost (Axxess).also can't recommend them if you're in pinetown durban area on vuma trenched due to random hop 3 drops. still on going since i migrated on 1 aug, had no issue the previous 6 months with other isp's.
I (also from Durban) was on Openserve Home with Afrihost and had no problems. 1 September moved to Pure Fibre and immediately problems started. The routing is effed, packet loss is ridiculous and best of all is, I can't even log into my hosting at Afrihost (Axxess).
Can anyone recommend another ISP please. Sending a million emails and traceroutes has gotten nobody nowhere with Afrihost and I don't see it changing anytime soon or in the distant future. I cannot pay for something I cannot use.
Did you manage to get any feedback?I see quite a few posts in this regard. Let me check with our hardware manager - he might be able to get some direction from the distributor/manufacturer![]()
Did you manage to get any feedback?
His advice was to use the returns feature so we can send these units back to the manufacturer. Apparently this is not a general issue with the unit.
We are also issuing an updated model, so that might also eliminate the issue.
What the process for this?
Migrating my Fibre to Afrihost has been a bit of a nightmare. Wouldn't recommend it.
So now I'm stuck between my old ISP and Afrihost and wondering, will my Fibre die at the end of the month?
- First struggled to get my B number from my previous ISP. Not Afrihost's fault in any way but multiple calls and followups to finally get this information from my previous ISP.
- My previous ISP informed me that they released my line on the 6 September.
- Confirmed with Afrihost via a support ticket and they said they placed my Line Migration order. Should take aprox. 2 days I was told.
- Followed up on the 12th, 14th and 17th with NO feedback from Afrihost.
- On the 19th used Whatsapp Support and was informed that my line had been successfully migrated and that my router was ready for collection. Great news I thought.
- Collected my router at the offices on the 20th. Told the representative it still showed processing on the portal and was informed a supervisor just needs to link my B number and left with the expectation that it will be sorted.
- Nothing happened so followed up via Whatsapp again later on the 20th and was this time informed that in fact my line migration has not been completed and that my line was still locked by the previous operator. I need to follow up again with my previous ISP.
- After painfully again confirming with the previous ISP I got the information that the line was already released on the 6th already.
@AfriMan @AfriFella - Any advice?
no wonder i couldn't find "the button", thought i was blind, my router doesn't show in clientzone, only 3 huawei routers for lte:Can i exchange mine for the updated model ? I have not opened mine yet. It's still sitting there in the box. Do i just hit the "exchange" button ?
View attachment 717517

Can i exchange mine for the updated model ? I have not opened mine yet. It's still sitting there in the box. Do i just hit the "exchange" button ?
View attachment 717517
no wonder i couldn't find "the button", thought i was blind, my router doesn't show in clientzone, only 3 huawei routers for lte:
View attachment 717545

Yes @AfriMan they need to contact Liquid telecom. There is packet loss on their transit provider Liquid over Seacom. They need to reroute because EU traffic is suffering....
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter.Dlink - 0 | 41 | 41 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| cpt-rx2.ip.adsl.co.za - 0 | 41 | 41 | 2 | 3 | 5 | 3 |
| cpt-net1.ip.adsl.co.za - 0 | 41 | 41 | 2 | 2 | 4 | 2 |
| be-22.lza-pe1-cpt.liquidtelecom.net - 0 | 41 | 41 | 2 | 2 | 4 | 3 |
|te-0-2-0-17.luk-pe1-gsw.liquidtelecom.net - 0 | 41 | 41 | 142 | 142 | 144 | 143 |
| be-5.luk-pe1-tho.liquidtelecom.net - 0 | 41 | 41 | 142 | 142 | 144 | 143 |
| 5.11.8.145.liquidtelecom.net - 0 | 41 | 41 | 141 | 145 | 201 | 142 |
| 195.66.226.234 - 0 | 41 | 41 | 143 | 145 | 193 | 144 |
| ae1-br01-eqld5.as57976.net - 0 | 41 | 41 | 173 | 176 | 216 | 174 |
| et-0-0-2-br02-eqam1.as57976.net - 0 | 41 | 41 | 176 | 180 | 220 | 211 |
| et-0-0-67-pe02-eqam1.as57976.net - 0 | 41 | 41 | 176 | 180 | 229 | 177 |
| 185.60.112.157 - 0 | 41 | 41 | 176 | 177 | 179 | 177 |
|________________________________________________|______|______|______|______|______|______|
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter.Dlink - 0 | 51 | 51 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| cpt-rx2.ip.adsl.co.za - 0 | 51 | 51 | 2 | 3 | 8 | 5 |
| cpt-net1.ip.adsl.co.za - 0 | 51 | 51 | 2 | 2 | 4 | 3 |
| be-22.lza-pe1-cpt.liquidtelecom.net - 0 | 51 | 51 | 2 | 2 | 4 | 3 |
|te-0-2-0-10.lza-p3-jhb.liquidtelecom.net - 0 | 51 | 51 | 178 | 179 | 184 | 179 |
| xe-0-1-3.lfr-pe2-mrs.liquidtelecom.net - 0 | 51 | 51 | 177 | 180 | 230 | 178 |
|et-7-0-0-u100.cr-polaris.fra1.bb.godaddy.com - 0 | 51 | 51 | 195 | 196 | 201 | 195 |
| ae0.cr-antares.fra10.bb.godaddy.com - 0 | 51 | 51 | 195 | 197 | 229 | 195 |
| ae0.cr-vega.sxb1.bb.godaddy.com - 0 | 51 | 51 | 197 | 198 | 231 | 199 |
| gw-heg.curie.router.fr.velia.net - 0 | 51 | 51 | 195 | 196 | 217 | 196 |
| sxb24acA.strasbourg.fr.velia.net - 0 | 51 | 51 | 199 | 205 | 268 | 204 |
| 185.136.166.85 - 0 | 51 | 51 | 197 | 198 | 204 | 198 |
|________________________________________________|______|______|______|______|______|______|
Interesting, im not seeing the same packetloss here from cape town for some reason. Is it still ongoing on your end?
Code:|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | dlinkrouter.Dlink - 0 | 41 | 41 | 0 | 0 | 1 | 0 | | No response from host - 100 | 9 | 0 | 0 | 0 | 0 | 0 | | cpt-rx2.ip.adsl.co.za - 0 | 41 | 41 | 2 | 3 | 5 | 3 | | cpt-net1.ip.adsl.co.za - 0 | 41 | 41 | 2 | 2 | 4 | 2 | | be-22.lza-pe1-cpt.liquidtelecom.net - 0 | 41 | 41 | 2 | 2 | 4 | 3 | |te-0-2-0-17.luk-pe1-gsw.liquidtelecom.net - 0 | 41 | 41 | 142 | 142 | 144 | 143 | | be-5.luk-pe1-tho.liquidtelecom.net - 0 | 41 | 41 | 142 | 142 | 144 | 143 | | 5.11.8.145.liquidtelecom.net - 0 | 41 | 41 | 141 | 145 | 201 | 142 | | 195.66.226.234 - 0 | 41 | 41 | 143 | 145 | 193 | 144 | | ae1-br01-eqld5.as57976.net - 0 | 41 | 41 | 173 | 176 | 216 | 174 | | et-0-0-2-br02-eqam1.as57976.net - 0 | 41 | 41 | 176 | 180 | 220 | 211 | | et-0-0-67-pe02-eqam1.as57976.net - 0 | 41 | 41 | 176 | 180 | 229 | 177 | | 185.60.112.157 - 0 | 41 | 41 | 176 | 177 | 179 | 177 | |________________________________________________|______|______|______|______|______|______|
Edit: Nvm i see its a different route mine is taking.
Heres one over the seacom route:
Code:|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | dlinkrouter.Dlink - 0 | 51 | 51 | 0 | 0 | 1 | 0 | | No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 | | cpt-rx2.ip.adsl.co.za - 0 | 51 | 51 | 2 | 3 | 8 | 5 | | cpt-net1.ip.adsl.co.za - 0 | 51 | 51 | 2 | 2 | 4 | 3 | | be-22.lza-pe1-cpt.liquidtelecom.net - 0 | 51 | 51 | 2 | 2 | 4 | 3 | |te-0-2-0-10.lza-p3-jhb.liquidtelecom.net - 0 | 51 | 51 | 178 | 179 | 184 | 179 | | xe-0-1-3.lfr-pe2-mrs.liquidtelecom.net - 0 | 51 | 51 | 177 | 180 | 230 | 178 | |et-7-0-0-u100.cr-polaris.fra1.bb.godaddy.com - 0 | 51 | 51 | 195 | 196 | 201 | 195 | | ae0.cr-antares.fra10.bb.godaddy.com - 0 | 51 | 51 | 195 | 197 | 229 | 195 | | ae0.cr-vega.sxb1.bb.godaddy.com - 0 | 51 | 51 | 197 | 198 | 231 | 199 | | gw-heg.curie.router.fr.velia.net - 0 | 51 | 51 | 195 | 196 | 217 | 196 | | sxb24acA.strasbourg.fr.velia.net - 0 | 51 | 51 | 199 | 205 | 268 | 204 | | 185.136.166.85 - 0 | 51 | 51 | 197 | 198 | 204 | 198 | |________________________________________________|______|______|______|______|______|______|