MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Getting the same problem. Connects but then nothing downloads. Proceeded to disconnect and reconnect.This cycle repeats itself over and over
 
MWEB Guy said:
Afternoon Kimbo, what speeds are you obtaining?
Click to expand...

Hi MWEB Guy

Everything else is fine, just NNTP is dead like "mors dood"

Test conducted on 08 April 2013 03:20:16 PM
Download Speed: 871 kbps (108.9 KB/sec transfer rate)
Upload Speed: 416 kbps (52 KB/sec transfer rate)
Latency: 61 ms
 
MWEB Guy said:
Afternoon Mephisto_Helix, we cannot replicate the problem with the news server and we are testing from Cape Town.

Please change your username realm to @dslmweb.co.za and let me know if it makes any difference. (I put protected access back on as well).


Are you testing the MWEB news servers?
Click to expand...

Realm changed, no difference ....... I only have Mwebs servers.

It is just dead dead dead. I have even tried different aged articles and it's the same problem. Browsing is fine, gaming is fine but downloads are officially dead.
 
I had a connection for a minute, at a whopping 20kbps but it's gone again
 
Success ....... everyone try change your realm and then change it back to default again.
 
kimbo said:
Hi MWEB Guy

Everything else is fine, just NNTP is dead like "mors dood"

Test conducted on 08 April 2013 03:20:16 PM
Download Speed: 871 kbps (108.9 KB/sec transfer rate)
Upload Speed: 416 kbps (52 KB/sec transfer rate)
Latency: 61 ms
Click to expand...

The NNTP you are referring to. Where are you downloading from?
 
Ok so it's been fine most of the day in GW2 but as soon as 5pm hits, WHAM the high latency is back.

Here are two traceroutes done at about 4PM and one now.

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

1 2 ms 2 ms <1 ms 192.168.0.1
2 12 ms 11 ms 12 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 17 ms 16 ms 15 ms 197-84-8-10.cpt.mweb.co.za [197.84.8.10]
4 16 ms 16 ms 15 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 192 ms 190 ms 191 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178.113]
6 195 ms 194 ms 189 ms 197-84-4-32.cpt.mweb.co.za [197.84.4.32]
7 164 ms 166 ms 164 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
8 162 ms 163 ms 160 ms 176.67.177.131
9 168 ms 160 ms 166 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
10 171 ms 171 ms 173 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166.153]
11 209 ms 208 ms 208 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
12 185 ms 172 ms 170 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
13 175 ms 172 ms 171 ms ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]
14 207 ms 208 ms 207 ms ae-4-90.edge6.Frankfurt1.Level3.net [4.69.154.202]
15 208 ms 206 ms 207 ms 195.16.161.58
16 200 ms 208 ms 201 ms 206-127-157-86.plaync.com [206.127.157.86]
17 203 ms 202 ms 202 ms 206-127-157-102.plaync.com [206.127.157.102]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.

Trace complete.

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

1 1 ms 1 ms 1 ms 192.168.0.1
2 474 ms 496 ms 527 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 593 ms 616 ms 629 ms 197-84-8-10.cpt.mweb.co.za [197.84.8.10]
4 594 ms 537 ms 515 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 577 ms 557 ms 614 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178.113]
6 641 ms 663 ms 706 ms 197-84-4-32.cpt.mweb.co.za [197.84.4.32]
7 373 ms 357 ms 323 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
8 376 ms 350 ms 415 ms 176.67.177.131
9 261 ms 322 ms 355 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
10 409 ms 401 ms 387 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166.153]
11 421 ms 387 ms 444 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
12 482 ms 436 ms 426 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
13 412 ms 413 ms 443 ms ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]
14 430 ms 396 ms 449 ms ae-4-90.edge6.Frankfurt1.Level3.net [4.69.154.202]
15 384 ms 361 ms 313 ms 195.16.161.58
16 318 ms 285 ms 263 ms 206-127-157-86.plaync.com [206.127.157.86]
17 316 ms 315 ms 340 ms 206-127-157-102.plaync.com [206.127.157.102]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.

I find it hard to believe that the exchange goes from being fine all day and then it magically gets hit with every user in the Southern Suburbs at precisely 5pm.
 
StevenC said:
Ok so it's been fine most of the day in GW2 but as soon as 5pm hits, WHAM the high latency is back.

Here are two traceroutes done at about 4PM and one now.

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

1 2 ms 2 ms <1 ms 192.168.0.1
2 12 ms 11 ms 12 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 17 ms 16 ms 15 ms 197-84-8-10.cpt.mweb.co.za [197.84.8.10]
4 16 ms 16 ms 15 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 192 ms 190 ms 191 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178.113]
6 195 ms 194 ms 189 ms 197-84-4-32.cpt.mweb.co.za [197.84.4.32]
7 164 ms 166 ms 164 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
8 162 ms 163 ms 160 ms 176.67.177.131
9 168 ms 160 ms 166 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
10 171 ms 171 ms 173 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166.153]
11 209 ms 208 ms 208 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
12 185 ms 172 ms 170 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
13 175 ms 172 ms 171 ms ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]
14 207 ms 208 ms 207 ms ae-4-90.edge6.Frankfurt1.Level3.net [4.69.154.202]
15 208 ms 206 ms 207 ms 195.16.161.58
16 200 ms 208 ms 201 ms 206-127-157-86.plaync.com [206.127.157.86]
17 203 ms 202 ms 202 ms 206-127-157-102.plaync.com [206.127.157.102]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.

Trace complete.

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

1 1 ms 1 ms 1 ms 192.168.0.1
2 474 ms 496 ms 527 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 593 ms 616 ms 629 ms 197-84-8-10.cpt.mweb.co.za [197.84.8.10]
4 594 ms 537 ms 515 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 577 ms 557 ms 614 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178.113]
6 641 ms 663 ms 706 ms 197-84-4-32.cpt.mweb.co.za [197.84.4.32]
7 373 ms 357 ms 323 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
8 376 ms 350 ms 415 ms 176.67.177.131
9 261 ms 322 ms 355 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
10 409 ms 401 ms 387 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166.153]
11 421 ms 387 ms 444 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
12 482 ms 436 ms 426 ms ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.186]
13 412 ms 413 ms 443 ms ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]
14 430 ms 396 ms 449 ms ae-4-90.edge6.Frankfurt1.Level3.net [4.69.154.202]
15 384 ms 361 ms 313 ms 195.16.161.58
16 318 ms 285 ms 263 ms 206-127-157-86.plaync.com [206.127.157.86]
17 316 ms 315 ms 340 ms 206-127-157-102.plaync.com [206.127.157.102]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.

I find it hard to believe that the exchange goes from being fine all day and then it magically gets hit with every user in the Southern Suburbs at precisely 5pm.
Click to expand...

Good evening, this is standard symptoms for a congested exchange.

If you live in a residential area, it makes sense that latencies increase at or after 5PM. Majority of us work till 4pm or 5pm.

Have you referred this to Telkom as yet?
 
Problem is that from your first couple hops it's very high, indicating a borked exchange :/
 
MWEB Guy said:
Good evening, this is standard symptoms for a congested exchange.

If you live in a residential area, it makes sense that latencies increase at or after 5PM. Majority of us work till 4pm or 5pm.

Have you referred this to Telkom as yet?
Click to expand...

Do you have any tips on how to do this? I phone the usual 10210 (iirc) but the technicians love doing the "you must phone this department" run around which leads me back to the place I called first. Then they deny any problem on the exchange. How would I get this information across to them in a manner that shows them I know what the problem is and no number of port resets would do it? :P
 
StevenC said:
Do you have any tips on how to do this? I phone the usual 10210 (iirc) but the technicians love doing the "you must phone this department" run around which leads me back to the place I called first. Then they deny any problem on the exchange. How would I get this information across to them in a manner that shows them I know what the problem is and no number of port resets would do it? :P
Click to expand...

I would suggest requesting to speak to a manager.

They should be able to provide you an email address where you can send your proof to.

I would also add speed test results before and after 5pm.
 
MWEB Guy said:
I would suggest requesting to speak to a manager.

They should be able to provide you an email address where you can send your proof to.

I would also add speed test results before and after 5pm.
Click to expand...

Failing that, occupy your nearest Telkom shop. Go armed with pre- and post 5pm traceroutes and speedtests. [-]Threaten grievous bodily harm.[/-] Demand to speak to the manager.
 
Thanks for the advice guys :)

I think I shall go brandish some weapons in a Telkom shop :)
 
Mortiiy said:
I am now in my cancellation notification month, awaiting the final debit and reversal..... not very promising from the looks of it.
If this reversal does not occur timely, I sure as hell gonna release a **** storm!!! BS like this is not needed.....
Click to expand...

You and me both :)
 
oober said:
I submitted my cancellation form on the 28th and they did not reply whether it is correct and when it will be cancelled. I assume it is correct and if they bill me at the end of the month I will just go to the bank and dispute the debit order.
Click to expand...

Same problem. I phoned (actually the wife did). When we asked for a reference # we were told "Just use my name" .... no doubt some temp that will not be working for MWEB next week. Big business sucks toads ... not my style but it's what it is.

AXXESS, AFRIHOST, RSAWEB, etc, etc, are but blips on the big game radar... I've bailed out. No more. Please, please wise up brothers and sisters and do the same.
 
Just given this thread 5 *****'s - people need to know.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X