MWEB Uncapped Subscribers Feedback

[Chevron]

My line syncs and all is well, however, I have no internet connection.
What's going on?

Just had that now with browsing this forum.

@mweb ops I'll pm you in a bit.

 

[GingerBeer]

Gingerbeer is right those spikes can be annoying - I find that having a slightly higher ping can often be preferable if it's more stable. Anything sub 100 is really quite playable though.
You must really be a very serious gamer if you're after a sub 20 Gingerbeer - those are practically LAN conditions

As a matter of interest this is what a pingtest to games.saix.net looked like from our 384k testbench in Cape Town a few minutes ago - I certainly wouldn't find it too challenging to get some frags in on that connection!

I play often, but not seriously.
So I see what pings other players
are getting and they tell us what
network they are on.

100ms is definitely not playable if
you want to win anything on the
fast games. I think it's time MWEB
employed some people who
actually play games.

I believe there is only one member
of staff at MWEB who played an
online game in his life and it was
only once.

Compare this to WebAfrica, where
their techies are all playing quite
regularly.

If MWEB is going to compete, then
they need to gain some credibility
with customers and what they do
with the internet.

This probably explains why they take
such a strong line on torrents as well.

 

[TheYak]

Guess I jinxed it again. Downloads are not going any higher than 56k/s. *sigh*

 

[straatkat]

Can anyone tell me more about the mweb newsserver?

 

[Chevron]

Looks like its local too. Just got dropped from local warcraft match.

Any ideas people?

 

[Chevron]

I had a constant ping to google.co.za running in the background and the drops are evident.

Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=438ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=412ms TTL=50
Reply from 64.233.179.104: bytes=32 time=423ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=415ms TTL=50
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=415ms TTL=50
Reply from 64.233.179.104: bytes=32 time=423ms TTL=50
Reply from 64.233.179.104: bytes=32 time=423ms TTL=50
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=412ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=420ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=415ms TTL=50
Reply from 64.233.179.104: bytes=32 time=430ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=426ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=415ms TTL=50
Reply from 64.233.179.104: bytes=32 time=424ms TTL=50
Reply from 64.233.179.104: bytes=32 time=423ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Reply from 64.233.179.104: bytes=32 time=419ms TTL=50
Reply from 64.233.179.104: bytes=32 time=412ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=412ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=420ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=420ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=430ms TTL=50
Reply from 64.233.179.104: bytes=32 time=423ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=419ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=418ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=416ms TTL=50
Reply from 64.233.179.104: bytes=32 time=416ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=416ms TTL=50
Reply from 64.233.179.104: bytes=32 time=417ms TTL=50
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50
Reply from 64.233.179.104: bytes=32 time=416ms TTL=50
Reply from 64.233.179.104: bytes=32 time=412ms TTL=50
Reply from 64.233.179.104: bytes=32 time=417ms TTL=50
Reply from 64.233.179.104: bytes=32 time=475ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=422ms TTL=50
Reply from 64.233.179.104: bytes=32 time=416ms TTL=50
Reply from 64.233.179.104: bytes=32 time=420ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=419ms TTL=50
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=422ms TTL=50
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Reply from 64.233.179.104: bytes=32 time=416ms TTL=50
Reply from 64.233.179.104: bytes=32 time=420ms TTL=50
Reply from 64.233.179.104: bytes=32 time=422ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=418ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50
Reply from 64.233.179.104: bytes=32 time=418ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=404ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=428ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=411ms TTL=50
Reply from 64.233.179.104: bytes=32 time=412ms TTL=50
Reply from 64.233.179.104: bytes=32 time=415ms TTL=50
Reply from 64.233.179.104: bytes=32 time=412ms TTL=50
Reply from 64.233.179.104: bytes=32 time=419ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=416ms TTL=50
Reply from 64.233.179.104: bytes=32 time=404ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50

Ping statistics for 64.233.179.104:
Packets: Sent = 1051, Received = 1016, Lost = 35 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 403ms, Maximum = 499ms, Average = 412ms

 

[MWEBHelp]

@GingerBeer - I think you might be underestimating us a little there

I played Counterstrike, Quake 3 and Starcraft competetively at clan level and attending competitions for many years and was very active in the gaming community administering servers for MWEB long before I was employed by them.

In more recent years I have also played Joint Operations and Battlefield 2 and I have also spent far too much time on the MMO scene. (I have tanked Black Temple in WoW and solo farmed UnderWorld in Guiildwars although Ultima Online remains unchallenged as the best MMO in my book).

I don't get as much time as I would like to game these days, work and my children keep me very busy, but I am currently getting my feet wet with Starcraft 2 and I have a sealed copy of Bad Company 2 lying on my desk which I really am going to find the time to install one of these days

As such I take gaming and the needs of our gaming customers very seriously and I can assure you that I am definitely not the only MWEB employee who feels very strongly about this.

There are some complexities in terms of the way IPC networks work - in terms of where the IPC breakout resides and peering links that have an impact on things like gaming performance. Believe me when I say that we are aware of these issues and addressing them will be very much a part of our thinking as we grow the network going forward.

Kind Regards
MWEB Operations (Tech Manager)

 

[MWEBHelp]

I had a constant ping to google.co.za running in the background and the drops are evident.

Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=408ms TTL=50
Reply from 64.233.179.104: bytes=32 time=409ms TTL=50

Ping statistics for 64.233.179.104:
Packets: Sent = 1051, Received = 1016, Lost = 35 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 403ms, Maximum = 499ms, Average = 412ms

That packet loss doesn't look healthy - my test bench looks like this :

Reply from 64.233.179.104: bytes=32 time=438ms TTL=50
Reply from 64.233.179.104: bytes=32 time=435ms TTL=50
Reply from 64.233.179.104: bytes=32 time=435ms TTL=50
Reply from 64.233.179.104: bytes=32 time=433ms TTL=50
Reply from 64.233.179.104: bytes=32 time=433ms TTL=50
Reply from 64.233.179.104: bytes=32 time=431ms TTL=50
Reply from 64.233.179.104: bytes=32 time=433ms TTL=50

Ping statistics for 64.233.179.104:
Packets: Sent = 355, Received = 355, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 422ms, Maximum = 693ms, Average = 433ms

As you can see I stopped it at 355 with 0 lost. Let's get you talking to someone to have a look at what might be causing that - please inbox us those details

 

[Chevron]

and again random spikes:

Reply from 64.233.179.104: bytes=32 time=420ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=420ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=423ms TTL=50
Reply from 64.233.179.104: bytes=32 time=420ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=422ms TTL=50
Reply from 64.233.179.104: bytes=32 time=421ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=421ms TTL=50
Reply from 64.233.179.104: bytes=32 time=547ms TTL=50
Reply from 64.233.179.104: bytes=32 time=412ms TTL=50
Reply from 64.233.179.104: bytes=32 time=410ms TTL=50
Reply from 64.233.179.104: bytes=32 time=404ms TTL=50
Reply from 64.233.179.104: bytes=32 time=406ms TTL=50
Reply from 64.233.179.104: bytes=32 time=405ms TTL=50
Reply from 64.233.179.104: bytes=32 time=405ms TTL=50
Reply from 64.233.179.104: bytes=32 time=404ms TTL=50
Reply from 64.233.179.104: bytes=32 time=404ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=422ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=425ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=426ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=425ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=457ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=426ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=426ms TTL=50
Request timed out.
Reply from 64.233.179.104: bytes=32 time=418ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.179.104: bytes=32 time=423ms TTL=50
Reply from 64.233.179.104: bytes=32 time=445ms TTL=50
Reply from 64.233.179.104: bytes=32 time=443ms TTL=50
Reply from 64.233.179.104: bytes=32 time=441ms TTL=50
Reply from 64.233.179.104: bytes=32 time=441ms TTL=50
Reply from 64.233.179.104: bytes=32 time=421ms TTL=50
Reply from 64.233.179.104: bytes=32 time=440ms TTL=50
Reply from 64.233.179.104: bytes=32 time=422ms TTL=50
Reply from 64.233.179.104: bytes=32 time=422ms TTL=50
Reply from 64.233.179.104: bytes=32 time=422ms TTL=50
Reply from 64.233.179.104: bytes=32 time=440ms TTL=50
Reply from 64.233.179.104: bytes=32 time=434ms TTL=50
Reply from 64.233.179.104: bytes=32 time=413ms TTL=50
Reply from 64.233.179.104: bytes=32 time=419ms TTL=50
Reply from 64.233.179.104: bytes=32 time=431ms TTL=50
Reply from 64.233.179.104: bytes=32 time=436ms TTL=50
Reply from 64.233.179.104: bytes=32 time=435ms TTL=50
Reply from 64.233.179.104: bytes=32 time=435ms TTL=50
Reply from 64.233.179.104: bytes=32 time=435ms TTL=50
Reply from 64.233.179.104: bytes=32 time=435ms TTL=50
Reply from 64.233.179.104: bytes=32 time=435ms TTL=50
Reply from 64.233.179.104: bytes=32 time=435ms TTL=50
Reply from 64.233.179.104: bytes=32 time=437ms TTL=50
Reply from 64.233.179.104: bytes=32 time=416ms TTL=50
Reply from 64.233.179.104: bytes=32 time=407ms TTL=50

10 min prior to this was pinging fine. Mweb ops I pmed you my line stats. Could an snr of 9 and attentuation of 11.5 cause issues?

 

[zorko]

In general mweb 4meg sucks i never got decent speeds on the product and the service sucked, i know not many enjoy telkom but iu am back with them and although it might cost more in the long run i get full speeds almost anytime of the day.

 

[Valerion]

and again random spikes:

<SNIP>

10 min prior to this was pinging fine. Mweb ops I pmed you my line stats. Could an snr of 9 and attentuation of 11.5 cause issues?

I get more or less the same from time to time, but in my case my line completely loses sync for 1/2 a second - 2 seconds or sometimes more. My PPPoE link doesn't drop, though. This is a fairly new thing, ever since Telkom fixed a line error, so I suspect the issue is not as fixed as they believe. You should check this as well, that your router stays synched when you have packet loss.

 

[Chevron]

Ok. Seems as though it isn't mweb.

Telkom just told me that my exchange is part of the 10meg trial and there is nothing that they can do.

Don't know whether to be happy or sad at this point.

Apparantly my line will keep haing issues till the 20th.

 

[Adrenalin]

Whhooo!!

changed accounts, with the assistance of MWEB Operations, and the line is flying!!!!

*touches wood*

 

[Aharon]

Changed to what exactly?

 

[GingerBeer]

@GingerBeer - I think you might be underestimating us a little there

I played Counterstrike, Quake 3 and Starcraft competetively at clan level and attending competitions for many years and was very active in the gaming community administering servers for MWEB long before I was employed by them.

In more recent years I have also played Joint Operations and Battlefield 2 and I have also spent far too much time on the MMO scene. (I have tanked Black Temple in WoW and solo farmed UnderWorld in Guiildwars although Ultima Online remains unchallenged as the best MMO in my book).

I don't get as much time as I would like to game these days, work and my children keep me very busy, but I am currently getting my feet wet with Starcraft 2 and I have a sealed copy of Bad Company 2 lying on my desk which I really am going to find the time to install one of these days

As such I take gaming and the needs of our gaming customers very seriously and I can assure you that I am definitely not the only MWEB employee who feels very strongly about this.

There are some complexities in terms of the way IPC networks work - in terms of where the IPC breakout resides and peering links that have an impact on things like gaming performance. Believe me when I say that we are aware of these issues and addressing them will be very much a part of our thinking as we grow the network going forward.

Kind Regards
MWEB Operations (Tech Manager)

It may be true, it may not. I just can't
take seriously someone who says 100ms
is suitable for gaming.
Do you really want to play CSS with an in-
game ping of 100ms????????????????????

 

[Degaron]

MWEB should add a HOn server serouisly I mean at the moment SAIX is laggin its ass of and the only decent server available is IS.

 

[Fudzy]

Anybody else on Mweb uncapped have issues making an initial connection to Steam? I have to stop all network activity and even then it's a hit & miss affair. After it's connected though I've found the download speeds from Steam to be fine (+/- 80% of line speed) but the latency often leaves a lot to be desired.

 

[d7e7r7]

It seems to me the Mweb uncapped has better online support in this forum, do any of the other uncapped ISP's have someone online on this forum?

 

[Greenis]

Telkom is the best! 4gigs + upgrading to 10mbps All Mahala!

 

[d7e7r7]

Telkom is the best! 4gigs + upgrading to 10mbps All Mahala!

What happened to Ayoba?