MWEB Uncapped Subscribers Feedback

[Kosmik]

Hi Mephisto_Helix

What do you experience with only your browsing running? Do you connection drop while gaming?

Kind regards
MWEB Operations

Yes, steam client disconnects and BFBC2 can't connect to ea. Look at the final continous ping, it actually fails, times out at one stage.

Here look at this:

tracert www.mybroadband.co.za

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

1 2 ms 1 ms 1 ms 192.168.2.1
2 11 ms 11 ms 10 ms 41-133-66-1.dsl.mweb.co.za [41.133.66.1]
3 25 ms 25 ms 25 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 23 ms 31 ms 163 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 46 ms 27 ms 28 ms TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 25 ms 25 ms 25 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
7 29 ms 57 ms 25 ms static161-134.netactive.co.za [196.22.161.134]
8 27 ms 27 ms 26 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

9 26 ms 26 ms 26 ms 196.44.31.99
10 26 ms 43 ms 26 ms 196.30.1.21
11 25 ms 25 ms 24 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 25 ms 25 ms 24 ms 196.30.213.108
13 28 ms 27 ms 27 ms 41.72.136.53
14 38 ms 25 ms 62 ms mybroadband.co.za [41.203.21.137]

Trace complete.

ping www.mybroadband.co.za

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52

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

ping www.mybroadband.co.za

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52

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

ping www.mybroadband.co.za

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=144ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52

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

ping www.mybroadband.co.za

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=27ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52

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

ping www.mybroadband.co.za /t

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=27ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=42ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=30ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=28ms TTL=52
Reply from 41.203.21.137: bytes=32 time=48ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=27ms TTL=52
Reply from 41.203.21.137: bytes=32 time=144ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=61ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=29ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=33ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=39ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=26ms TTL=52
Reply from 41.203.21.137: bytes=32 time=28ms TTL=52
Reply from 41.203.21.137: bytes=32 time=31ms TTL=52
Reply from 41.203.21.137: bytes=32 time=30ms TTL=52
Reply from 41.203.21.137: bytes=32 time=27ms TTL=52
Reply from 41.203.21.137: bytes=32 time=25ms TTL=52
Reply from 41.203.21.137: bytes=32 time=35ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=38ms TTL=52
Reply from 41.203.21.137: bytes=32 time=34ms TTL=52
Reply from 41.203.21.137: bytes=32 time=31ms TTL=52
Reply from 41.203.21.137: bytes=32 time=47ms TTL=52
Reply from 41.203.21.137: bytes=32 time=30ms TTL=52
Reply from 41.203.21.137: bytes=32 time=33ms TTL=52
Reply from 41.203.21.137: bytes=32 time=48ms TTL=52
Reply from 41.203.21.137: bytes=32 time=112ms TTL=52
Reply from 41.203.21.137: bytes=32 time=65ms TTL=52
Reply from 41.203.21.137: bytes=32 time=84ms TTL=52
Reply from 41.203.21.137: bytes=32 time=38ms TTL=52
Reply from 41.203.21.137: bytes=32 time=68ms TTL=52
Reply from 41.203.21.137: bytes=32 time=115ms TTL=52
Reply from 41.203.21.137: bytes=32 time=71ms TTL=52
Reply from 41.203.21.137: bytes=32 time=31ms TTL=52
Reply from 41.203.21.137: bytes=32 time=48ms TTL=52
Reply from 41.203.21.137: bytes=32 time=197ms TTL=52
Reply from 41.203.21.137: bytes=32 time=98ms TTL=52
Reply from 41.203.21.137: bytes=32 time=121ms TTL=52
Reply from 41.203.21.137: bytes=32 time=143ms TTL=52
Reply from 41.203.21.137: bytes=32 time=165ms TTL=52
Reply from 41.203.21.137: bytes=32 time=393ms TTL=52
Reply from 41.203.21.137: bytes=32 time=415ms TTL=52
Reply from 41.203.21.137: bytes=32 time=130ms TTL=52
Reply from 41.203.21.137: bytes=32 time=154ms TTL=52
Reply from 41.203.21.137: bytes=32 time=175ms TTL=52
Reply from 41.203.21.137: bytes=32 time=403ms TTL=52
Reply from 41.203.21.137: bytes=32 time=221ms TTL=52
Reply from 41.203.21.137: bytes=32 time=244ms TTL=52
Reply from 41.203.21.137: bytes=32 time=164ms TTL=52
Reply from 41.203.21.137: bytes=32 time=186ms TTL=52
Reply from 41.203.21.137: bytes=32 time=106ms TTL=52
Reply from 41.203.21.137: bytes=32 time=129ms TTL=52
General failure.
General failure.
Request timed out.
General failure.
Request timed out.
Request timed out.
Reply from 41.203.21.137: bytes=32 time=260ms TTL=52
Reply from 41.203.21.137: bytes=32 time=77ms TTL=52
Reply from 41.203.21.137: bytes=32 time=100ms TTL=52
Reply from 41.203.21.137: bytes=32 time=225ms TTL=52
Reply from 41.203.21.137: bytes=32 time=43ms TTL=52
Reply from 41.203.21.137: bytes=32 time=273ms TTL=52
Reply from 41.203.21.137: bytes=32 time=191ms TTL=52
Reply from 41.203.21.137: bytes=32 time=318ms TTL=52
Reply from 41.203.21.137: bytes=32 time=237ms TTL=52
Reply from 41.203.21.137: bytes=32 time=258ms TTL=52
Reply from 41.203.21.137: bytes=32 time=383ms TTL=52
Reply from 41.203.21.137: bytes=32 time=407ms TTL=52

Ping statistics for 41.203.21.137:
Packets: Sent = 95, Received = 89, Lost = 6 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 415ms, Average = 95ms

 

[Kosmik]

Hmm ok, one thing I have done is move the nic ( wireless ) to a dif usb port. Pings seem better now so maybe that was my issue. I'll keep a trace running and check.

 

[MWEBHelp]

Just browsing - came to a standstill, no traffic, twice for about 5mins each time and then just resumed. This also happened yesterday for roughly 25 minutes, the same time as everyone else noticed it.

Gaming - I don't even bother because the ping is useless to play with. A few weeks ago it would 999 and disconnect/drop but now it's just high ping that happens exactly like the traffic interruption.

Hi Mephisto_Helix

We experienced a slight dip in traffic yesterday, please monitor and keep me posted. Do you experience this with all games?

Kind regards
MWEB Operations

 

[Mephisto_Helix]

I only play one online atm ..... coz I'm obsessed see


But yeah, I'll keep you posted bru

 

[Kosmik]

Hi Mwebops,

Running a ping loop fine now but I'm stilll getting disconnects from BFBC2 EA. Nothing else is running.

 

[MWEBHelp]

Hi Mwebops,

Running a ping loop fine now but I'm stilll getting disconnects from BFBC2 EA. Nothing else is running.

Hi Kosmik

Thanks for the update, please monitor and keep me posted.

MWEB Operations

 

[cryptic1]

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

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

 

[Kosmik]

Whats with the lag spikes this morning. Plays fine , then wham.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.


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

1 20 ms 2 ms 2 ms 192.168.2.1
2 2103 ms 1210 ms 312 ms 41-133-66-1.dsl.mweb.co.za [41.133.66.1]
3 28 ms 25 ms 26 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
4 30 ms 31 ms 28 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 32 ms 42 ms 44 ms TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 29 ms 28 ms 35 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
7 27 ms 36 ms 33 ms static161-134.netactive.co.za [196.22.161.134]
8 28 ms 30 ms 28 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

9 29 ms 34 ms 38 ms 196.44.31.99
10 29 ms 28 ms 30 ms 196.30.1.21
11 30 ms 31 ms 29 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 29 ms 29 ms 28 ms 196.30.213.108
13 32 ms 31 ms 32 ms 41.72.136.53
14 39 ms 27 ms 28 ms mybroadband.co.za [41.203.21.137]

Trace complete.

 

[MWEBHelp]

Whats with the lag spikes this morning. Plays fine , then wham.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.


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

1 20 ms 2 ms 2 ms 192.168.2.1
2 2103 ms 1210 ms 312 ms 41-133-66-1.dsl.mweb.co.za [41.133.66.1]
3 28 ms 25 ms 26 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
4 30 ms 31 ms 28 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 32 ms 42 ms 44 ms TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 29 ms 28 ms 35 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
7 27 ms 36 ms 33 ms static161-134.netactive.co.za [196.22.161.134]
8 28 ms 30 ms 28 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

9 29 ms 34 ms 38 ms 196.44.31.99
10 29 ms 28 ms 30 ms 196.30.1.21
11 30 ms 31 ms 29 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 29 ms 29 ms 28 ms 196.30.213.108
13 32 ms 31 ms 32 ms 41.72.136.53
14 39 ms 27 ms 28 ms mybroadband.co.za [41.203.21.137]

Trace complete.

Hi Kosmik

Is your experience intermittent? Have you rebooted already?

Kind regards
MWEB Operations

 

[Kosmik]

Intermittent. Played mostly Eve for the afternoon and had no issues but that game is a lot more lag friendly and a fps.I have rebooted, both router and pc at different times. I see others on BF2 also with a similar issue as when I spike the lag counter goes to 600+ and there are a few others as well.

 

[MWEBHelp]

Intermittent. Played mostly Eve for the afternoon and had no issues but that game is a lot more lag friendly and a fps.I have rebooted, both router and pc at different times. I see others on BF2 also with a similar issue as when I spike the lag counter goes to 600+ and there are a few others as well.

Kosmik, are you experiencing these spike only when playing games or on normal browsing as well? Are the others on BF2 also on Mweb account or not, do you perhaps know?

Regards,
MWEB Ops

 

[PurSpyk!!]

Steam downloads once again slow, Steam is set to download from the cpt mweb server, getting 70KB/s on 4 meg line?

 

[MWEBHelp]

Steam downloads once again slow, Steam is set to download from the cpt mweb server, getting 70KB/s on 4 meg line?

Hi PurSpyk,

Please provide me with speedtest results and your Mweb details via PM in order for me to look into this.

Regards,
MWEB Ops

 

[Zord]

So a nice and friendly Telkom Customer support consultant, who was neither, decided to condescendedly speak to me and say that my packet loss isnt related to my line and they have no way of tracing it. So I explain to him that my noise margin on my router which normally sits on 22 is now dropping to 8 and is sitting around 12. This is only when it rains/thunderstorms. Trying to get them to fix my attenuation is a lost cause and I understand that. They just dont care. But how hard is it to just fix the line so it isnt open to the elements? I mean every single time theres a rainstorm/thunderstorm, the internet is unusable. I cant download, I cant browse webpages, uploads fail due to connection timing out. What can I do ? I have reported another fault but the aforementioned Telkom consultant pretty much flat out said to me they arent going to fix it, in fact I still havent received an sms stating that they even logged the fault. I really dont know what to do. Please Mweb please help me

 

[MWEBHelp]

So a nice and friendly Telkom Customer support consultant, who was neither, decided to condescendedly speak to me and say that my packet loss isnt related to my line and they have no way of tracing it. So I explain to him that my noise margin on my router which normally sits on 22 is now dropping to 8 and is sitting around 12. This is only when it rains/thunderstorms. Trying to get them to fix my attenuation is a lost cause and I understand that. They just dont care. But how hard is it to just fix the line so it isnt open to the elements? I mean every single time theres a rainstorm/thunderstorm, the internet is unusable. I cant download, I cant browse webpages, uploads fail due to connection timing out. What can I do ? I have reported another fault but the aforementioned Telkom consultant pretty much flat out said to me they arent going to fix it, in fact I still havent received an sms stating that they even logged the fault. I really dont know what to do. Please Mweb please help me

Good Morning Zord

Please see the inbox message I have sent you.

Kind regards,
MWEB Ops

 

[Prof.Merlin]

I must say i am not to impressed with mweb uncapped.

I have had it since 1st march. Downloading files over http or ftp gives me more or less full speed. But torrents i do not get more than 10k/s on a 4mbit uncapped account. I have now tried 4 torrents and they all have more than enough seeds.

I am not a heavy downloader. Hardly ever download. But when i want to download something on torrent, i expect to get a lil better than 10k/s.

My cousin used to have a 384k uncapped account running over my line, and he used to get peak speeds through torrent

 

[Gtx Gaming]

have tried after hours? i can easy get 400-500kbs at 12 am and 150kbs in weekends.

running though the day i get about 1.5gb of torrents done.

though i am the only one on my line.

 

[Prof.Merlin]

Yup tried after hours as well. I have had 8 gig torrent that i started last sunday. It is now on 43%

 

[Gtx Gaming]

damn :/

i did 8gb file last night no probs, did you change settings to accept tad more connections, as you never connect to all peers, sometimes you get pretty crappy ones

 

[MWEBHelp]

I must say i am not to impressed with mweb uncapped.

I have had it since 1st march. Downloading files over http or ftp gives me more or less full speed. But torrents i do not get more than 10k/s on a 4mbit uncapped account. I have now tried 4 torrents and they all have more than enough seeds.

I am not a heavy downloader. Hardly ever download. But when i want to download something on torrent, i expect to get a lil better than 10k/s.

My cousin used to have a 384k uncapped account running over my line, and he used to get peak speeds through torrent

Yup tried after hours as well. I have had 8 gig torrent that i started last sunday. It is now on 43%

Good Morning Prof.Merlin

Are you only encountering problems when downloading torrents? Which sites are you downloading from?

Kind regards,
MWEB Ops