MWEB Uncapped ADSL Feedback - Part 3

@dslmweb

Download Speed: 3628 kbps (453.5 KB/sec transfer rate)
Upload Speed: 199 kbps (24.9 KB/sec transfer rate)
Latency: 23 ms
2014/09/24, 7:33:04 AM


guest@telkom

Download Speed: 6968 kbps (871 KB/sec transfer rate)
Upload Speed: 539 kbps (67.4 KB/sec transfer rate)
Latency: 15 ms
2014/09/24, 7:29:56 AM

I have checked your account and I see that there is a line fault logged to Telkom to investigate this
 
How can it be a line fault if one account gives near 100% of the expected speed, and another doesnt? Explain that to me please. It has now once again been escalated to your "specialists".

Last Result:
Download Speed: 442 kbps (55.3 KB/sec transfer rate)
Upload Speed: 162 kbps (20.3 KB/sec transfer rate)
Latency: 1502 ms
2014/09/24, 8:28:20 AM

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 1191 ms 1258 ms 1383 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 1780 ms 1564 ms 731 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 450 ms 451 ms 549 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 631 ms 671 ms 707 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.225]
6 912 ms 1098 ms 1163 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]
7 1372 ms 1490 ms 1196 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 947 ms 946 ms 859 ms 196.28.178.66
9 1396 ms 1620 ms 1938 ms cte-core-sw2.vwol.net [196.41.144.35]
10 1782 ms 660 ms 1553 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Last edited:
How can it be a line fault if one account gives near 100% of the expected speed, and another doesnt? Explain that to me please. It has now once again been escalated to your "specialists".

Last Result:
Download Speed: 442 kbps (55.3 KB/sec transfer rate)
Upload Speed: 162 kbps (20.3 KB/sec transfer rate)
Latency: 1502 ms
2014/09/24, 8:28:20 AM

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 1191 ms 1258 ms 1383 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 1780 ms 1564 ms 731 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 450 ms 451 ms 549 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 631 ms 671 ms 707 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.225]
6 912 ms 1098 ms 1163 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]
7 1372 ms 1490 ms 1196 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 947 ms 946 ms 859 ms 196.28.178.66
9 1396 ms 1620 ms 1938 ms cte-core-sw2.vwol.net [196.41.144.35]
10 1782 ms 660 ms 1553 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Thanks, yes this certainly looks like a congested exchange
 
How can it be a line fault if one account gives near 100% of the expected speed, and another doesnt? Explain that to me please. It has now once again been escalated to your "specialists".

Just because another account works does not eliminate there being a line fault. Every time you make a new connection to another ISP, you effectively undergo a port reset, which relieves some line-related problems, particularly congestion, temporarily. Also, AFAIK you're using the Telkom Guest account to test? Rather get a free GB from another ISP to test with. Keep it in your router for as long as it lasts so that it's not simply a quick reconnection to do a Speedtest.

Last Result:
Download Speed: 442 kbps (55.3 KB/sec transfer rate)
Upload Speed: 162 kbps (20.3 KB/sec transfer rate)
Latency: 1502 ms
2014/09/24, 8:28:20 AM

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 1191 ms 1258 ms 1383 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 1780 ms 1564 ms 731 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 450 ms 451 ms 549 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 631 ms 671 ms 707 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.225]
6 912 ms 1098 ms 1163 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]
7 1372 ms 1490 ms 1196 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 947 ms 946 ms 859 ms 196.28.178.66
9 1396 ms 1620 ms 1938 ms cte-core-sw2.vwol.net [196.41.144.35]
10 1782 ms 660 ms 1553 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Definitely a line fault/congestion, as suspected in the beginning.
 
Another day - Targeted port shaping still in full swing

Well, it's another bright and sunny day in Durban and I see that we still have inexplicable port shaping / throttling on port 563 SSL.

Still no word from MWeb technical on why this is happening.

This is starting to become very annoying now.

I should NOT be seeing this kind of shaping for over 75% of any given day.

At the very least I would like an explanation from MWeb and a committed response acknowledging that they are doing something to cause this.

If not them, then who ? Everything else works perfectly, only NewsGroup related ports appear to be affected, and not late at night. It doesn't take a genius to work out that somebody is time boxing my connection heavily.
 
Well, it's another bright and sunny day in Durban and I see that we still have inexplicable port shaping / throttling on port 563 SSL.

Still no word from MWeb technical on why this is happening.

This is starting to become very annoying now.

I should NOT be seeing this kind of shaping for over 75% of any given day.

At the very least I would like an explanation from MWeb and a committed response acknowledging that they are doing something to cause this.

If not them, then who ? Everything else works perfectly, only NewsGroup related ports appear to be affected, and not late at night. It doesn't take a genius to work out that somebody is time boxing my connection heavily.


Hi send me a PM with your MWEB details please
 
Just because another account works does not eliminate there being a line fault. Every time you make a new connection to another ISP, you effectively undergo a port reset, which relieves some line-related problems, particularly congestion, temporarily. Also, AFAIK you're using the Telkom Guest account to test? Rather get a free GB from another ISP to test with. Keep it in your router for as long as it lasts so that it's not simply a quick reconnection to do a Speedtest.



Definitely a line fault/congestion, as suspected in the beginning.

Ahh, blame the exchange again, shall we. Still leaves me with a service that I cant use. 7 days out of the last 10.... and it goes on and on. How can they "recreate my account" and it's perfect for 3 days, then all of a sudden all dead again? You explain that to me.
 
Ahh, blame the exchange again, shall we. Still leaves me with a service that I cant use. 7 days out of the last 10.... and it goes on and on. How can they "recreate my account" and it's perfect for 3 days, then all of a sudden all dead again? You explain that to me.

That's why you need another account with a few gigs (not Telkom Guest) in your router for a few days. Basically what happens is an account is refreshed/reauthenticated, you get a port reset and new IP, and the issue appears to go away for minutes/hours/days, until it comes back. Sounds like what is happening to you. So blame Telkom absolutely, but not MWEB.
 
Whats this news about the News server?
Just got an email that they are shutting it down "due to the extremely low uptake on the service"...
The reason I stopped using it was because of the extremely low reliability of the service. Don't get me wrong, it started off great. And then it just went downhill. Went with a local service instead.

Who knew it was through GigaNews? If the locally hosted MWEB news server was anything to go by, I don't even want to think about the discounted giganews packages they're offering, which are hosted internationally. Or am I wrong, are the Giganews packages actually worth it?
 
Sigh, back to normal for now. I dont get this, unless Telkom did something:

Last Result:
Download Speed: 8741 kbps (1092.6 KB/sec transfer rate)
Upload Speed: 856 kbps (107 KB/sec transfer rate)
Latency: 12 ms
2014/09/24, 1:32:55 PM

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 7 ms 9 ms 14 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 13 ms 15 ms 13 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 10 ms 10 ms 9 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 44 ms 45 ms 45 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.225]
6 44 ms 40 ms 61 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]
7 37 ms 38 ms 37 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 37 ms 38 ms 37 ms 196.28.178.66
9 96 ms 39 ms 38 ms cte-core-sw2.vwol.net [196.41.144.35]
10 39 ms 37 ms 37 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Beginning to get a bit frustrated...

My Mweb account is hating on downloading anything that is P2P. I can never seem to download torrents anymore with my Mweb account.. I lose all peers and basically just end up getting stuck at connecting/searching for peers on uTorrent.. >_>

But Telkom account is fine.. I've made sure ports are forwarded, I've tried proxies, I've changed ports, I've tried a different torrent program...

Also my IRC connection to IRC servers is also problematic with Mweb account. I either cannot connect to an IRC server.. Or I get disconnected after about 2 minutes.. So in short.. What is going on?
 
Beginning to get a bit frustrated...

My Mweb account is hating on downloading anything that is P2P. I can never seem to download torrents anymore with my Mweb account.. I lose all peers and basically just end up getting stuck at connecting/searching for peers on uTorrent.. >_>

But Telkom account is fine.. I've made sure ports are forwarded, I've tried proxies, I've changed ports, I've tried a different torrent program...

Leave them running overnight, they'll be done by morning. p2p receives lowest priority, and usually opens up between 19h00 and 00h00.
 
Leave them running overnight, they'll be done by morning. p2p receives lowest priority, and usually opens up between 19h00 and 00h00.

Im aware of this. But it's gotten to the point that it it's like.. completely dead regardless of time.
 
and Mweb in Durban once more is poop .....



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=156ms TTL=119
Reply from 196.2.63.110: bytes=32 time=153ms TTL=119
Reply from 196.2.63.110: bytes=32 time=163ms TTL=119
Reply from 196.2.63.110: bytes=32 time=163ms 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 = 153ms, Maximum = 163ms, Average = 158ms

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 6 ms 6 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 119 ms 118 ms 120 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 124 ms 126 ms 125 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 162 ms 162 ms 161 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
5 177 ms 171 ms 170 ms 196.28.178.66
6 154 ms 157 ms 157 ms cte-core-sw2.vwol.net [196.41.144.35]
7 156 ms 156 ms 158 ms www.mweb.co.za [196.2.63.110]

Trace complete.


Other accounts are fine all round .....
 
Hmm.. so I'm on 6mb standard uncapped

You have used 132.44 GB so far this month.

Last Session: 24 September, 2014, 16:47:58

Connection status: Unthrottled

Your total usage for the past 30 days: 153.99 GB

I assumed I'd be throttled by now, lucky?
 
Hmm.. so I'm on 6mb standard uncapped



I assumed I'd be throttled by now, lucky?

Very! ;)

Perhaps the end of MWEB Usenet is helping you out.

attachment.php
 
Since the news server is done for, will you allow me to use SSL to be able to connect to my backup server from midnight to 6am or am I moving ISP's soon?
 
Since the news server is done for, will you allow me to use SSL to be able to connect to my backup server from midnight to 6am or am I moving ISP's soon?

gotta say, if the free news from Mweb is stopping, it's done for as a product. Time to start shopping round.
 
Top
Sign up to the MyBroadband newsletter
X