MWEB Uncapped ADSL Feedback - Part 3

giggity said:
Posting this for a friend on Mweb 1mbps uncapped (I think it's 2mbps now).

Code: 
  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2    27 ms    37 ms    29 ms  41-133-48-1.dsl.mweb.co.za [41.133.48.1]
  3   242 ms   234 ms   191 ms  197-82-5-250.dbn.mweb.co.za [197.82.5.250]
  4   120 ms   139 ms   171 ms  197-82-2-3.dbn.mweb.co.za [197.82.2.3]
  5   302 ms   224 ms   215 ms  176.67.177.227
  6   213 ms   210 ms   232 ms  ldn-b5-link.telia.net [62.115.13.13]
  7   426 ms   285 ms   239 ms  cloudflare-ic-154357-ldn-b5.c.telia.net [80.239.161.246]
  8   214 ms     *      230 ms  141.101.114.14

Trace complete.

He's getting huge ping fluctuations. It looks like the Durban Mweb.
Click to expand...

Afternoon, where are you tracing to?
 
Tested my Line with Zertop's line tool and this is the results.
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 41.132.72.1 with 32 bytes of data:
Reply from 41.132.72.1: bytes=32 time=8ms TTL=254
Reply from 41.132.72.1: bytes=32 time=8ms TTL=254
Reply from 41.132.72.1: bytes=32 time=8ms TTL=254
Reply from 41.132.72.1: bytes=32 time=9ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254
Reply from 41.132.72.1: bytes=32 time=9ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254
Reply from 41.132.72.1: bytes=32 time=8ms TTL=254
Reply from 41.132.72.1: bytes=32 time=46ms TTL=254
Reply from 41.132.72.1: bytes=32 time=10ms TTL=254
Reply from 41.132.72.1: bytes=32 time=8ms TTL=254
Reply from 41.132.72.1: bytes=32 time=8ms TTL=254
Reply from 41.132.72.1: bytes=32 time=9ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254
Reply from 41.132.72.1: bytes=32 time=9ms TTL=254
Reply from 41.132.72.1: bytes=32 time=9ms TTL=254
Reply from 41.132.72.1: bytes=32 time=41ms TTL=254
Reply from 41.132.72.1: bytes=32 time=69ms TTL=254
Reply from 41.132.72.1: bytes=32 time=76ms TTL=254
Reply from 41.132.72.1: bytes=32 time=57ms TTL=254
Reply from 41.132.72.1: bytes=32 time=53ms TTL=254
Reply from 41.132.72.1: bytes=32 time=17ms TTL=254
Reply from 41.132.72.1: bytes=32 time=8ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254
Reply from 41.132.72.1: bytes=32 time=8ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254
Reply from 41.132.72.1: bytes=32 time=7ms TTL=254

Ping statistics for 41.132.72.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 76ms, Average = 18ms

Fri 03/28/2014 21:41:56.03

Still get multiple DSL disconnects after 9 at night.
 
MWEB Guy definite problems with MWEB account.

Started getting lagg from just before 4 on online gaming and general Youtube.
Switched to Axxess test account and everything is running as it should.
 
Vl@d said:
MWEB Guy definite problems with MWEB account.

Started getting lagg from just before 4 on online gaming and general Youtube.
Switched to Axxess test account and everything is running as it should.
Click to expand...

provide me with a trace route to a local and international site
 
Currently on Axxess account playing online in Guildwars 2.
Will have to send when I'm back on Mweb.
But haven't had reply on the traceroutes sent a few nights ago.
Problems started when I switched to the standard 6mb account
 
Taceroute on Axxess
C:\Users\Vlad>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 6 ms 5 ms 5 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.
1]
3 22 ms 8 ms 17 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 9 ms 8 ms 8 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 9 ms 8 ms 8 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 13 ms 8 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 8 ms 8 ms 108 ms 196.44.0.72
8 9 ms 10 ms 9 ms postfix.wipronet.co.za [196.22.161.133]
9 30 ms 30 ms 30 ms 197-80-7-34.jhb.mweb.co.za [197.80.7.34]
10 35 ms 34 ms 35 ms tengige0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

11 31 ms 31 ms 31 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
12 29 ms 29 ms 28 ms 196.28.178.66
13 28 ms 30 ms 28 ms cte-core-sw2.vwol.net [196.41.144.35]
14 35 ms 28 ms 28 ms www.mweb.co.za [196.2.63.110]

Trace complete.



C:\Users\Vlad>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 5 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.
1]
3 8 ms 9 ms 8 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 10 ms 8 ms 9 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 9 ms 8 ms 11 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 9 ms 8 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 178 ms 178 ms 177 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83
]
8 175 ms 173 ms 173 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
9 * * * Request timed out.
10 174 ms 174 ms 174 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
11 181 ms 179 ms 180 ms 132.185.255.165
12 174 ms 174 ms 173 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Trace complete.

On Mweb

C:\Users\Vlad>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 5 ms 6 ms 6 ms 41-132-72-1.dsl.mweb.co.za [41.132.72.1]
3 7 ms 7 ms 8 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 8 ms 8 ms 8 ms vl-92.vic-hscore-2.mweb.co.za [197.80.2.2]
5 35 ms 35 ms 35 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [197.80.5.24
2]
6 42 ms 50 ms 35 ms tengige0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

7 32 ms 32 ms 32 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
8 32 ms 32 ms 32 ms 196.28.178.66
9 33 ms 33 ms 32 ms cte-core-sw2.vwol.net [196.41.144.35]
10 32 ms 33 ms 32 ms www.mweb.co.za [196.2.63.110]

Trace complete.


C:\Users\Vlad>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 158 ms 64 ms * 41-132-72-1.dsl.mweb.co.za [41.132.72.1]
3 14 ms 8 ms 7 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 8 ms 8 ms 8 ms vl-92.vic-hscore-2.mweb.co.za [197.80.2.2]
5 187 ms * 185 ms tengig0-7-0-2.12.vic-p-1.mweb.co.za [197.80.5.24
1]
6 190 ms 186 ms 187 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
7 188 ms 187 ms 186 ms 176.67.177.131
8 186 ms 186 ms 186 ms ldn-b5-link.telia.net [62.115.13.13]
9 186 ms 187 ms 186 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
10 * * * Request timed out.
11 184 ms 184 ms 184 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 184 ms 184 ms 184 ms 132.185.255.149
13 184 ms 184 ms 184 ms fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.
 
Vl@d said:
Taceroute on Axxess
C:\Users\Vlad>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 6 ms 5 ms 5 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.
1]
3 22 ms 8 ms 17 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 9 ms 8 ms 8 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 9 ms 8 ms 8 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 13 ms 8 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 8 ms 8 ms 108 ms 196.44.0.72
8 9 ms 10 ms 9 ms postfix.wipronet.co.za [196.22.161.133]
9 30 ms 30 ms 30 ms 197-80-7-34.jhb.mweb.co.za [197.80.7.34]
10 35 ms 34 ms 35 ms tengige0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

11 31 ms 31 ms 31 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
12 29 ms 29 ms 28 ms 196.28.178.66
13 28 ms 30 ms 28 ms cte-core-sw2.vwol.net [196.41.144.35]
14 35 ms 28 ms 28 ms www.mweb.co.za [196.2.63.110]

Trace complete.



C:\Users\Vlad>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 5 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.
1]
3 8 ms 9 ms 8 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 10 ms 8 ms 9 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 9 ms 8 ms 11 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 9 ms 8 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 178 ms 178 ms 177 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83
]
8 175 ms 173 ms 173 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
9 * * * Request timed out.
10 174 ms 174 ms 174 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
11 181 ms 179 ms 180 ms 132.185.255.165
12 174 ms 174 ms 173 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Trace complete.

On Mweb

C:\Users\Vlad>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 5 ms 6 ms 6 ms 41-132-72-1.dsl.mweb.co.za [41.132.72.1]
3 7 ms 7 ms 8 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 8 ms 8 ms 8 ms vl-92.vic-hscore-2.mweb.co.za [197.80.2.2]
5 35 ms 35 ms 35 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [197.80.5.24
2]
6 42 ms 50 ms 35 ms tengige0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

7 32 ms 32 ms 32 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
8 32 ms 32 ms 32 ms 196.28.178.66
9 33 ms 33 ms 32 ms cte-core-sw2.vwol.net [196.41.144.35]
10 32 ms 33 ms 32 ms www.mweb.co.za [196.2.63.110]

Trace complete.


C:\Users\Vlad>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 158 ms 64 ms * 41-132-72-1.dsl.mweb.co.za [41.132.72.1]
3 14 ms 8 ms 7 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 8 ms 8 ms 8 ms vl-92.vic-hscore-2.mweb.co.za [197.80.2.2]
5 187 ms * 185 ms tengig0-7-0-2.12.vic-p-1.mweb.co.za [197.80.5.24
1]
6 190 ms 186 ms 187 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
7 188 ms 187 ms 186 ms 176.67.177.131
8 186 ms 186 ms 186 ms ldn-b5-link.telia.net [62.115.13.13]
9 186 ms 187 ms 186 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
10 * * * Request timed out.
11 184 ms 184 ms 184 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 184 ms 184 ms 184 ms 132.185.255.149
13 184 ms 184 ms 184 ms fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.
Click to expand...

Thanks for that, I have escalated this to our specialists to investigate and contact you.

Your ref number is 1391736
 
Hey my net just died, came back to lag

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

1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]
2 9 ms 9 ms 8 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 10 ms 9 ms 9 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 10 ms 10 ms 9 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 17 ms 17 ms 10 ms 196.28.178.66
6 323 ms 234 ms 263 ms cte-core-sw2.vwol.net [196.41.144.35]
7 244 ms 280 ms 132 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
rpdblu said:
Hey my net just died, came back to lag

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

1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]
2 9 ms 9 ms 8 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 10 ms 9 ms 9 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 10 ms 10 ms 9 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 17 ms 17 ms 10 ms 196.28.178.66
6 323 ms 234 ms 263 ms cte-core-sw2.vwol.net [196.41.144.35]
7 244 ms 280 ms 132 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

Hi rpdblu send me a PM with your MWEB details.
 
MWEB dies the comes back continuously anyone else experiencing it ? And when its back the latency is insane
 
Been my problem the last 2 weeks with no resolve as yet.
 
Fayera said:
MWEB dies the comes back continuously anyone else experiencing it ? And when its back the latency is insane
Click to expand...

Morning Fayera

Please PM me the MWEB email address or username so that I can have a look from our side.

When you say dies, does the connection drop?
 
Mweb Guy spoke to two other friends of mine also Mweb users which have the same problem with dsl connection dropping on the Mweb accounts while other accounts is stable.
One is in the same town as me and the other is in Centurion.
 
Vl@d said:
Mweb Guy spoke to two other friends of mine also Mweb users which have the same problem with dsl connection dropping on the Mweb accounts while other accounts is stable.
One is in the same town as me and the other is in Centurion.
Click to expand...

Morning Vl@d

I checked the account and noticed our technical team will be contacting you. There is also a line fault open with Telkom. We are still in contact with them regarding this and we will provide you feedback as we receive information.
 
No Mweb Guy no contact from your technical team. Telkom sent a technician out for the line didn't find anything.
Everything was running fine till just after 19:30 when lagg on online gaming became unbearable
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X