MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Masataka said:
Getting the same here. Just loaded up a video, and immediate response with full line capacity.

The height of the shapping seems to come in around 8PM. Pretty blatant that it is happening on a schedule and not on actual usage.
Click to expand...

Maybe the "schedule" is just congestion at that time ;)
 
MWEB Guy said:
Hi

I have checked your account and I see numerous disconnects on the line for today alone.
Seems as though the connection is not vry stable and that would certainly have an impact on your connection.

I would advise having a fault logged for you line so Telkom could perhaps check if there's any noise on the line.
Click to expand...

We did have a problem on the line. Have had telkom out here. Had an intermittent adsl connection the last few days and noise on the phone line. All of which is now resolved.

Please advise what you can do to resolve the slow news server
 
Mr Feesh said:
We did have a problem on the line. Have had telkom out here. Had an intermittent adsl connection the last few days and noise on the phone line. All of which is now resolved.

Please advise what you can do to resolve the slow news server
Click to expand...

Hi Mr Feesh

With regards to the news server which is free, we have no problems with it and 200kb/s is a good speed taking into account it is a contended service. We have been transparent about our news server being a best effort and that speeds are not guaranteed on it.
 
Strange issues this side, at the office... I have a feeling its exchange congestion. I have now tested with Mweb, Axxess and even WebAfrica and all are equally iffy...

4mb line, 4mb Mweb Uncapped accout:


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

1 <1 ms <1 ms <1 ms 192.168.10.254
2 1733 ms 1374 ms 3537 ms 41-132-74-1.dsl.mweb.co.za [41.132.74.1]
3 1645 ms 3053 ms 354 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 1421 ms 221 ms 256 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 2469 ms 362 ms 109 ms 196.28.178.66
6 * * 1517 ms cte-core-sw2.vwol.net [196.41.144.35]
7 1097 ms * 1358 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

Intl Tracert:
Tracing route to cnn-56m.gslb.vgtf.net [157.166.249.11] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.10.254
2 2266 ms 1775 ms 2445 ms 41-132-74-1.dsl.mweb.co.za [41.132.74.1]
3 2490 ms 2581 ms 618 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 2006 ms * 2044 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 * 1392 ms 3540 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 237 ms 156 ms 159 ms 197-84-4-33.cpt.mweb.co.za [197.84.4.33]
7 2358 ms 431 ms 363 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
8 2445 ms 821 ms 385 ms 176.67.177.131
9 2780 ms 843 ms 1936 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
10 2101 ms 2091 ms 1726 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166.153]
11 431 ms 156 ms 2100 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
12 614 ms 1945 ms 1932 ms ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74]
13 2009 ms 2025 ms 243 ms ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50]
14 2011 ms 2624 ms 1998 ms ae-1-100.ebr1.Washington12.Level3.net [4.69.143.213]
15 2294 ms 598 ms 2273 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
16 490 ms 1956 ms 1813 ms ae-1-51.edge2.Atlanta4.Level3.net [4.69.150.17]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
Click to expand...

I called Telkom, they said that everything was OK. I called Mweb support earlier too but murphey's law, everything ran 100% fine while on the phone. Pings/speed/traces everything... 10 minutes later everything back down to what is showing in the above..

:cry:
 
Flidiot said:
Strange issues this side, at the office... I have a feeling its exchange congestion. I have now tested with Mweb, Axxess and even WebAfrica and all are equally iffy...

4mb line, 4mb Mweb Uncapped accout:


Local Tracert:


Intl Tracert:


I called Telkom, they said that everything was OK. I called Mweb support earlier too but murphey's law, everything ran 100% fine while on the phone. Pings/speed/traces everything... 10 minutes later everything back down to what is showing in the above..

:cry:
Click to expand...

Hi Flidiot

The results you provided points to the exchange being congested. Telkom will need to sort it out from their side. I suggest providing them with the traceroutes as well.
 
MWEB Guy said:
Hi Flidiot

The results you provided points to the exchange being congested. Telkom will need to sort it out from their side. I suggest providing them with the traceroutes as well.
Click to expand...

I thought that was the case... Don't usually like to point fingers at Telkom, but...Ok I am lying, I love to blame them. Just wanted to give them benefit of the doubt this time :erm:

Thanks for confirming MWEB Guy!
 
MWEB Guy said:
Hi Mr Feesh

With regards to the news server which is free, we have no problems with it and 200kb/s is a good speed taking into account it is a contended service. We have been transparent about our news server being a best effort and that speeds are not guaranteed on it.
Click to expand...

I understand that speeds are not guaranteed but can you confirm if any other users are experiencing slower speeds.
 
@mr mweb guy

I just DCed using mweb from diablo 3...

it is not nice.
it makes real life rage.
 
Mr Feesh said:
I understand that speeds are not guaranteed but can you confirm if any other users are experiencing slower speeds.
Click to expand...

Hi Mr Feesh
Has speeds improved when connecting to the news server?
 
Pr⊕phet said:
@mr mweb guy

I just DCed using mweb from diablo 3...

it is not nice.
it makes real life rage.
Click to expand...

Hi Pr⊕phet

I checked on our side and the current session is still active, the connection didn't drop on our side.
 
MWEB Guy said:
Hi Pr⊕phet

I checked on our side and the current session is still active, the connection didn't drop on our side.
Click to expand...

That's because I just reconnected. Getting PRTG now to monitor it, this is the second time it happens... I really suggest your gaming guy or whatever starts checking this out. It is already a huge issue over at AH and I pray mweb isn't going that route. Going to slit something...
 
packet loss indicating.

Code: 
C:\Windows\system32>pathping 80.239.210.89

Tracing route to 80-239-210-89.customer.teliacarrier.com [80.239.210.89]
over a maximum of 30 hops:
  0  JadeX64 [10.10.10.10]
  1  . [10.10.10.1]
  2  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
  3  197-80-4-210.jhb.mweb.co.za [197.80.4.210]
  4  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5  tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
  6  pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
  7  176.67.177.131
  8  xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
  9  vl-3504-ve-118.csw1.London1.Level3.net [4.69.166.141]
 10  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
 11  ldn-b5-link.telia.net [213.248.96.37]
 12  ldn-bb2-link.telia.net [80.91.249.181]
 13  hbg-bb2-link.telia.net [80.91.247.168]
 14  adm-bb4-link.telia.net [80.91.245.140]
 15  adm-b5-link.telia.net [80.91.253.186]
 16     *        *        *
Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           JadeX64 [10.10.10.10]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  . [10.10.10.1]
                                7/ 100 =  7%   |
  2   22ms     7/ 100 =  7%     0/ 100 =  0%  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
                                0/ 100 =  0%   |
  3   22ms     7/ 100 =  7%     0/ 100 =  0%  197-80-4-210.jhb.mweb.co.za [197.80.4.210]
                                0/ 100 =  0%   |
  4   22ms     7/ 100 =  7%     0/ 100 =  0%  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
                                1/ 100 =  1%   |
  5   25ms     8/ 100 =  8%     0/ 100 =  0%  tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
                                0/ 100 =  0%   |
  6  213ms     8/ 100 =  8%     0/ 100 =  0%  pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
                                0/ 100 =  0%   |
  7  206ms     8/ 100 =  8%     0/ 100 =  0%  176.67.177.131
                                0/ 100 =  0%   |
  8  203ms     8/ 100 =  8%     0/ 100 =  0%  xe-8-1-0.edge3.London1.Level3.net[195.50.124.133]
                                0/ 100 =  0%   |
  9  208ms     8/ 100 =  8%     0/ 100 =  0%  vl-3504-ve-118.csw1.London1.Level3.net [4.69.166.141]
                                0/ 100 =  0%   |
 10  211ms     8/ 100 =  8%     0/ 100 =  0%  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
                                0/ 100 =  0%   |
 11  212ms     9/ 100 =  9%     1/ 100 =  1%  213.248.96.37
                                0/ 100 =  0%   |
 12  214ms     8/ 100 =  8%     0/ 100 =  0%  80.91.249.181
                                0/ 100 =  0%   |
 13  238ms     8/ 100 =  8%     0/ 100 =  0%

going to retest just now
 
Second round.. Seems OK. I think.

Code: 
C:\Windows\system32>pathping 80.239.210.89

Tracing route to 80-239-210-89.customer.teliacarrier.com [80.239.210.89]
over a maximum of 30 hops:
  0  JadeX64 [10.10.10.10]
  1  . [10.10.10.1]
  2  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
  3  197-80-4-82.jhb.mweb.co.za [197.80.4.82]
  4  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5  tengig0-7-0-2.12.vic-p-1.mweb.co.za [196.22.169.241]
  6  pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
  7  176.67.177.131
  8  xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
  9  vl-3502-ve-116.csw1.London1.Level3.net [4.69.166.133]
 10  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
 11  Telia [4.68.111.182]
 12     *     ldn-bb2-link.telia.net [80.91.247.93]
 13  hbg-bb2-link.telia.net [213.155.132.250]
 14  adm-bb4-link.telia.net [80.91.246.220]
 15  adm-b5-link.telia.net [213.155.130.43]
 16     *        *        *
Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           JadeX64 [10.10.10.10]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  . [10.10.10.1]
                                0/ 100 =  0%   |
  2   17ms     0/ 100 =  0%     0/ 100 =  0%  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
                                0/ 100 =  0%   |
  3   17ms     0/ 100 =  0%     0/ 100 =  0%  197-80-4-82.jhb.mweb.co.za [197.80.4.82]
                                0/ 100 =  0%   |
  4   16ms     0/ 100 =  0%     0/ 100 =  0%  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
                                0/ 100 =  0%   |
  5   20ms     0/ 100 =  0%     0/ 100 =  0%  tengig0-7-0-2.12.vic-p-1.mweb.co.za [196.22.169.241]
                                0/ 100 =  0%   |
  6  201ms     0/ 100 =  0%     0/ 100 =  0%  pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
                                0/ 100 =  0%   |
  7  207ms     0/ 100 =  0%     0/ 100 =  0%  176.67.177.131
                                0/ 100 =  0%   |
  8  209ms     0/ 100 =  0%     0/ 100 =  0%  xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
                                0/ 100 =  0%   |
  9  202ms     0/ 100 =  0%     0/ 100 =  0%  vl-3502-ve-116.csw1.london1.level3.net [4.69.166.133]
                                0/ 100 =  0%   |
 10  202ms     0/ 100 =  0%     0/ 100 =  0%  ae-1-51.edge5.london1.level3.net [4.69.139.75]
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%   100/ 100 =100%  telia [4.68.111.182]
                                0/ 100 =  0%   |
 12  219ms     0/ 100 =  0%     0/ 100 =  0%  ldn-bb2-link.telia.net [80.91.247.93]
                                0/ 100 =  0%   |
 13  232ms     0/ 100 =  0%     0/ 100 =  0%  hbg-bb2-link.telia.net [213.155.132.250]
                                0/ 100 =  0%   |
 14  221ms     0/ 100 =  0%     0/ 100 =  0%  adm-bb4-link.telia.net [80.91.246.220]
                                0/ 100 =  0%   |
 15  222ms     0/ 100 =  0%     0/ 100 =  0%  adm-b5-link.telia.net [213.155.130.43]

Trace complete.

C:\Windows\system32>
 
Pr⊕phet said:
packet loss indicating.

Code: 
C:\Windows\system32>pathping 80.239.210.89

Tracing route to 80-239-210-89.customer.teliacarrier.com [80.239.210.89]
over a maximum of 30 hops:
  0  JadeX64 [10.10.10.10]
  1  . [10.10.10.1]
  2  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
  3  197-80-4-210.jhb.mweb.co.za [197.80.4.210]
  4  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5  tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
  6  pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
  7  176.67.177.131
  8  xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
  9  vl-3504-ve-118.csw1.London1.Level3.net [4.69.166.141]
 10  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
 11  ldn-b5-link.telia.net [213.248.96.37]
 12  ldn-bb2-link.telia.net [80.91.249.181]
 13  hbg-bb2-link.telia.net [80.91.247.168]
 14  adm-bb4-link.telia.net [80.91.245.140]
 15  adm-b5-link.telia.net [80.91.253.186]
 16     *        *        *
Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           JadeX64 [10.10.10.10]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  . [10.10.10.1]
                                7/ 100 =  7%   |
  2   22ms     7/ 100 =  7%     0/ 100 =  0%  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
                                0/ 100 =  0%   |
  3   22ms     7/ 100 =  7%     0/ 100 =  0%  197-80-4-210.jhb.mweb.co.za [197.80.4.210]
                                0/ 100 =  0%   |
  4   22ms     7/ 100 =  7%     0/ 100 =  0%  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
                                1/ 100 =  1%   |
  5   25ms     8/ 100 =  8%     0/ 100 =  0%  tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
                                0/ 100 =  0%   |
  6  213ms     8/ 100 =  8%     0/ 100 =  0%  pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
                                0/ 100 =  0%   |
  7  206ms     8/ 100 =  8%     0/ 100 =  0%  176.67.177.131
                                0/ 100 =  0%   |
  8  203ms     8/ 100 =  8%     0/ 100 =  0%  xe-8-1-0.edge3.London1.Level3.net[195.50.124.133]
                                0/ 100 =  0%   |
  9  208ms     8/ 100 =  8%     0/ 100 =  0%  vl-3504-ve-118.csw1.London1.Level3.net [4.69.166.141]
                                0/ 100 =  0%   |
 10  211ms     8/ 100 =  8%     0/ 100 =  0%  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
                                0/ 100 =  0%   |
 11  212ms     9/ 100 =  9%     1/ 100 =  1%  213.248.96.37
                                0/ 100 =  0%   |
 12  214ms     8/ 100 =  8%     0/ 100 =  0%  80.91.249.181
                                0/ 100 =  0%   |
 13  238ms     8/ 100 =  8%     0/ 100 =  0%

going to retest just now
Click to expand...

Thanks Pr⊕phet, keep me posted.
 
Just DCed again. Now to extract data from pingplotter
 
Packet loss indicating

a3md0l.jpg



Code: 
C:\Windows\system32>pathping 80.239.209.99

Tracing route to 80-239-209-99.customer.teliacarrier.com [80.239.209.99]
over a maximum of 30 hops:
  0  JadeX64 [10.10.10.10]
  1  . [10.10.10.1]
  2  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
  3  41-86-107-18.mweb.co.za [41.86.107.18]
  4  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5  tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
  6  pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
  7  176.67.177.131
  8  xe-8-1-0.edge3.london1.level3.net [195.50.124.133]
  9  vl-3601-ve-225.csw2.London1.Level3.net [4.69.166.145]
 10     *     ae-2-52.edge5.London1.Level3.net [4.69.139.107]
 11  telia [4.68.111.182]
 12  ldn-bb2-link.telia.net [80.91.247.93]
 13  hbg-bb2-link.telia.net [80.91.247.198]
 14  adm-bb4-link.telia.net [80.91.245.56]
 15  adm-b5-link.telia.net [213.155.130.43]
 16     *        *        *
Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           JadeX64 [10.10.10.10]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  . [10.10.10.1]
                                0/ 100 =  0%   |
  2   17ms     0/ 100 =  0%     0/ 100 =  0%  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
                                0/ 100 =  0%   |
  3   18ms     0/ 100 =  0%     0/ 100 =  0%  41-86-107-18.mweb.co.za [41.86.107.18]
                                0/ 100 =  0%   |
  4   20ms     0/ 100 =  0%     0/ 100 =  0%  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
                                0/ 100 =  0%   |
  5   20ms     0/ 100 =  0%     0/ 100 =  0%  tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
                                0/ 100 =  0%   |
  6  208ms     0/ 100 =  0%     0/ 100 =  0%  pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
                                0/ 100 =  0%   |
  7  208ms     0/ 100 =  0%     0/ 100 =  0%  176.67.177.131
                                0/ 100 =  0%   |
  8  205ms     0/ 100 =  0%     0/ 100 =  0%  xe-8-1-0.edge3.london1.level3.net [195.50.124.133]
                                0/ 100 =  0%   |
  9  212ms     0/ 100 =  0%     0/ 100 =  0%  vl-3601-ve-225.csw2.London1.Level3.net [4.69.166.145]
                                0/ 100 =  0%   |
 10  205ms     0/ 100 =  0%     0/ 100 =  0%  ae-2-52.edge5.London1.Level3.net [4.69.139.107]
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%   100/ 100 =100%  telia [4.68.111.182]
                                0/ 100 =  0%   |
 12  220ms     0/ 100 =  0%     0/ 100 =  0%  ldn-bb2-link.telia.net [80.91.247.93]
                                0/ 100 =  0%   |
 13  273ms     1/ 100 =  1%     1/ 100 =  1%  hbg-bb2-link.telia.net [80.91.247.198]
                                0/ 100 =  0%   |
 14  261ms     0/ 100 =  0%     0/ 100 =  0%  adm-bb4-link.telia.net [80.91.245.56]
                                0/ 100 =  0%   |
 15  241ms     0/ 100 =  0%     0/ 100 =  0%  adm-b5-link.telia.net [213.155.130.43]

Trace complete.

C:\Windows\system32>
 
Last edited:
MWEB Guy said:
Provide me with a trace route and ping test to that site and I will escalate this matter to our specialists
Click to expand...

So here we are again. No feedback on my request of yesterday.
Access to 4shared.com was up later the night. Tonite i have the same issue, not accessible but possible via web-proxy.

So I assume the, "send me your stats so our specialists can look at it" is basically a tongue-in-cheek response while/during manipulation of access for periods...........
 
Last edited:
Let me give it the benefit of the doubt.

MwebGuy, please have a look. I cannot access 4shared.com while it is possible via web proxy. I again asked another Mweb user and he confirms the same...

Should I provide a ping and traceroute?

Regards
Mortiiy
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X