MWEB Uncapped ADSL Feedback - Part 3

International seems to be terribly slow here in Durban, Westville. Even loading Speed Test times out. :(
 
International seems to be terribly slow here in Durban, Westville. Even loading Speed Test times out. :(

Evening, we have no reported international outages at the moment.

Is all international traffic affected?

Are you connected to the router via a wireless or cable connection?
 
Anyone else having trouble loading webpages ?
I cant even open Google anymore.
My Mweb 6Mb Uncapped Premium is worse than dial up at the moment.
 
And then it is suddenly back to normal... And then it goes back to being unusable again... So irritating.
 
Evening, we have no reported international outages at the moment.

Is all international traffic affected?

Are you connected to the router via a wireless or cable connection?

Hi MWEB Guy! For the past 3 weeks I've been experiencing constant disconnect's with International access being cut off after 6pm for a few minutes and then again at 10pm for most of the night. This usually happens on weekends. My ADSL disconnects often on a Tuesday and Thursday and when its back, my International is slow.

I've had Telkom over twice now and they've fiddled around at the exchange, stating that everything is fine on their end.
 
Hi MWEB Guy! For the past 3 weeks I've been experiencing constant disconnect's with International access being cut off after 6pm for a few minutes and then again at 10pm for most of the night. This usually happens on weekends. My ADSL disconnects often on a Tuesday and Thursday and when its back, my International is slow.

I've had Telkom over twice now and they've fiddled around at the exchange, stating that everything is fine on their end.

I have now escalated this to our specialists to investigate and to make contact with you.

Your ref number for this is 1538496
 
I have no clue what changed on the MWEB network but my latency went from 60ms to 24ms. MWEB guy please ask your techies not to touch.... It is looking good again after months of terrible latency. And it is not my line or exchange otherwise my afrihost accounts would be doing the same.
 
Ye, every bloody evening around the same time I'm having Mweb issues and other networks (apart from Vox) are fine. I'm willing to bet it's at the Dinx again.

Mweb -

C:\Users\Andre>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=129ms TTL=119
Reply from 196.2.63.110: bytes=32 time=129ms TTL=119
Reply from 196.2.63.110: bytes=32 time=128ms TTL=119
Reply from 196.2.63.110: bytes=32 time=138ms TTL=119

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

C:\Users\Andre>tracert mweb.co.za

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

1 5 ms 5 ms 5 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 98 ms 96 ms 97 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 92 ms 90 ms 91 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 134 ms 132 ms 132 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
5 143 ms 140 ms 141 ms 196.28.178.66
6 141 ms 134 ms 134 ms cte-core-sw2.vwol.net [196.41.144.35]
7 135 ms 138 ms 140 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Andre>ping bbc.co.uk

Pinging bbc.co.uk [212.58.246.103] with 32 bytes of data:
Reply from 212.58.246.103: bytes=32 time=295ms TTL=49
Reply from 212.58.246.103: bytes=32 time=294ms TTL=49
Reply from 212.58.246.103: bytes=32 time=294ms TTL=49
Reply from 212.58.246.103: bytes=32 time=299ms TTL=49

Ping statistics for 212.58.246.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 294ms, Maximum = 299ms, Average = 295ms

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

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

1 5 ms 5 ms 5 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 102 ms 102 ms 105 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 107 ms 107 ms 103 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 294 ms 293 ms 287 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
5 277 ms 276 ms 274 ms ldn-b5-link.telia.net [62.115.13.13]
6 271 ms 273 ms 273 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
7 * * * Request timed out.
8 * * * Request timed out.
9 292 ms 298 ms 297 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 284 ms 281 ms 282 ms 132.185.255.165
11 269 ms 269 ms 270 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Trace complete.


WA -

C:\Users\Andre>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=38ms TTL=115
Reply from 196.2.63.110: bytes=32 time=38ms TTL=115
Reply from 196.2.63.110: bytes=32 time=38ms TTL=115
Reply from 196.2.63.110: bytes=32 time=37ms TTL=115

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

C:\Users\Andre>tracert mweb.co.za

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

1 5 ms 5 ms 5 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.
1]
2 7 ms 8 ms 7 ms cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.2
45]
3 7 ms 7 ms 6 ms 196.26.210.200
4 7 ms 7 ms 7 ms mi-za-umh-p7-ten-0-0-1-1.ip.isnet.net [168.209.9
3.239]
5 18 ms 19 ms 19 ms 168.209.255.208
6 17 ms 17 ms 16 ms core2a-bry-gi1-0-0.ip.isnet.net [168.209.218.2]

7 17 ms 17 ms 17 ms core2a-pkl-te1-2.isnet.net [168.209.100.241]
8 17 ms 17 ms 18 ms 168.209.1.170
9 22 ms 17 ms 17 ms mweb-2.jinx.net.za [196.223.14.32]
10 41 ms 39 ms 46 ms tengig-0-7-0-3-vic-p-2.mweb.co.za [197.80.7.98]

11 42 ms 39 ms 38 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]

12 37 ms 37 ms 37 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
13 41 ms 38 ms 38 ms 196.28.178.66
14 37 ms 39 ms 38 ms cte-core-sw2.vwol.net [196.41.144.35]
15 39 ms 37 ms 37 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Andre>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data:
Reply from 212.58.244.18: bytes=32 time=199ms TTL=50
Reply from 212.58.244.18: bytes=32 time=199ms TTL=50
Reply from 212.58.244.18: bytes=32 time=199ms TTL=50
Reply from 212.58.244.18: bytes=32 time=199ms TTL=50

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

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

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

1 5 ms 5 ms 5 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.
1]
2 7 ms 7 ms 7 ms cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.2
45]
3 7 ms 7 ms 7 ms 196.26.210.200
4 16 ms 17 ms 16 ms 196.38.74.176
5 19 ms 19 ms 19 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]

6 194 ms 195 ms 195 ms 168.209.246.3
7 199 ms 199 ms 198 ms bbc-linx.pr01.rbsov.bbc.co.uk [195.66.236.103]
8 * * * Request timed out.
9 * * * Request timed out.
10 193 ms 193 ms 191 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 200 ms 200 ms 199 ms 132.185.255.149
12 199 ms 198 ms 199 ms fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.
 
Ye, every bloody evening around the same time I'm having Mweb issues and other networks (apart from Vox) are fine. I'm willing to bet it's at the Dinx again.

Mweb -




WA -


Hi Has this managed to improve ?
 
Hi Mwebguy

Please check out my line as per PM.

Mweb-

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tony>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=650ms TTL=119
Reply from 196.2.63.110: bytes=32 time=600ms TTL=119
Reply from 196.2.63.110: bytes=32 time=626ms TTL=119
Reply from 196.2.63.110: bytes=32 time=589ms TTL=119

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

C:\Users\Tony>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 myrouter.Home [192.168.1.1]
2 517 ms 471 ms 499 ms 41-133-80-1.dsl.mweb.co.za [41.133.80.1]
3 559 ms 557 ms 564 ms 197-80-96-210.jhb.mweb.co.za [197.80.96.210]
4 503 ms 514 ms 541 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 619 ms 667 ms 498 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 503 ms 539 ms 581 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]

7 556 ms 582 ms 726 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 707 ms 562 ms 509 ms 196.28.178.66
9 539 ms 485 ms 473 ms cte-core-sw2.vwol.net [196.41.144.35]
10 520 ms 580 ms 608 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Tony>ping bbc.co.uk

Pinging bbc.co.uk [212.58.246.104] with 32 bytes of data:
Reply from 212.58.246.104: bytes=32 time=714ms TTL=49
Reply from 212.58.246.104: bytes=32 time=711ms TTL=49
Reply from 212.58.246.104: bytes=32 time=718ms TTL=49
Reply from 212.58.246.104: bytes=32 time=733ms TTL=49

Ping statistics for 212.58.246.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 711ms, Maximum = 733ms, Average = 719ms

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

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

1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]
2 465 ms 540 ms 585 ms 41-133-80-1.dsl.mweb.co.za [41.133.80.1]
3 640 ms 603 ms 502 ms 197-80-96-210.jhb.mweb.co.za [197.80.96.210]
4 577 ms 558 ms 497 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 605 ms * 588 ms tengig-0-0-0-2-11-vic-p-2.mweb.co.za [197.80.5.2
26]
6 690 ms 754 ms 766 ms s2-pos0-3-2-0-pos0-3-0-0.thd-p-1.mweb.co.za [197
.80.5.9]
7 756 ms 746 ms 787 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
8 582 ms 601 ms 659 ms ldn-b5-link.telia.net [62.115.13.13]
9 723 ms 756 ms 732 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
10 * * * Request timed out.
11 * * * Request timed out.
12 611 ms 661 ms 756 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
13 674 ms 660 ms 684 ms 132.185.255.165
14 723 ms 770 ms 776 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]

Trace complete.

C:\Users\Tony>

Afrihost -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tony>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=550ms TTL=115
Request timed out.
Reply from 196.2.63.110: bytes=32 time=372ms TTL=115
Reply from 196.2.63.110: bytes=32 time=475ms TTL=115

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 372ms, Maximum = 550ms, Average = 465ms

C:\Users\Tony>tracert mweb.co.za

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

1 440 ms 417 ms 427 ms 105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
2 497 ms 490 ms 542 ms 41.181.221.250
3 430 ms 555 ms 547 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
4 520 ms 442 ms 402 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
5 468 ms 535 ms 499 ms 196.44.0.74
6 * * 452 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]

7 433 ms 473 ms 532 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
8 530 ms * * vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
9 600 ms 551 ms * 196.28.178.66
10 444 ms 452 ms 514 ms cte-core-sw2.vwol.net [196.41.144.35]
11 395 ms 348 ms * www.mweb.co.za [196.2.63.110]
12 * 561 ms 560 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Tony>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data:
Reply from 212.58.244.18: bytes=32 time=720ms TTL=50
Reply from 212.58.244.18: bytes=32 time=630ms TTL=50
Reply from 212.58.244.18: bytes=32 time=631ms TTL=50
Reply from 212.58.244.18: bytes=32 time=653ms TTL=50

Ping statistics for 212.58.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 630ms, Maximum = 720ms, Average = 658ms

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

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

1 453 ms 467 ms 496 ms 105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
2 553 ms 478 ms * 41.181.221.250
3 * 490 ms 553 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
4 606 ms 577 ms 550 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
5 783 ms 798 ms 742 ms 41.181.180.10
6 838 ms 803 ms 773 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

7 882 ms 962 ms 805 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.15
6]
8 582 ms 612 ms 662 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83
]
9 796 ms 817 ms 796 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
10 * * * Request timed out.
11 * * * Request timed out.
12 713 ms 686 ms 664 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
13 663 ms 732 ms 685 ms 132.185.255.149
14 701 ms 733 ms 723 ms fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.

C:\Users\Tony>
 
Mweb Guy,

It seems you can't access Mweb.co.za from any connection DSL/3G???



Edit: I have been on hold for over 30mins.... is Mweb that busy?

Hi Hummercellc

I checked on my side and I see that there was an issue earlier with browsing to the MWEB home page.
It has since been resolved though and the notice has been removed from the notice board.


Outage Num:22769
MWEB All outage affecting All Regions
MWEB All services in the following area may be Inaccessible : All Regions : Browsing to www.mweb.co.za inaccessible. Engineers are currently investigating.
Start Date:2014-09-10 14:34:18
End Date:2014-09-10 15:01:03
Status:Closed
 
Anyone else in durban having issues?

Been having extremely slow speed since 5pm yesterday.

Websites are barely loading if they load at all.
 
Anyone else in durban having issues?

Been having extremely slow speed since 5pm yesterday.

Websites are barely loading if they load at all.

Hi, are aware of this and our engineers are currently investigating
 
It seems to be nation wide and not just mweb, I have tested openweb, webafrica, vox, axxess, afrihost etc. Can barely browse on all
 
Hmm, my line was also on avg 2mbp slower than normal yesterday around 5pm. Didnt have time to test this morning.
 
Top
Sign up to the MyBroadband newsletter
X