MWEB Uncapped ADSL Feedback - Part 2

Hummercellc · Mar 19, 2013

Mweb Guy,

Are the Techie's looking at the 4meg account problem? because I am getting really frustrated now!

http://www.speedtest.net/result/2584605789.png
http://www.speedtest.net/result/2584610012.png

MWEBHelp · Mar 19, 2013

Hummercellc said:
Mweb Guy,

Are the Techie's looking at the 4meg account problem? because I am getting really frustrated now!

http://www.speedtest.net/result/2584605789.png
http://www.speedtest.net/result/2584610012.png

Good Afternoon, the query is with our network team and we are awaiting their feedback.

Please bear with us...

merge · Mar 19, 2013

Hi MWEB Guy, any idea whats wrong with my speeds? Are you having news server issues again?

MWEBHelp · Mar 19, 2013

merge said:
Hi MWEB Guy, any idea whats wrong with my speeds? Are you having news server issues again?

Good Day merge, please provide me the actual speeds you are obtaining at the moment.

I also require you to provide me your MWEB account details via private message please.

merge · Mar 19, 2013

MWEB Guy said:
Good Day merge, please provide me the actual speeds you are obtaining at the moment.

I also require you to provide me your MWEB account details via private message please.

44KB/s

I'll PM the details just now

MWEBHelp · Mar 19, 2013

merge said:
44KB/s

I'll PM the details just now

Thanks for the details, that is not too bad considering the time of day.

I have changed a setting on your account as an interim measure, please reboot your router and let me know if it helps.

Hummercellc · Mar 19, 2013

Well, It is going from bad to worse,

http://www.speedtest.net/result/2584782795.png

Took me 2 mins to post this and 5mins to do a speedtest, NNTP is stone dead.

MWEBHelp · Mar 19, 2013

Hummercellc said:
Well, It is going from bad to worse,

http://www.speedtest.net/result/2584782795.png

Took me 2 mins to post this and 5mins to do a speedtest, NNTP is stone dead.

Thanks for the data HummerCellC, I have had a re-auth completed on the back end. Please reboot your router and let me know if this makes a difference.

merge · Mar 19, 2013

MWEB Guy said:
Thanks for the details, that is not too bad considering the time of day.

I have changed a setting on your account as an interim measure, please reboot your router and let me know if it helps.

It's the same. BTW, it's not a time of day thing(do you shape heavily during the day?) because I had the same speeds last night.

Also, when I use an alternative news server I get the same speeds. This has not been a problem before.

MWEBHelp · Mar 19, 2013

merge said:
It's the same. BTW, it's not a time of day thing(do you shape heavily during the day?) because I had the same speeds last night.

Also, when I use an alternative news server I get the same speeds. This has not been a problem before.

The shaping is a bit more aggressive during the day, as business traffic is prioritised

Please provide me speed test results, tracers and pings to mweb.co.za and bbc.co.uk

merge · Mar 19, 2013

MWEB Guy said:
The shaping is a bit more aggressive during the day, as business traffic is prioritised

Ah, ok.

MWEB Guy said:
Please provide me speed test results, tracers and pings to mweb.co.za and bbc.co.uk

Sure...How do I do that?

MWEBHelp · Mar 19, 2013

merge said:
Ah, ok.

Sure...How do I do that?

Start, command prompt (once the black screen loads), tracert bbc.co.uk and press enter. You can then right click and select mark. Then highlight the data with your curser and press enter to copy. YOu can then past the results here, ctrl v.

merge · Mar 19, 2013

MWEB Guy said:
Start, command prompt (once the black screen loads), tracert bbc.co.uk and press enter. You can then right click and select mark. Then highlight the data with your curser and press enter to copy. YOu can then past the results here, ctrl v.

tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:

1 General failure.

Trace complete.

--------------------------------------------------------------------------

tracert mweb.co.za

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

1 1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 7 ms 8 ms 197-87-40-1.cpt.mweb.co.za [197.87.40.1]
3 8 ms 27 ms 10 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
4 59 ms 63 ms 51 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 42 ms 46 ms 44 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 33 ms 34 ms 34 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

7 30 ms 32 ms 30 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 42 ms 51 ms 31 ms 196.28.178.66
9 60 ms 39 ms 64 ms cte-core-sw2.vwol.net [196.41.144.35]
10 30 ms 30 ms 42 ms www.mweb.co.za [196.2.63.110]

Trace complete.

MWEBHelp · Mar 19, 2013

merge said:
tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:

1 General failure.

Trace complete.

--------------------------------------------------------------------------

tracert mweb.co.za

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

1 1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 7 ms 8 ms 197-87-40-1.cpt.mweb.co.za [197.87.40.1]
3 8 ms 27 ms 10 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
4 59 ms 63 ms 51 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 42 ms 46 ms 44 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 33 ms 34 ms 34 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

7 30 ms 32 ms 30 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 42 ms 51 ms 31 ms 196.28.178.66
9 60 ms 39 ms 64 ms cte-core-sw2.vwol.net [196.41.144.35]
10 30 ms 30 ms 42 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Your trace results seem normal, please monitor your speeds through the course of this evening and let me know if it improves or not.

merge · Mar 19, 2013

MWEB Guy said:
Your trace results seem normal, please monitor your speeds through the course of this evening and let me know if it improves or not.

Will do

Magnarmalok · Mar 19, 2013

View attachment 2585124669.png
http://www.speedtest.net/result/2585124669.png

Code:

Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:

  1   246 ms   158 ms    71 ms  41-133-102-1.dsl.mweb.co.za [41.133.102.1]
  2   274 ms   317 ms   441 ms  197-84-8-10.cpt.mweb.co.za [197.84.8.10]
  3    89 ms     7 ms     7 ms  197-84-3-2.cpt.mweb.co.za [197.84.3.2]
  4   303 ms   307 ms   464 ms  TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178
.113]
  5   267 ms   244 ms   211 ms  197-84-4-32.cpt.mweb.co.za [197.84.4.32]
  6   372 ms   397 ms   443 ms  197-84-4-197.cpt.mweb.co.za [197.84.4.197]
  7   258 ms   227 ms   255 ms  176.67.177.131
  8   830 ms   809 ms   731 ms  xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
  9   860 ms   677 ms   718 ms  vl-3601-ve-225.csw2.London1.Level3.net [4.69.166
.145]
 10   724 ms   755 ms     *     ae-2-52.edge4.London1.Level3.net [4.69.139.106]

 11   563 ms   537 ms   734 ms  BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
.222]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   540 ms   685 ms   780 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
 15   645 ms   640 ms   688 ms  132.185.255.156
 16   367 ms   335 ms   274 ms  www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.

Code:

Pinging bbc.co.uk [212.58.253.67] with 32 bytes of dat
Reply from 212.58.253.67: bytes=32 time=249ms TTL=113
Reply from 212.58.253.67: bytes=32 time=311ms TTL=113
Reply from 212.58.253.67: bytes=32 time=285ms TTL=113
Reply from 212.58.253.67: bytes=32 time=411ms TTL=113

Ping statistics for 212.58.253.67:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
    Minimum = 249ms, Maximum = 411ms, Average = 314ms

Code:

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

  1   412 ms   387 ms   420 ms  41-133-102-1.dsl.mweb.co.za [41.133.102.1]
  2   300 ms   235 ms   230 ms  196-28-178-222.adsl.mweb.co.za [196.28.178.222]

  3   338 ms   414 ms   356 ms  197-84-2-2.cpt.mweb.co.za [197.84.2.2]
  4   297 ms   350 ms   373 ms  196.28.178.66
  5   272 ms   293 ms   273 ms  cte-core-sw2.vwol.net [196.41.144.35]
  6   213 ms   232 ms   285 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Code:

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=342ms TTL=123
Reply from 196.2.63.110: bytes=32 time=8ms TTL=123
Reply from 196.2.63.110: bytes=32 time=126ms TTL=123
Reply from 196.2.63.110: bytes=32 time=163ms TTL=123

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

This is on a 1mb line In Welgemoed, Bellville.

MWEBHelp · Mar 19, 2013

Magnarmalok said:

View attachment 43458
http://www.speedtest.net/result/2585124669.png

Code:

Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:

  1   246 ms   158 ms    71 ms  41-133-102-1.dsl.mweb.co.za [41.133.102.1]
  2   274 ms   317 ms   441 ms  197-84-8-10.cpt.mweb.co.za [197.84.8.10]
  3    89 ms     7 ms     7 ms  197-84-3-2.cpt.mweb.co.za [197.84.3.2]
  4   303 ms   307 ms   464 ms  TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178
.113]
  5   267 ms   244 ms   211 ms  197-84-4-32.cpt.mweb.co.za [197.84.4.32]
  6   372 ms   397 ms   443 ms  197-84-4-197.cpt.mweb.co.za [197.84.4.197]
  7   258 ms   227 ms   255 ms  176.67.177.131
  8   830 ms   809 ms   731 ms  xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
  9   860 ms   677 ms   718 ms  vl-3601-ve-225.csw2.London1.Level3.net [4.69.166
.145]
 10   724 ms   755 ms     *     ae-2-52.edge4.London1.Level3.net [4.69.139.106]

 11   563 ms   537 ms   734 ms  BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
.222]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   540 ms   685 ms   780 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
 15   645 ms   640 ms   688 ms  132.185.255.156
 16   367 ms   335 ms   274 ms  www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.

Code:

Pinging bbc.co.uk [212.58.253.67] with 32 bytes of dat
Reply from 212.58.253.67: bytes=32 time=249ms TTL=113
Reply from 212.58.253.67: bytes=32 time=311ms TTL=113
Reply from 212.58.253.67: bytes=32 time=285ms TTL=113
Reply from 212.58.253.67: bytes=32 time=411ms TTL=113

Ping statistics for 212.58.253.67:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
    Minimum = 249ms, Maximum = 411ms, Average = 314ms

Code:

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

  1   412 ms   387 ms   420 ms  41-133-102-1.dsl.mweb.co.za [41.133.102.1]
  2   300 ms   235 ms   230 ms  196-28-178-222.adsl.mweb.co.za [196.28.178.222]

  3   338 ms   414 ms   356 ms  197-84-2-2.cpt.mweb.co.za [197.84.2.2]
  4   297 ms   350 ms   373 ms  196.28.178.66
  5   272 ms   293 ms   273 ms  cte-core-sw2.vwol.net [196.41.144.35]
  6   213 ms   232 ms   285 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Code:

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=342ms TTL=123
Reply from 196.2.63.110: bytes=32 time=8ms TTL=123
Reply from 196.2.63.110: bytes=32 time=126ms TTL=123
Reply from 196.2.63.110: bytes=32 time=163ms TTL=123

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

This is on a 1mb line In Welgemoed, Bellville.

Good evening, those results are not good. It show's a big jump in latency on the very first hop, which would illustrate that the problem is closet to the remote end or the remote end itself.

Were you perhaps running downloads while doing these tests?

Magnarmalok · Mar 19, 2013

MWEB Guy said:
Good evening, those results are not good. It show's a big jump in latency on the very first hop, which would illustrate that the problem is closet to the remote end or the remote end itself.

Were you perhaps running downloads while doing these tests?

No, I wasn't I had all of them off for quite awhile since it's almost impossible to navigate http as it is. I'll try restarting the modem and see what happens.

MWEBHelp · Mar 19, 2013

Magnarmalok said:
No, I wasn't I had all of them off for quite awhile since it's almost impossible to navigate http as it is. I'll try restarting the modem and see what happens.

let me know what the results are after the reboot...

alternate · Mar 19, 2013

Magnarmalok from your tracerts if you are not doing anything else on the line and no downloads are happening on any other devices on your network then it looks like your exchange is congested. It's Telkom's fault not your ISP (mweb) and I've have the same problem for 7 months.

Join the MyBroadband community

Get started

MWEB Uncapped ADSL Feedback - Part 2

Expert Member

MWEB Representative

Member

MWEB Representative

Member

MWEB Representative

Expert Member

MWEB Representative

Member

MWEB Representative

Member

MWEB Representative

Member

MWEB Representative

Member

Expert Member

MWEB Representative

Expert Member

MWEB Representative

Expert Member