ISP cash cow
Executive Member
it's a cloudflare issue where they have disabled all sa cdn's mixed with kuk liquidtelecom route, vpn (to get off liquid) should sort you out.
where did you run the vpn from?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
it's a cloudflare issue where they have disabled all sa cdn's mixed with kuk liquidtelecom route, vpn (to get off liquid) should sort you out.
from sa, but don't have one anymore but am considering getting a year's sub off ebay. they're dirt cheap, like $5, I prefer expressvpn over nordvpn from past experience.where did you run the vpn from?
from sa, but don't have one anymore but am considering getting a year's sub off ebay. they're dirt cheap, like $5, I prefer expressvpn over nordvpn from past experience.
Yeah I have a couple of VPN accounts but did you just have it running still as Country: South Africa City:Jhb and it sorted the issue out?
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.Afrihost - I honestly don't know who else to talk to anymore between your call centre and Vumatel.
I have probably spoken to over 15 different agents - all promising to get back to me and to personally take it upon them to sort out the issue with the install as "this is not how you guys do business"
In Summary:
After placing an order for fibre on the 3rd of September (a simple migration of ISP services) (Fibre been running no issue for two years, previous flatmate left and took router) I still today do not have this connection up and running.
The router arrived on the 11th of September - at the time afrihost had placed an order with Vumatel for a "NEW FIBRE INSTALL" - Not sure why - definitely specified for migration of services - but anyways called Vumatel and asked them to change this to a migration. The next day all is apparently configured from Vumatel - ONT CONFIG is updated with new MAC address and we're ready to go.
Wrong - Popped in the D-LINK Router (configured obviously) and all we have is a"Failed to get an IP Address from the DHCP Server"
Confirm the next day again with AFRIHOST and VUMATEL that all CONFIG in terms of FSAN and MAC addressing is setup and done correctly to which both parties assure me that all is configured correctly.
I continue to call AFRIHOST pretty much everyday trying to get this sorted - most operators telling me that I need to go to https://clientzone.afrihost.com/fibre-activate/ etc. etc. which can be a little difficult if you don't actually have an IP address to get there. Both parties keep blaming each other saying the problem lies of the other end seeing as everything is up and running correctly on their end.
Got through to at least one guy who said this is extremely strange as he can see the DHCP server keeps returning invalid IP assignment (afihost side) - eventually told me he is going to escalate this to the network engineers as something strange is going on - still waiting for that escalation.
Another operator told me the ONT is now broken and that Vumatel is going to come and replace it. Still waiting on that one as well.
On Sunday another operator told me that he has seen a problem on their end but needs to be in contact with Vuma to fix this and it will be done first thing in morning after which he will give me a call to confirm that the problem has now been corrected. Yeah still waiting on that one as well.
In short it is now the 24th of September - I've had the router for nearly two weeks with a line that up & running yet cannot even get an IP Address to "Activate" this wonderful line.
Afrihost could you please come and collect your ROUTER? As I think I'll be going somewhere else?
I see under "Cancel this service" there is a reason stating "Installation was a nightmare" - well this wasn't just a nightmare - it's an absolute **** show and the only thing it's done for me was bring my Airtime balance to a near 0 after having to call these clowns most days trying to get this **** sorted. -478/10 - Can't recommend.
Afrihost - I honestly don't know who else to talk to anymore between your call centre and Vumatel.
I have probably spoken to over 15 different agents - all promising to get back to me and to personally take it upon them to sort out the issue with the install as "this is not how you guys do business"
In Summary:
After placing an order for fibre on the 3rd of September (a simple migration of ISP services) (Fibre been running no issue for two years, previous flatmate left and took router) I still today do not have this connection up and running.
The router arrived on the 11th of September - at the time afrihost had placed an order with Vumatel for a "NEW FIBRE INSTALL" - Not sure why - definitely specified for migration of services - but anyways called Vumatel and asked them to change this to a migration. The next day all is apparently configured from Vumatel - ONT CONFIG is updated with new MAC address and we're ready to go.
Wrong - Popped in the D-LINK Router (configured obviously) and all we have is a"Failed to get an IP Address from the DHCP Server"
Confirm the next day again with AFRIHOST and VUMATEL that all CONFIG in terms of FSAN and MAC addressing is setup and done correctly to which both parties assure me that all is configured correctly.
I continue to call AFRIHOST pretty much everyday trying to get this sorted - most operators telling me that I need to go to https://clientzone.afrihost.com/fibre-activate/ etc. etc. which can be a little difficult if you don't actually have an IP address to get there. Both parties keep blaming each other saying the problem lies of the other end seeing as everything is up and running correctly on their end.
Got through to at least one guy who said this is extremely strange as he can see the DHCP server keeps returning invalid IP assignment (afihost side) - eventually told me he is going to escalate this to the network engineers as something strange is going on - still waiting for that escalation.
Another operator told me the ONT is now broken and that Vumatel is going to come and replace it. Still waiting on that one as well.
On Sunday another operator told me that he has seen a problem on their end but needs to be in contact with Vuma to fix this and it will be done first thing in morning after which he will give me a call to confirm that the problem has now been corrected. Yeah still waiting on that one as well.
In short it is now the 24th of September - I've had the router for nearly two weeks with a line that up & running yet cannot even get an IP Address to "Activate" this wonderful line.
Afrihost could you please come and collect your ROUTER? As I think I'll be going somewhere else?
I see under "Cancel this service" there is a reason stating "Installation was a nightmare" - well this wasn't just a nightmare - it's an absolute **** show and the only thing it's done for me was bring my Airtime balance to a near 0 after having to call these clowns most days trying to get this **** sorted. -478/10 - Can't recommend.
I see there are some routing issues mentioned here - can anyone tell me if this is still happening?
AH:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter.Dlink - 0 | 213 | 213 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| cpt-rx2.ip.adsl.co.za - 0 | 213 | 213 | 2 | 3 | 10 | 3 |
| cpt-net1.ip.adsl.co.za - 0 | 213 | 213 | 2 | 2 | 7 | 2 |
| be-22.lza-pe1-cpt.liquidtelecom.net - 0 | 213 | 213 | 2 | 2 | 5 | 3 |
|Te-0-3-0-11.lza-p3-jhb.liquidtelecom.net - 0 | 213 | 213 | 176 | 177 | 182 | 178 |
| xe-0-1-3.lfr-pe2-mrs.liquidtelecom.net - 0 | 213 | 213 | 177 | 179 | 242 | 177 |
|et-7-0-0-u100.cr-polaris.fra1.bb.godaddy.com - 0 | 213 | 213 | 195 | 196 | 216 | 195 |
| ae0.cr-antares.fra10.bb.godaddy.com - 0 | 213 | 213 | 195 | 197 | 226 | 196 |
| ae0.cr-vega.sxb1.bb.godaddy.com - 0 | 213 | 213 | 196 | 198 | 215 | 196 |
| gw-heg.curie.router.fr.velia.net - 0 | 213 | 213 | 196 | 201 | 250 | 198 |
| sxb24acA.strasbourg.fr.velia.net - 0 | 213 | 213 | 198 | 205 | 282 | 199 |
| 185.136.166.85 - 0 | 213 | 213 | 197 | 199 | 207 | 199 |
|________________________________________________|______|______|______|______|______|______|
NordVPN:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.8.8.1 - 0 | 7 | 7 | 146 | 146 | 147 | 147 |
| Packet was too big. - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| ae2.31-rt1-cr.ldn.as25369.net - 0 | 7 | 7 | 146 | 146 | 148 | 146 |
| ae1.rt0-thn.ldn.as25369.net - 0 | 7 | 7 | 146 | 147 | 150 | 146 |
| be4021.ccr22.lon01.atlas.cogentco.com - 0 | 7 | 7 | 146 | 147 | 149 | 148 |
| be2869.ccr42.lon13.atlas.cogentco.com - 0 | 7 | 7 | 147 | 147 | 149 | 147 |
| be12489.ccr42.par01.atlas.cogentco.com - 0 | 7 | 7 | 154 | 155 | 156 | 155 |
| be3545.rcr21.sxb01.atlas.cogentco.com - 0 | 7 | 7 | 161 | 162 | 163 | 162 |
|be2781.nr14.b015623-2.sxb01.atlas.cogentco.com - 0 | 7 | 7 | 162 | 162 | 163 | 163 |
| ae7.cr-nunki.sxb1.core.heg.com - 0 | 7 | 7 | 161 | 163 | 165 | 165 |
| gw-heg.newton.router.fr.velia.net - 0 | 7 | 7 | 163 | 166 | 170 | 163 |
| sxb24acA.strasbourg.fr.velia.net - 0 | 7 | 7 | 162 | 163 | 165 | 163 |
| 185.136.166.85 - 0 | 7 | 7 | 161 | 161 | 163 | 161 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Heres a test from this evening:
Code:AH: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | dlinkrouter.Dlink - 0 | 213 | 213 | 0 | 0 | 1 | 0 | | No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 | | cpt-rx2.ip.adsl.co.za - 0 | 213 | 213 | 2 | 3 | 10 | 3 | | cpt-net1.ip.adsl.co.za - 0 | 213 | 213 | 2 | 2 | 7 | 2 | | be-22.lza-pe1-cpt.liquidtelecom.net - 0 | 213 | 213 | 2 | 2 | 5 | 3 | |Te-0-3-0-11.lza-p3-jhb.liquidtelecom.net - 0 | 213 | 213 | 176 | 177 | 182 | 178 | | xe-0-1-3.lfr-pe2-mrs.liquidtelecom.net - 0 | 213 | 213 | 177 | 179 | 242 | 177 | |et-7-0-0-u100.cr-polaris.fra1.bb.godaddy.com - 0 | 213 | 213 | 195 | 196 | 216 | 195 | | ae0.cr-antares.fra10.bb.godaddy.com - 0 | 213 | 213 | 195 | 197 | 226 | 196 | | ae0.cr-vega.sxb1.bb.godaddy.com - 0 | 213 | 213 | 196 | 198 | 215 | 196 | | gw-heg.curie.router.fr.velia.net - 0 | 213 | 213 | 196 | 201 | 250 | 198 | | sxb24acA.strasbourg.fr.velia.net - 0 | 213 | 213 | 198 | 205 | 282 | 199 | | 185.136.166.85 - 0 | 213 | 213 | 197 | 199 | 207 | 199 | |________________________________________________|______|______|______|______|______|______| NordVPN: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 10.8.8.1 - 0 | 7 | 7 | 146 | 146 | 147 | 147 | | Packet was too big. - 100 | 7 | 0 | 0 | 0 | 0 | 0 | | ae2.31-rt1-cr.ldn.as25369.net - 0 | 7 | 7 | 146 | 146 | 148 | 146 | | ae1.rt0-thn.ldn.as25369.net - 0 | 7 | 7 | 146 | 147 | 150 | 146 | | be4021.ccr22.lon01.atlas.cogentco.com - 0 | 7 | 7 | 146 | 147 | 149 | 148 | | be2869.ccr42.lon13.atlas.cogentco.com - 0 | 7 | 7 | 147 | 147 | 149 | 147 | | be12489.ccr42.par01.atlas.cogentco.com - 0 | 7 | 7 | 154 | 155 | 156 | 155 | | be3545.rcr21.sxb01.atlas.cogentco.com - 0 | 7 | 7 | 161 | 162 | 163 | 162 | |be2781.nr14.b015623-2.sxb01.atlas.cogentco.com - 0 | 7 | 7 | 162 | 162 | 163 | 163 | | ae7.cr-nunki.sxb1.core.heg.com - 0 | 7 | 7 | 161 | 163 | 165 | 165 | | gw-heg.newton.router.fr.velia.net - 0 | 7 | 7 | 163 | 166 | 170 | 163 | | sxb24acA.strasbourg.fr.velia.net - 0 | 7 | 7 | 162 | 163 | 165 | 163 | | 185.136.166.85 - 0 | 7 | 7 | 161 | 161 | 163 | 161 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
he is talking about kuk eu ping going on for months, now you change the subject and start talking about cloudflare, no wonder it's taking so long.Checked with our NOC team. They confirm we've logged a ticket with Cloudflare cos we're getting similar routing issues to our own website.
Can't officially speak for others sites getting similar issues but it's likely to be the same cause.
My best guess is that Cloudflare are rerouting some local sites to global nodes because there is something happening with local nodes.
he is talking about kuk eu ping going on for months, now you change the subject and start talking about cloudflare, no wonder it's taking so long.
Confusing, cos I was picking up on the Cloudflare conversation.
Our network manager is looking at the routing and to see what can be changed - I think I did mention this a few posts back. I did say up front that it was going to be a long process. Things are definitely moving, so I am sure we'll get a positive result.
not if you bothered looking at his tracerts.Confusing, cos I was picking up on the Cloudflare conversation.
Our network manager is looking at the routing and to see what can be changed - I think I did mention this a few posts back. I did say up front that it was going to be a long process. Things are definitely moving, so I am sure we'll get a positive result.
Hi @AfriMan. Still waiting for assistance to sign up.?
