MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
It doesn't matter. Streaming problem will never be fixed. I will cancel my account at the end of this month. I'm tired of being screwed around. Right now, MWEB is no longer the best ISP in SA.
 
Mweb is definitely throttling us. from yesterday only getting 100kb on all types of downloads. It's f***** up. I see why everyone is leaving them
 
It's really hilarious and lame at the same time that my most recent speedtest.net result is excellent -_-
 
Was just on Youtube and it streamed perfectly. Am downloading at 450+kb/s (on 4Mb) at the moment which is the highest speed I've had in ages. Something got fixed somewhere and I'm grateful, thank you.
 
Saskue said:
Mweb is definitely throttling us. from yesterday only getting 100kb on all types of downloads. It's f***** up. I see why everyone is leaving them
Click to expand...

I have replied to your inbox message with a test i would like you to run.

This will assist me in getting to the bottom of this issue.
 
MWEB Guy said:
Morning StevenC

From the traceroute results provided, the 2nd hop is very high. This points to congestion. I know you mentioned you contacted Telkom and they confirmed the exchange is not congested, but the results show otherwise.

Have you provided them these results? Also, when you do a traceroute test during the day, what does the results look like?
Click to expand...

After the port reset yesterday, it was fine the whole day (11ms to about 20ms which I tested at intervals). Latency was the expected 200ms and my experience yesterday was the best I have seen in months. Sadly, come the evening and it's gone to hell. I will be at home on Sunday afternoon and Monday all day, I will perform necessary tests then.

Traceroute from now coming in:

Tracing route to 206-127-146-50.plaync.com [206.127.146.50]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.0.1
2 166 ms 152 ms 144 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 73 ms 69 ms 71 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190]
4 129 ms 107 ms 94 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 227 ms 240 ms 227 ms TenGigE0-7-0-2.12.cpt-p-2.mweb.co.za [196.28.178.114]
6 * * 307 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 251 ms 217 ms 231 ms 176.67.177.131
8 345 ms 360 ms 395 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 390 ms 388 ms 411 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166.153]
10 450 ms 473 ms * ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
11 443 ms 464 ms 526 ms ae-24-24.ebr2.Frankfurt1.Level3.net [4.69.148.198]
12 436 ms 430 ms * ae-72-72.csw2.Frankfurt1.Level3.net [4.69.140.22]
13 * * * Request timed out.
14 363 ms 380 ms 363 ms 195.16.161.58
15 425 ms 439 ms 487 ms 206-127-157-86.plaync.com [206.127.157.86]
16 478 ms 468 ms 458 ms 206-127-157-102.plaync.com [206.127.157.102]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.

That 3rd hop being lower than the 2nd hop - is that possible?

Edit: Now that I am actually trying to play, this is the worst lag I have experienced since the SEACOM troubles began.
 
Last edited:
Its never ending, slow, slow, slow, and all we always get asked to do is reset router, pinging this, tracert this. Log onto different ISP, and everything is flying again. It took 10mins to download a 65kb definition update for Microsoft Serucity Essentials, and this is on a 4MB line. Will be cancelling on Monday, sick of these continual issues.
 
Hi MWEB guy,
been having issues on my 4mb uncapped since the Seacom incident. Switching between @dslmweb.co.za and @dsl512two.co.za seems to resolve it every now and then, but the problem returns after awhile.
Speedtest.net results seems to be OK but still having packet drops.
No issues when using my Webafrica or Afrihost accounts.

Ping statistics for 173.194.34.191:
Packets: Sent = 468, Received = 379, Lost = 89 (19% loss),
Approximate round trip times in milli-seconds:
Minimum = 155ms, Maximum = 706ms, Average = 164ms

Tracing route to google.co.uk [173.194.34.120]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 10 ms 9 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 13 ms 12 ms 12 ms 197-84-8-10.cpt.mweb.co.za [197.84.8.10]
4 13 ms 13 ms 12 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 161 ms 162 ms 174 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 164 ms 157 ms 163 ms 197-84-4-33.cpt.mweb.co.za [197.84.4.33]
7 198 ms 195 ms 199 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
8 161 ms 164 ms 162 ms 176.67.177.131
9 170 ms 162 ms * 176.67.177.133
10 * 161 ms 167 ms 176.67.177.255
11 166 ms 175 ms 166 ms 209.85.240.63
12 157 ms 158 ms 157 ms 209.85.253.47
13 163 ms 160 ms * lhr14s20-in-f24.1e100.net [173.194.34.120]
14 167 ms 163 ms 159 ms lhr14s20-in-f24.1e100.net [173.194.34.120]

Trace complete.
 
Last edited:
After the Seacom troubles, the speeds were once again what it should be, but youtube and general streaming is slow as hell as of tonight. Is their a problem with the Mweb's network or could it be that my local Telkom exchange is just congested?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X