MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Dysphoric said:
Hi

As per my comment from Sunday night, still having serious problems, WoW ping >1000ms, and download speeds are crawling.

http://www.speedtest.net/my-result/2841006139

Trace routes:

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.1.1
2 121 ms 111 ms 98 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 116 ms 109 ms 89 ms te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166
]
4 107 ms 113 ms * 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 * 132 ms 130 ms 196.28.178.66
6 124 ms 119 ms 101 ms cte-core-sw2.vwol.net [196.41.144.35]
7 82 ms 74 ms 81 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Tracing route to www.bbc.net.uk [212.58.246.94]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 81 ms 72 ms 69 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 104 ms 87 ms 74 ms 197-84-8-82.cpt.mweb.co.za [197.84.8.82]
4 132 ms 117 ms 118 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 206 ms 211 ms 248 ms TenGigE0-7-0-2.12.cpt-p-2.mweb.co.za [196.28.178
.114]
6 235 ms 260 ms * 197-84-4-195.cpt.mweb.co.za [197.84.4.195]
7 * 299 ms 312 ms 176.67.177.131
8 223 ms 278 ms * xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
9 * 277 ms 275 ms vl-3504-ve-118.csw1.London1.Level3.net [4.69.166
.141]
10 272 ms 252 ms 261 ms 4.69.166.1
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * 257 ms 244 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
15 * * 298 ms 132.185.255.164
16 277 ms 257 ms 269 ms bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.


Please don't blame it on exchange congestion, I have had that ongoing issue for the last year or more (these trace routes look no different to normal for me); and I have alwyas consistently got a few hundred ms ping to EU servers and acceptable download speeds for my 2mb line.

Can't do anything at the moment.
Current issue has been ongoing for about 1 week now.
Click to expand...

Hi

Are you getting these problems all through the day or only certain times of the day?
Try doing these same test during the day and again in the evening to see if there is any difference.
I'm afraid from what your traces show though, it seems like it could possibly be congestion at the exchange.
 
Vorador said:
Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 2 ms 1 ms <1 ms Alpha.Home [192.168.1.1]
2 776 ms 808 ms 720 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 790 ms 825 ms 884 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 950 ms 864 ms 905 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 887 ms 851 ms 960 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za [196.22.169.225]
6 844 ms 891 ms 903 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
7 892 ms 786 ms 825 ms static161-134.netactive.co.za [196.22.161.134]
8 845 ms 945 ms 915 ms 196.44.0.223
9 941 ms 912 ms 981 ms 196.44.31.99
10 910 ms 931 ms 964 ms ge10-1-1sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.8]
11 947 ms 908 ms 920 ms tengigabitethernet9-1.gw21.jnb6.za.mtnbusiness.net [196.31.220.27]
12 783 ms 824 ms 866 ms tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.net [196.31.63.150]
13 935 ms 956 ms 924 ms core-router1.jnb2.host-h.net [196.30.213.108]
14 873 ms 919 ms 834 ms 41.72.136.53
15 877 ms 871 ms 953 ms mybroadband.co.za [41.203.21.137]

Trace complete.

Tracing route to www-bbc-com.bbc.net.uk [212.58.246.91]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Alpha.Home [192.168.1.1]
2 808 ms 875 ms 911 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 862 ms 894 ms 837 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 897 ms * 879 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 1036 ms 1059 ms 1154 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 1123 ms 1092 ms 1148 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 1226 ms 1119 ms 1026 ms 176.67.177.227
8 1072 ms 1064 ms 1079 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 1059 ms 1052 ms 1042 ms 4.69.166.137
10 1052 ms 1066 ms 1055 ms 4.69.166.13
11 1004 ms 1050 ms 1114 ms 212.113.14.222
12 * * * Request timed out.
13 * * * Request timed out.
14 1040 ms 1125 ms 1094 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
15 1241 ms 1134 ms 1111 ms 132.185.255.164
16 1196 ms 1208 ms 1002 ms bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]

Trace complete.
Click to expand...

Hi Vorador

These trace routes points to possible congestion issue on your exchange.
This is evident by the spike in the second hop and the fact that you said during the day it's fine.
It's most likely why your connection is so degraded after hours.
 
MWEB Guy said:
do a trace route to a local and international site and send me the results.
Click to expand...

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms READYSHARE []
2 3 ms 2 ms 1 ms
3 37 ms 35 ms 35 ms 41-133-120-1.dsl.mweb.co.za [41.133.120.1]
4 37 ms 37 ms 37 ms 197-80-132-142.jhb.mweb.co.za [197.80.132.142]
5 38 ms 38 ms 38 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 46 ms 46 ms 53 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za [196.22.169.225]
7 97 ms 103 ms 100 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
8 48 ms 50 ms 50 ms static161-134.netactive.co.za [196.22.161.134]
9 72 ms 84 ms 85 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]
10 117 ms 94 ms 95 ms 196.44.31.99
11 61 ms 47 ms 46 ms 196.30.1.39
12 43 ms 39 ms 39 ms tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.net [196.31.220.21]
13 39 ms 39 ms 39 ms tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.net [196.31.63.150]
14 40 ms 43 ms 38 ms core-router1.jnb2.host-h.net [196.30.213.108]
15 40 ms 39 ms 39 ms core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
16 41 ms 40 ms 39 ms mybroadband.co.za [41.203.21.137]

Trace complete.
Click to expand...

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms READYSHARE []
2 2 ms 1 ms 1 ms
3 37 ms 36 ms 37 ms 41-133-120-1.dsl.mweb.co.za [41.133.120.1]
4 41 ms 49 ms 55 ms 197-80-132-142.jhb.mweb.co.za [197.80.132.142]
5 42 ms 46 ms 47 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 45 ms 49 ms 56 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za [196.22.169.225]
7 91 ms 78 ms 76 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
8 51 ms 45 ms 52 ms static161-134.netactive.co.za [196.22.161.134]
9 44 ms 41 ms 40 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]
10 39 ms 41 ms 38 ms 196.44.31.99
11 54 ms 43 ms 39 ms 196.30.1.39
12 54 ms 42 ms 38 ms tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.net [196.31.220.21]
13 43 ms 38 ms 39 ms tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.net [196.31.63.150]
14 45 ms 43 ms 39 ms core-router1.jnb2.host-h.net [196.30.213.108]
15 40 ms 40 ms 40 ms core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
16 56 ms 50 ms 57 ms mybroadband.co.za [41.203.21.137]

Trace complete.
Click to expand...

Tracing route to www-bbc-com.bbc.net.uk [212.58.246.92]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms READYSHARE []
2 2 ms 1 ms 1 ms
3 36 ms 36 ms 36 ms 41-133-120-1.dsl.mweb.co.za [41.133.120.1]
4 37 ms 37 ms 37 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
5 36 ms 37 ms 37 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 222 ms 218 ms 220 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
7 223 ms 222 ms 219 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
8 219 ms 219 ms 219 ms 176.67.177.227
9 217 ms 217 ms 216 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
10 219 ms 219 ms 219 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166.153]
11 217 ms 217 ms 216 ms 4.69.166.17
12 220 ms 218 ms 219 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14.222]
13 * * * Request timed out.
14 * * * Request timed out.
15 217 ms 233 ms 235 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
16 221 ms 219 ms 220 ms 132.185.255.164
17 219 ms 218 ms 218 ms bbc-vip013.cwwtf.bbc.co.uk [212.58.246.92]

Trace complete.
Click to expand...
Tracing route to www-bbc-com.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms READYSHARE []
2 2 ms 1 ms 1 ms
3 37 ms 35 ms 34 ms 41-133-120-1.dsl.mweb.co.za [41.133.120.1]
4 41 ms 42 ms 37 ms 197-80-4-70.jhb.mweb.co.za [197.80.4.70]
5 38 ms 37 ms 37 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 219 ms 214 ms 216 ms tengig0-7-0-2.12.vic-p-1.mweb.co.za [196.22.169.241]
7 218 ms 216 ms 219 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
8 223 ms 215 ms 215 ms 176.67.177.131
9 215 ms 214 ms 233 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
10 216 ms 215 ms 214 ms vl-3504-ve-118.csw1.London1.Level3.net [4.69.166.141]
11 214 ms 214 ms 214 ms 4.69.166.5
12 217 ms 216 ms 216 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14.222]
13 * * * Request timed out.
14 * * * Request timed out.
15 217 ms 216 ms 217 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
16 216 ms 217 ms 216 ms 132.185.255.164
17 219 ms 217 ms 217 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.
Click to expand...

Like a Yo-Yo. I have to be happy I presume. After all it's best effort!
 
Seriously said:
Like a Yo-Yo. I have to be happy I presume. After all it's best effort!
Click to expand...

Hi

I don't see any issues with your traces, the results look good.
With regards to the request that timed out, this could be as a result of a firewall on the bbc network blocking your request.
What seems to be the problem you are experiencing?
 
Im getting some packetloss on my line.

Ok so talked to a mweb person and couldn't find the problem and they will phone me back tomorrow.

Did another test now with a pingtest to telkom and had avg latency of 40ms and highest being 100 but no loss.

Did a test to mweb.co.za right after that and I get 12ms avg but some packet loss and a few very high return pings like 500ms <
 
Last edited:
MWEB Guy said:
Hi

Are you getting these problems all through the day or only certain times of the day?
Try doing these same test during the day and again in the evening to see if there is any difference.
I'm afraid from what your traces show though, it seems like it could possibly be congestion at the exchange.
Click to expand...

Trace from this morning 8:30am

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.1.1
2 7 ms 7 ms 7 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 9 ms 8 ms 9 ms te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166
]
4 8 ms 9 ms 8 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 10 ms 8 ms 9 ms 196.28.178.66
6 9 ms 9 ms 8 ms cte-core-sw2.vwol.net [196.41.144.35]
7 * 25 ms * www.mweb.co.za [196.2.63.110]
8 21 ms 20 ms 24 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Speedtest: http://www.speedtest.net/result/2846209061.png

So what are my options? The congestion has been there all year, but as of the last week I might as well not use it from 5pm-12am, which is the only time I'm at home. Congestion is also there all day weekends, will take another trace tomorrow to demonstrate.
 
Dysphoric said:
Trace from this morning 8:30am

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.1.1
2 7 ms 7 ms 7 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 9 ms 8 ms 9 ms te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166
]
4 8 ms 9 ms 8 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 10 ms 8 ms 9 ms 196.28.178.66
6 9 ms 9 ms 8 ms cte-core-sw2.vwol.net [196.41.144.35]
7 * 25 ms * www.mweb.co.za [196.2.63.110]
8 21 ms 20 ms 24 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Speedtest: http://www.speedtest.net/result/2846209061.png

So what are my options? The congestion has been there all year, but as of the last week I might as well not use it from 5pm-12am, which is the only time I'm at home. Congestion is also there all day weekends, will take another trace tomorrow to demonstrate.
Click to expand...

Thank you for the feedback, it's almost certainly as a result of a congested exchange but I could log a line fault for you if you'd like.
The trace looks good and so does the speedtest if you compare it to the earlier test you posted.
Please check again tomorrow as you said but I doubt it will change.
 
Last edited:
EDIT: Never mind. Just found out that my account has been already cancelled. :o
 
Last edited:
XennoX said:
Okay, it seems like my line has gone down again. The line is sync'ed but no authentication is taking place. This is getting crazy, its the 4th time this year.
Click to expand...

Hi XennoX, test by setting your router up with telkoms guest details and going to www.saix.net

Username: guest@telkomadsl
Password: guest
 
Very, very slow line today. It takes more than a minute to load a normal webpage...



Is it normal that I never get a faster connection than 1,5 Mbit/s although I pay for 2Mbit? The average down speed ranges between 1.0 and 1.5 Mbit/s. Upspeed is at around 0,40 Mbit/s. I am thinking about moving to another ISP as I don't get what I pay for...
 
capek said:
Very, very slow line today. It takes more than a minute to load a normal webpage...



Is it normal that I never get a faster connection than 1,5 Mbit/s although I pay for 2Mbit? The average down speed ranges between 1.0 and 1.5 Mbit/s. Upspeed is at around 0,40 Mbit/s. I am thinking about moving to another ISP as I don't get what I pay for...
Click to expand...

Hi capek, send me a trace route to a local and international site.
 
MWEB Guy said:
Hi capek, send me a trace route to a local and international site.
Click to expand...

I don't know if this is correct because it is still tracing (for 5 minutes already) but I only get 12 * * * 13 *** and so on...

traceroute to www.iol.co.za (196.38.8.254), 64 hops max, 72 byte packets
1 * 192.168.1.1 (192.168.1.1) 2055.723 ms 54.830 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 483.339 ms 1008.463 ms 1933.113 ms
3 197-84-8-82.cpt.mweb.co.za (197.84.8.82) 1019.011 ms 210.462 ms 776.775 ms
4 * 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 686.614 ms 504.265 ms
5 tengige0-0-0-2.11.cpt-p-1.mweb.co.za (196.28.178.97) 58.580 ms 22.003 ms 24.747 ms
6 197-84-4-225.cpt.mweb.co.za (197.84.4.225) 249.222 ms 224.063 ms 44.704 ms
7 is.cinx.net.za (196.223.22.10) 46.753 ms 223.308 ms 20.224 ms
8 168.209.6.12 (168.209.6.12) 14.257 ms 15.443 ms 208.580 ms
9 168.209.100.13 (168.209.100.13) 38.926 ms 35.835 ms 35.947 ms
10 csw5-pkl-te1-7.ip.isnet.net (196.26.0.188) 52.591 ms 37.114 ms 44.149 ms
11 196.38.8.254 (196.38.8.254) 444.373 ms 39.648 ms 42.639 ms
12 ***
13 ***
etc.

traceroute to www.spiegel.de (62.138.116.3), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 6.841 ms 2.933 ms 8.401 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 1843.083 ms 14.549 ms 81.131 ms
3 te1-1-0.511.cpt-ipc-1.mweb.co.za (196.28.178.202) 63.466 ms 23.788 ms 159.286 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 17.550 ms 14.468 ms 701.235 ms
5 197-84-5-241.cpt.mweb.co.za (197.84.5.241) 267.698 ms 174.613 ms 350.292 ms
6 197-84-4-193.cpt.mweb.co.za (197.84.4.193) 579.596 ms 165.736 ms 163.847 ms
7 176.67.177.148 (176.67.177.148) 203.333 ms 196.573 ms 270.460 ms
8 xe-10-1-3.edge4.london1.level3.net (212.113.14.121) 193.316 ms 199.604 ms 200.529 ms
9 195.50.122.2 (195.50.122.2) 183.792 ms 171.842 ms 187.621 ms
10 xe0-1-4-0-grtfraix5.red.telefonica-wholesale.net (84.16.14.165) 182.399 ms 186.964 ms 201.070 ms
11 176.52.253.174 (176.52.253.174) 331.691 ms 180.214 ms 200.294 ms
12 rmwc-frnk-de01-xe-7-0-3-0.nw.mediaways.net (195.71.212.221) 276.333 ms
rmwc-frnk-de01-xe-7-1-0-0.nw.mediaways.net (195.71.158.161) 175.977 ms
rmwc-frnk-de01-xe-2-0-0-0.nw.mediaways.net (195.71.158.17) 205.905 ms
13 rmwc-brmn-de02-gigaet-1-1-0.nw.mediaways.net (195.71.212.82) 338.821 ms
rmwc-gtso-de01-ge-0-0-0-0.nw.mediaways.net (195.71.254.78) 192.989 ms
rmwc-brmn-de02-gigaet-1-1-0.nw.mediaways.net (195.71.212.82) 184.049 ms
14 xmws-gtso-de11-vlan-2.nw.mediaways.net (195.71.10.195) 181.654 ms
xmws-gtso-de12-vlan-3.nw.mediaways.net (195.71.10.203) 179.715 ms 180.546 ms
15 62.138.116.3 (62.138.116.3) 182.112 ms 212.854 ms 196.526 ms
 
capek said:
I don't know if this is correct because it is still tracing (for 5 minutes already) but I only get 12 * * * 13 *** and so on...

traceroute to www.iol.co.za (196.38.8.254), 64 hops max, 72 byte packets
1 * 192.168.1.1 (192.168.1.1) 2055.723 ms 54.830 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 483.339 ms 1008.463 ms 1933.113 ms
3 197-84-8-82.cpt.mweb.co.za (197.84.8.82) 1019.011 ms 210.462 ms 776.775 ms
4 * 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 686.614 ms 504.265 ms
5 tengige0-0-0-2.11.cpt-p-1.mweb.co.za (196.28.178.97) 58.580 ms 22.003 ms 24.747 ms
6 197-84-4-225.cpt.mweb.co.za (197.84.4.225) 249.222 ms 224.063 ms 44.704 ms
7 is.cinx.net.za (196.223.22.10) 46.753 ms 223.308 ms 20.224 ms
8 168.209.6.12 (168.209.6.12) 14.257 ms 15.443 ms 208.580 ms
9 168.209.100.13 (168.209.100.13) 38.926 ms 35.835 ms 35.947 ms
10 csw5-pkl-te1-7.ip.isnet.net (196.26.0.188) 52.591 ms 37.114 ms 44.149 ms
11 196.38.8.254 (196.38.8.254) 444.373 ms 39.648 ms 42.639 ms
12 ***
13 ***
etc.

traceroute to www.spiegel.de (62.138.116.3), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 6.841 ms 2.933 ms 8.401 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 1843.083 ms 14.549 ms 81.131 ms
3 te1-1-0.511.cpt-ipc-1.mweb.co.za (196.28.178.202) 63.466 ms 23.788 ms 159.286 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 17.550 ms 14.468 ms 701.235 ms
5 197-84-5-241.cpt.mweb.co.za (197.84.5.241) 267.698 ms 174.613 ms 350.292 ms
6 197-84-4-193.cpt.mweb.co.za (197.84.4.193) 579.596 ms 165.736 ms 163.847 ms
7 176.67.177.148 (176.67.177.148) 203.333 ms 196.573 ms 270.460 ms
8 xe-10-1-3.edge4.london1.level3.net (212.113.14.121) 193.316 ms 199.604 ms 200.529 ms
9 195.50.122.2 (195.50.122.2) 183.792 ms 171.842 ms 187.621 ms
10 xe0-1-4-0-grtfraix5.red.telefonica-wholesale.net (84.16.14.165) 182.399 ms 186.964 ms 201.070 ms
11 176.52.253.174 (176.52.253.174) 331.691 ms 180.214 ms 200.294 ms
12 rmwc-frnk-de01-xe-7-0-3-0.nw.mediaways.net (195.71.212.221) 276.333 ms
rmwc-frnk-de01-xe-7-1-0-0.nw.mediaways.net (195.71.158.161) 175.977 ms
rmwc-frnk-de01-xe-2-0-0-0.nw.mediaways.net (195.71.158.17) 205.905 ms
13 rmwc-brmn-de02-gigaet-1-1-0.nw.mediaways.net (195.71.212.82) 338.821 ms
rmwc-gtso-de01-ge-0-0-0-0.nw.mediaways.net (195.71.254.78) 192.989 ms
rmwc-brmn-de02-gigaet-1-1-0.nw.mediaways.net (195.71.212.82) 184.049 ms
14 xmws-gtso-de11-vlan-2.nw.mediaways.net (195.71.10.195) 181.654 ms
xmws-gtso-de12-vlan-3.nw.mediaways.net (195.71.10.203) 179.715 ms 180.546 ms
15 62.138.116.3 (62.138.116.3) 182.112 ms 212.854 ms 196.526 ms
Click to expand...

Please see the PM I sent you.
 
Something completely buggered.



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

  1     1 ms     1 ms     1 ms  Primary [192.168.0.1]
  2     *      543 ms   528 ms  41-133-98-1.dsl.mweb.co.za [41.133.98.1]
  3   520 ms   516 ms   544 ms  41-86-107-18.mweb.co.za [41.86.107.18]
  4   509 ms   523 ms   532 ms  197-80-2-2.jhb.mweb.co.za [197.80.2.2]
  5   550 ms   527 ms   522 ms  197-80-5-242.jhb.mweb.co.za [197.80.5.242]
  6   538 ms   540 ms   546 ms  TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

  7   540 ms   526 ms     *     vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
  8   537 ms     *      535 ms  196.28.178.66
  9   525 ms   522 ms   536 ms  cte-core-sw2.vwol.net [196.41.144.35]
 10   526 ms   528 ms   541 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Tracing route to cnn-lax-tmp.gslb.vgtf.net [157.166.240.13]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  Primary [192.168.0.1]
  2   515 ms   504 ms   504 ms  41-133-98-1.dsl.mweb.co.za [41.133.98.1]
  3   513 ms   503 ms   489 ms  197-80-4-82.jhb.mweb.co.za [197.80.4.82]
  4   520 ms   512 ms   496 ms  197-80-2-1.jhb.mweb.co.za [197.80.2.1]
  5   710 ms   681 ms   691 ms  197-80-5-226.jhb.mweb.co.za [197.80.5.226]
  6   714 ms   707 ms   698 ms  pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
  7   688 ms   698 ms   685 ms  176.67.177.131
  8   683 ms   665 ms   680 ms  xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
  9   824 ms   810 ms     *     vl-3604-ve-228.csw2.London1.Level3.net [4.69.166
.157]
 10   825 ms   827 ms   827 ms  ae-59-224.ebr2.London1.Level3.net [4.69.153.141]

 11     *      812 ms   847 ms  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

 12   834 ms   813 ms   842 ms  ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]

 13   838 ms   847 ms   849 ms  ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45]

 14   838 ms   827 ms   851 ms  4.69.135.185
 15   832 ms   852 ms   828 ms  ae-2-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]

 16   839 ms   823 ms   823 ms  ae-83-83.csw3.LosAngeles1.Level3.net [4.69.137.4
2]
 17     *        *      841 ms  ae-3-80.edge1.LosAngeles9.Level3.net [4.69.144.1
38]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

This is an uncapped 4Mb line.
 
Last edited:
feo said:
Something completely buggered.



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

  1     1 ms     1 ms     1 ms  Primary [192.168.0.1]
  2     *      543 ms   528 ms  41-133-98-1.dsl.mweb.co.za [41.133.98.1]
  3   520 ms   516 ms   544 ms  41-86-107-18.mweb.co.za [41.86.107.18]
  4   509 ms   523 ms   532 ms  197-80-2-2.jhb.mweb.co.za [197.80.2.2]
  5   550 ms   527 ms   522 ms  197-80-5-242.jhb.mweb.co.za [197.80.5.242]
  6   538 ms   540 ms   546 ms  TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

  7   540 ms   526 ms     *     vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
  8   537 ms     *      535 ms  196.28.178.66
  9   525 ms   522 ms   536 ms  cte-core-sw2.vwol.net [196.41.144.35]
 10   526 ms   528 ms   541 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Tracing route to cnn-lax-tmp.gslb.vgtf.net [157.166.240.13]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  Primary [192.168.0.1]
  2   515 ms   504 ms   504 ms  41-133-98-1.dsl.mweb.co.za [41.133.98.1]
  3   513 ms   503 ms   489 ms  197-80-4-82.jhb.mweb.co.za [197.80.4.82]
  4   520 ms   512 ms   496 ms  197-80-2-1.jhb.mweb.co.za [197.80.2.1]
  5   710 ms   681 ms   691 ms  197-80-5-226.jhb.mweb.co.za [197.80.5.226]
  6   714 ms   707 ms   698 ms  pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
  7   688 ms   698 ms   685 ms  176.67.177.131
  8   683 ms   665 ms   680 ms  xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
  9   824 ms   810 ms     *     vl-3604-ve-228.csw2.London1.Level3.net [4.69.166
.157]
 10   825 ms   827 ms   827 ms  ae-59-224.ebr2.London1.Level3.net [4.69.153.141]

 11     *      812 ms   847 ms  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

 12   834 ms   813 ms   842 ms  ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]

 13   838 ms   847 ms   849 ms  ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45]

 14   838 ms   827 ms   851 ms  4.69.135.185
 15   832 ms   852 ms   828 ms  ae-2-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]

 16   839 ms   823 ms   823 ms  ae-83-83.csw3.LosAngeles1.Level3.net [4.69.137.4
2]
 17     *        *      841 ms  ae-3-80.edge1.LosAngeles9.Level3.net [4.69.144.1
38]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

This is an uncapped 4Mb line.
Click to expand...

Hi feo

Your 2nd hop is very high which usually points to a congested exchange issue.

Have you brought the above results to the attention of Telkom? Please also see following link for more insight regarding congestion: http://mybroadband.co.za/news/adsl/82251-how-to-test-for-adsl-exchange-congestion.html

I have refreshed your MWEB account.
 
MWEB Guy said:
Hi feo

Your 2nd hop is very high which usually points to a congested exchange issue.

Have you brought the above results to the attention of Telkom? Please also see following link for more insight regarding congestion: http://mybroadband.co.za/news/adsl/82251-how-to-test-for-adsl-exchange-congestion.html

I have refreshed your MWEB account.
Click to expand...

My internet has been fine up until today so I doubt it's a congested exchange (things can't go pear shaped like this overnight).

No, I haven't contacted Telkom yet. Will you be able log something on my behalf or do I need to do that myself?
 
feo said:
My internet has been fine up until today so I doubt it's a congested exchange (things can't go pear shaped like this overnight).

No, I haven't contacted Telkom yet. Will you be able log something on my behalf or do I need to do that myself?
Click to expand...


Hi feo

You'll need to log it with Telkom directly as your ADSL line is with them.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X