Afterhours shaping on MWEB uncapped account.

Zyraz said:
Latency is back , didnt even manage one full game before lag started again.
Click to expand...

I have been keeping track of this and I have kept our specialists informed.
 
No call from technical yet.
Issue continues unfortunately.
 
Zyraz said:
No call from technical yet.
Issue continues unfortunately.
Click to expand...

They have a number of calls already scheduled. I will try and move the escalation forward however, I can not guarantee that they will be able to move your callback forward.

Regards MWEB Guy
 
MWEB Guy said:
They have a number of calls already scheduled. I will try and move the escalation forward however, I can not guarantee that they will be able to move your callback forward.

Regards MWEB Guy
Click to expand...

No problem , I understand .
Thanks anyways.
 
Regular timeouts.
>ping mweb.co.za -t

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=451ms TTL=122
Reply from 196.2.63.110: bytes=32 time=648ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=457ms TTL=122
Request timed out.
Request timed out.
Reply from 196.2.63.110: bytes=32 time=366ms TTL=122
Reply from 196.2.63.110: bytes=32 time=358ms TTL=122
Reply from 196.2.63.110: bytes=32 time=386ms TTL=122
Reply from 196.2.63.110: bytes=32 time=392ms TTL=122
Reply from 196.2.63.110: bytes=32 time=455ms TTL=122
Reply from 196.2.63.110: bytes=32 time=472ms TTL=122
Reply from 196.2.63.110: bytes=32 time=463ms TTL=122
Reply from 196.2.63.110: bytes=32 time=482ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=405ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=465ms TTL=122
Reply from 196.2.63.110: bytes=32 time=474ms TTL=122
Reply from 196.2.63.110: bytes=32 time=505ms TTL=122
Reply from 196.2.63.110: bytes=32 time=538ms TTL=122
Reply from 196.2.63.110: bytes=32 time=601ms TTL=122
Reply from 196.2.63.110: bytes=32 time=497ms TTL=122
Reply from 196.2.63.110: bytes=32 time=591ms TTL=122
Reply from 196.2.63.110: bytes=32 time=544ms TTL=122
Reply from 196.2.63.110: bytes=32 time=552ms TTL=122
Reply from 196.2.63.110: bytes=32 time=493ms TTL=122
Reply from 196.2.63.110: bytes=32 time=539ms TTL=122
Reply from 196.2.63.110: bytes=32 time=681ms TTL=122
Reply from 196.2.63.110: bytes=32 time=692ms TTL=122
Reply from 196.2.63.110: bytes=32 time=578ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=409ms TTL=122
Reply from 196.2.63.110: bytes=32 time=438ms TTL=122
Reply from 196.2.63.110: bytes=32 time=469ms TTL=122
Reply from 196.2.63.110: bytes=32 time=566ms TTL=122
Reply from 196.2.63.110: bytes=32 time=526ms TTL=122
Reply from 196.2.63.110: bytes=32 time=540ms TTL=122
Reply from 196.2.63.110: bytes=32 time=518ms TTL=122
Reply from 196.2.63.110: bytes=32 time=774ms TTL=122
Reply from 196.2.63.110: bytes=32 time=569ms TTL=122
Reply from 196.2.63.110: bytes=32 time=944ms TTL=122
Reply from 196.2.63.110: bytes=32 time=576ms TTL=122
Reply from 196.2.63.110: bytes=32 time=628ms TTL=122
Request timed out.
Request timed out.
Request timed out.
Reply from 196.2.63.110: bytes=32 time=711ms TTL=122
Reply from 196.2.63.110: bytes=32 time=520ms TTL=122
Reply from 196.2.63.110: bytes=32 time=423ms TTL=122
Reply from 196.2.63.110: bytes=32 time=378ms TTL=122
Reply from 196.2.63.110: bytes=32 time=413ms TTL=122
Reply from 196.2.63.110: bytes=32 time=400ms TTL=122
Reply from 196.2.63.110: bytes=32 time=419ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 54, Received = 45, Lost = 9 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 358ms, Maximum = 944ms, Average = 517ms
Click to expand...
 
Stable blow 30ms ping now. Off to attempt some gaming , hope its last ...

<Edit> ... better but it didnt last /cry
from 20ms to 400ms spikes and occassional timeouts.
 
Last edited:
Okay so a telkom tech pitched up after i logged a call more than two weeks ago...
I asked telkom to please let us know when they are coming through because we are working people.
They failed to do so and hence i had to correspond with them telephonically , added to that the tech was very rude after i asked why I was not called before he came to investigate the problem as i requested.

Well the response to the problem was very short . He basically told me that there was nothing he could do because Im not the only one with this problem.
When I asked him to expand on this , he replied that my degrading in latency is down to oversold exchange.
I asked him to put it in writing and he refused.
I asked him what i should do from here and the reply was that I must live the problem .
I asked him whether his superiors were aware of the problem since lots of people were apparently complaining (and have been for months according to the tech).
He said yes they were aware of the problem and have been for a while.
I asked if telkom is gonna be resolving this issue at some stage and i was told that is currently no plans to address this issue.

I was basically told to either live with the problem or move to a wireless service.

Now i have questions for Mwebguy ...
Is there anything i can do ?
Will moving my line over to mweb help in resolving this problem ?
Will hellopeter , carte blanche ,emailing Helen Zilla, phoning telkom and throwing my toys out the cot help in anyways or am I stuck with this problem forever ?
 
Last edited:
Zyraz said:
Okay so a telkom tech pitched up after i logged a call more than two weeks ago...
I asked telkom to please let us know when they are coming through because we are working people.
They failed to do so and hence i had to correspond with them telephonically , added to that the tech was very rude after i asked why I was not called before he came to investigate the problem as i requested.

Well the response to the problem was very short . He basically told me that there was nothing he could do because Im not the only one with this problem.
When I asked him to expand on this , he replied that my degrading in latency is down to oversold exchange.
I asked him to put it in writing and he refused.
I asked him what i should do from here and the reply was that I must live the problem .
I asked him whether his superiors were aware of the problem since lots of people were apparently complaining (and have been for months according to the tech).
He said yes they were aware of the problem and have been for a while.
I asked if telkom is gonna be resolving this issue at some stage and i was told that is currently no plans to address this issue.

I was basically told to either live with the problem or move to a wireless service.

Now i have questions for Mwebguy ...
Is there anything i can do ?
Will moving my line over to mweb help in resolving this problem ?
Will hellopeter , carte blanche ,emailing Helen Zilla, phoning telkom and throwing my toys out the cot help in anyways or am I stuck with this problem forever ?
Click to expand...

Hi Zyraz,

You'll have to take it up with Telkom until hopefully they decide to upgrade the congested exchange. Moving the line to MWEB won't make a difference as you'll still be in the same exchange.

It's Telkom's infrastructure.


MWEB Guy
 
MWEB Guy said:
Hi Zyraz,

You'll have to take it up with Telkom until hopefully they decide to upgrade the congested exchange. Moving the line to MWEB won't make a difference as you'll still be in the same exchange.

It's Telkom's infrastructure.


MWEB Guy
Click to expand...

Another question if I may ... would upgrading to a faster line from 1 Mb to 4 Mb help ? Logic says no because Im not really having problems with speed but complaining about latency ?

Have I got any grounds to turn this problem and refusal to rectify it from telkom into a legal battle ?
 
Zyraz said:
Another question if I may ... would upgrading to a faster line from 1 Mb to 4 Mb help ? Logic says no because Im not really having problems with speed but complaining about latency ?

Have I got any grounds to turn this problem and refusal to rectify it from telkom into a legal battle ?
Click to expand...

I don't think that upgrading your line speed will make a differance as it is the line that is currently at fault.

Regards
MWEB Guy
 
MWEB Guy said:
I don't think that upgrading your line speed will make a differance as it is the line that is currently at fault.

Regards
MWEB Guy
Click to expand...

Do I have any legal rights to force them to fix this issue or do i just have to accept that once again because of telkom`s monopoly they can get away with just telling me to live with it ?

Just for interest sake , if LLU went through would there be more that could be done than just accept the problem and live with it ?
 
Zyraz said:
Do I have any legal rights to force them to fix this issue or do i just have to accept that once again because of telkom`s monopoly they can get away with just telling me to live with it ?

Just for interest sake , if LLU went through would there be more that could be done than just accept the problem and live with it ?
Click to expand...

I don't believe you have any legal right unfortunately however, I have noticed that Telkom sometimes responds to customer persistence.

Regards
MWEB Guy
 
MWEB Guy said:
I don't believe you have any legal right unfortunately however, I have noticed that Telkom sometimes responds to customer persistence.

Regards
MWEB Guy
Click to expand...

Time to actually use the telephone line i get forced to pay for but never use...
Guess ill add an anolog telephone to my monthly shopping list.

Mwebguy , any rough idea how many of your customers sit with and have logged this same problem ?
10`s , 100`s , 1000`s , millions ?

It would be awesome if RPM or any other mod can do a survey/poll/article about this ...
 
Update 1/3/2012

Okay so a follow up status update...
Okay so line is now syncing at all. No line connectivity whatsoever. Logged a line fault last night , we will see how long this takes to get repaired.
I cant wait for LLU ...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X