This thread seems to have moved away from Q&A for the MWEB rep to a more discussive thread, so I am hoping the MWEB reps still monitor this thread. If so, I have a question or three:
Dear MWEB,
In previous posts MWEB stated that it has two bandwidth pools. Are these pools linked at all or is it a matter of pool A = priority traffic and pool B = all other traffic? Although possibly more difficult to implement, my feeling is that dynamic bandwidth allocation would be the optimum way to utilize the available bandwidth as it would appear that at the moment the shaping on the non-priority pool is done through a scheduling system (see earlier posted graphs showing how shaping decreases in set percentages based on time). At the rate people (heavy downloading users) are dropping the MWEB service on this thread alone, I can only imagine that MWEB's total BW pool is underutilized.
Also, given that EASSy will be operational end of June, could you please give us some indication of whether MWEB have purchased bandwidth on that cable or not?
And what is MWEB doing as an end-user service provider to prevent that effect of these outages, that sadly have become the stigma to the MWEB reputation, are mitigated/prevented/minimized in the future?
Kind regards,
Malaia
FYI: for those who read the reports on how Neotel outages were the actual blame for previous MWEB lost capacity, Neotel is the South African Telecommuncations subsidiary of Tata...if their cars are anything to go by it is really no surprize that they only aim to do the bare minimum...just a thought