MWEB Uncapped ADSL Feedback - Part 3

You need to get one, plug it in and listen for noise. If it isn't crystal clear, or if you have no dial tone, you have a line fault. Which is great, because then you can report it direct to Telkom, and they seem to give priority to voice line faults. Once these are resolved, ADSL issues normally resolve too. [...]

+1
 
We are still offline. 18 days and counting... How long is this supposed to go on like this? MWeb calls me every day (or I call them), telling me that there was a technician assigned but nobody knows when exactly the problem will be solved. I hear these excuses for two weeks already and the situation is still the same: my internet is not working.


Hi

I checked your account and I see that a consultant has contacted you this morning with the latest update on the fault.
I will ask the team to get some more info regarding when the tech will attend to this.
 
Results:
Download Speed: 1132 kbps (141.5 KB/sec transfer rate)
Upload Speed: 337 kbps (42.1 KB/sec transfer rate)
Latency: 451 ms
Jitter: 84 ms
2014/07/21, 5:29:21 PM

Nice Download speed. If only it was reflected during normal usage. Latency makes it seem really REALLY slow.

Mweb Guy can add that to my open fault if he wants :P
Mweb are great with the communication.
Telkom still can't tell me anything, but Mweb tell me my fault will be fixed by the end of the week.

Don't let Telkom make MWEB look bad. Make sure its your ISP before you blame your ISP.

Hi

Thanks for the info, I will update the log with the latest results as per your request.
Hopefully this will be resolved soon. ;)
 
Was out of the house pretty early so I didn't have time to check. On startup I couldn't connect at all. The DNS setting was in Automatic from ISP. Once I changed my DNS to 8.8.8.8 some packets came trickling in. Painfully slow.

Hi

Please let me know if the connection has improved.
 
You need to get one, plug it in and listen for noise. If it isn't crystal clear, or if you have no dial tone, you have a line fault. Which is great, because then you can report it direct to Telkom, and they seem to give priority to voice line faults. Once these are resolved, ADSL issues normally resolve too.

Your problem must be with Telkom, as you are probably aware.

Thanks for the tip. but I won't buy a phone only to check if there is a line fault. It's not my job to be honest. I am paying for a service which is not delivered at the moment. As I rent the line from MWEB they need to make sure that the problem is solved asap and urge Telkom to do something about the faulty line. They obivously do that but nothing happens nevertheless. There was a technician at my place on Friday. So Telkom should know what the problem is. After the technician has left, ADSL worked (slow but it worked) but since Saturday I am offline again...

Besides, I am also in contact with Telkom and call them every day. They say they are working on it. So what can I do except following up and complaining with MWEB and Telkom every day so that finally someone attends to the problem?!

Hi

I checked your account and I see that a consultant has contacted you this morning with the latest update on the fault.
I will ask the team to get some more info regarding when the tech will attend to this.

Thanks! A consultant has contacted me and told me that there are no news regarding the fault. I was told that a tech would attend to this but that MWEB did not know when. Obviously not today. I hope that this issue is resolved soon.
 
Last edited:
Hi

Please let me know if the connection has improved.

Only marginally. If I load at the right moment a page will load very fast and then suddenly nothing until it times out. Would post the speed test results but I can't get it to complete (though it stops at around 0.02 Mbps down)
 
Thanks for the tip. but I won't buy a phone only to check if there is a line fault. It's not my job to be honest. I am paying for a service which is not delivered at the moment. As I rent the line from MWEB they need to make sure that the problem is solved asap and urge Telkom to do something about the faulty line. They obivously do that but nothing happens nevertheless. There was a technician at my place on Friday. So Telkom should know what the problem is. After the technician has left, ADSL worked (slow but it worked) but since Saturday I am offline again...

Besides, I am also in contact with Telkom and call them every day. They say they are working on it. So what can I do except following up and complaining with MWEB and Telkom every day so that finally someone attends to the problem?!

Understand your frustration, but what I'm saying is that when they know it's a voice line fault, higher priority is given. So it might be worth the R99 for a cheapo phone. Can be useful in the future.
 
It's called shaping. I've been on this road for months with Mweb. My account claims i'm not throttled. Yet speeds of around 60kb per second is very common.
 
Understand your frustration, but what I'm saying is that when they know it's a voice line fault, higher priority is given. So it might be worth the R99 for a cheapo phone. Can be useful in the future.

+1

But using voice on a landline is so retro...
 
It's called shaping. I've been on this road for months with Mweb. My account claims i'm not throttled. Yet speeds of around 60kb per second is very common.

Hi Napalm

Shaping:

Shaping is aimed at traffic classes as a whole whereas throttling is aimed at specific users who generate above average usage.

Throttling:

Throttling is a bandwidth management practice to manage Internet traffic – a user’s connection speed may be reduced based on usage patterns and usage history
 
Hey,

I can't see how much wifi data I am getting on your website. It just says uncapped, but I thought that is only on the MWEB and FON networks. Do I get uncapped on AlwaysOn also?
 
And here we go again. This is getting pathetic now, every couple of bloody days

Mweb

C:\Users\Andre>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=138ms TTL=119
Reply from 196.2.63.110: bytes=32 time=135ms TTL=119
Reply from 196.2.63.110: bytes=32 time=133ms TTL=119
Reply from 196.2.63.110: bytes=32 time=147ms TTL=119

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 133ms, Maximum = 147ms, Average = 138ms

C:\Users\Andre>tracert mweb.co.za

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 98 ms 98 ms 97 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 108 ms 110 ms 104 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 142 ms 141 ms 139 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
5 164 ms 125 ms 125 ms 196.28.178.66
6 181 ms 140 ms 141 ms cte-core-sw2.vwol.net [196.41.144.35]
7 145 ms 146 ms 146 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Vox

C:\Users\Andre>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=41ms TTL=119
Reply from 196.2.63.110: bytes=32 time=40ms TTL=119
Reply from 196.2.63.110: bytes=32 time=40ms TTL=119
Reply from 196.2.63.110: bytes=32 time=39ms TTL=119

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 41ms, Average = 40ms

C:\Users\Andre>tracert mweb.co.za

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms dsl-197-245-30-1.voxdsl.co.za [197.245.30.1]
2 17 ms 17 ms 17 ms 196.41.25.6
3 18 ms 19 ms 19 ms 196.41.25.12
4 17 ms 18 ms 17 ms mweb.jb1.napafrica.net [196.46.25.145]
5 41 ms 42 ms 43 ms tengig-0-7-0-3-vic-p-2.mweb.co.za [197.80.7.98]

6 42 ms 43 ms 43 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]

7 38 ms 37 ms 37 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 38 ms 38 ms 37 ms 196.28.178.66
9 53 ms 39 ms 40 ms cte-core-sw2.vwol.net [196.41.144.35]
10 50 ms 56 ms 54 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
And here we go again. This is getting pathetic now, every couple of bloody days

Mweb



Vox

Have you tried keeping your Vox/another account connected for a couple of days, instead of your MWEB one?

Because connecting to another account is similar to a port reset which could explain why your latency goes back to normal when connecting to another account, as in the Vox case above.
 
And here we go again. This is getting pathetic now, every couple of bloody days

Mweb



Vox

Hi

I have just checked the account and it seems ok.
I can't see anything in the account that would cause this problem.
When this happens again, please do a speed test also on both ISP accounts.
If possible, include an international trace route and I will log this matter with our specialist so that they may call you.
 
The last time it happened with Mweb I had another account connected for 3 or 4 days and no issues. I have also switched back to the Mweb and it has the same crud while 3 other accounts carry on just fine so dunno where the 'port reset' theory comes in.
 
The last time it happened with Mweb I had another account connected for 3 or 4 days and no issues. I have also switched back to the Mweb and it has the same crud while 3 other accounts carry on just fine so dunno where the 'port reset' theory comes in.

I suggest keeping one of the other accounts in your router, and rather dialing up to MWEB on each PC as you need it. This would be a good way to test. Past performance cannot be a measure of the current or future.
 
Hi MWEB Guy

Sorry to bother again but my connection is still not working properly. It is hampering my ability to work from home since I can't get a stable VPN connection to the office.

Right now I am doing an SVN update that should be almost instantaneous but is trickling through in bytes per second on average (large spans of 0 Bytes/second interspersed by brief bursts of data. I tread to sync my emails earlier and it was not pretty.

What should I do?
 
Hi

I checked your account and I see that a consultant has contacted you this morning with the latest update on the fault.
I will ask the team to get some more info regarding when the tech will attend to this.

There were two technicians at my place this morning but the problem could only be solved temporarily. They brought their own router, connected it and got a (slow but steady) connection. So the problem is my router. At least that is what they concluded. After doing a reset with my router I was online again. I told them that I tried several resets before and that this did not help –*or only temporarily. But they would not listen and were gone.

When I came home from work I wasn't surprised that the internet was down again... IF this is because of my router it should work with another one. Luckily I still got the brand new MWEB Fon router in the original packaging. So I connected the Fon router and what a surprise: Same problem as with my good one year old TP-LINK router. I got a ADSL signal but internet is so slow that I can't access one single website and can't perform a speed test.

What now MWEB Guy? Looks like not only my router but also the brand new Fon router is broken... :p
 
Top
Sign up to the MyBroadband newsletter
X