who.is.michael
Expert Member
For those that might be interested....
http://www.asasa.org.za/ResultDetail.aspx?Ruling=3768
Let me know when I can remove the document.
Regards
M
EDIT: TX Skepitc replaced the url with yours...
Before I get lashed; ...lash FCB South Africa, their ruling came first.
I was exhausted of calling / emailing iBurst daily and hearing the same old line about my MTU and my equipment or settings that are faulty. They just refused to openly communicate with their customers and still don't! Why no representation on this forum?
I’ve been paying them in excess of R 2 200 per month for services they advertise, which I couldn’t use.
Subsequently matters has changed and it seems they have decided to make bandwidth available once more in Cape Town, although shaped to death - as currently the network is showing a marked improved from the poor state it was in during April – June of this year.
Thanks ASASA - At least they rid us of suppliers using “up to” claims... Telkom also got nicked.
http://www.asasa.org.za/ResultDetail.aspx?Ruling=3767
http://www.asasa.org.za/ResultDetail.aspx?Ruling=3768
Let me know when I can remove the document.
Regards
M
EDIT: TX Skepitc replaced the url with yours...
Before I get lashed; ...lash FCB South Africa, their ruling came first.
I was exhausted of calling / emailing iBurst daily and hearing the same old line about my MTU and my equipment or settings that are faulty. They just refused to openly communicate with their customers and still don't! Why no representation on this forum?
I’ve been paying them in excess of R 2 200 per month for services they advertise, which I couldn’t use.
Subsequently matters has changed and it seems they have decided to make bandwidth available once more in Cape Town, although shaped to death - as currently the network is showing a marked improved from the poor state it was in during April – June of this year.
Thanks ASASA - At least they rid us of suppliers using “up to” claims... Telkom also got nicked.
http://www.asasa.org.za/ResultDetail.aspx?Ruling=3767
Last edited: