MWEB Gaming Feedback

Nookie · May 5, 2011

Hi Will, I mentioned bad speeds in the Mweb thread however I am also having gaming problems. Logging on to STO is just about impossible never mind trying to game. Switching over to SAIX account produces playable results. Really a problem with my MWEB account.

Wavelength · May 5, 2011

Will@MWEB said:
The attenuation usually comes with other symptoms too. Can you do some continuous ping tests to local destinations and show us what the results look like to see if there are any indications of jitter and packet loss. Also your router may be able to give you statistics on CRC errors which are a possibility if your line is not 100%

Some data:

C:\>ping -n 50 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=46ms TTL=52
Reply from 41.203.21.137: bytes=32 time=46ms TTL=52
Reply from 41.203.21.137: bytes=32 time=50ms TTL=52
Reply from 41.203.21.137: bytes=32 time=37ms TTL=52
Reply from 41.203.21.137: bytes=32 time=46ms TTL=52
Reply from 41.203.21.137: bytes=32 time=49ms TTL=52
Reply from 41.203.21.137: bytes=32 time=27ms TTL=52
Reply from 41.203.21.137: bytes=32 time=32ms TTL=52
Reply from 41.203.21.137: bytes=32 time=43ms TTL=52
Reply from 41.203.21.137: bytes=32 time=38ms TTL=52
Request timed out.
Request timed out.
Reply from 41.203.21.137: bytes=32 time=42ms TTL=52
Reply from 41.203.21.137: bytes=32 time=41ms TTL=52
Reply from 41.203.21.137: bytes=32 time=48ms TTL=52
Reply from 41.203.21.137: bytes=32 time=33ms TTL=52
Reply from 41.203.21.137: bytes=32 time=49ms TTL=52
Reply from 41.203.21.137: bytes=32 time=50ms TTL=52
Reply from 41.203.21.137: bytes=32 time=32ms TTL=52
Reply from 41.203.21.137: bytes=32 time=16ms TTL=52
Reply from 41.203.21.137: bytes=32 time=42ms TTL=52
Reply from 41.203.21.137: bytes=32 time=39ms TTL=52
Reply from 41.203.21.137: bytes=32 time=50ms TTL=52
Reply from 41.203.21.137: bytes=32 time=45ms TTL=52
Reply from 41.203.21.137: bytes=32 time=49ms 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=10ms TTL=52
Reply from 41.203.21.137: bytes=32 time=32ms TTL=52
Reply from 41.203.21.137: bytes=32 time=49ms TTL=52
Reply from 41.203.21.137: bytes=32 time=17ms 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=40ms TTL=52
Reply from 41.203.21.137: bytes=32 time=28ms TTL=52
Reply from 41.203.21.137: bytes=32 time=49ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=49ms TTL=52
Request timed out.
Reply from 41.203.21.137: bytes=32 time=30ms TTL=52
Reply from 41.203.21.137: bytes=32 time=43ms TTL=52
Reply from 41.203.21.137: bytes=32 time=24ms TTL=52
Reply from 41.203.21.137: bytes=32 time=49ms TTL=52
Reply from 41.203.21.137: bytes=32 time=32ms TTL=52
Reply from 41.203.21.137: bytes=32 time=49ms TTL=52
Reply from 41.203.21.137: bytes=32 time=36ms TTL=52
Reply from 41.203.21.137: bytes=32 time=37ms TTL=52
Reply from 41.203.21.137: bytes=32 time=40ms TTL=52
Reply from 41.203.21.137: bytes=32 time=43ms TTL=52
Reply from 41.203.21.137: bytes=32 time=45ms TTL=52

Ping statistics for 41.203.21.137:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 50ms, Average = 38ms

C:\>

C:\>ping -n 50 www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=171ms TTL=119
Reply from 196.2.63.110: bytes=32 time=71ms TTL=119
Reply from 196.2.63.110: bytes=32 time=67ms TTL=119
Reply from 196.2.63.110: bytes=32 time=63ms TTL=119
Reply from 196.2.63.110: bytes=32 time=63ms TTL=119
Reply from 196.2.63.110: bytes=32 time=63ms TTL=119
Reply from 196.2.63.110: bytes=32 time=67ms TTL=119
Reply from 196.2.63.110: bytes=32 time=73ms TTL=119
Reply from 196.2.63.110: bytes=32 time=51ms TTL=119
Reply from 196.2.63.110: bytes=32 time=62ms TTL=119
Reply from 196.2.63.110: bytes=32 time=87ms TTL=119
Reply from 196.2.63.110: bytes=32 time=71ms TTL=119
Reply from 196.2.63.110: bytes=32 time=63ms TTL=119
Reply from 196.2.63.110: bytes=32 time=65ms TTL=119
Reply from 196.2.63.110: bytes=32 time=58ms TTL=119
Reply from 196.2.63.110: bytes=32 time=72ms TTL=119
Reply from 196.2.63.110: bytes=32 time=112ms TTL=119
Reply from 196.2.63.110: bytes=32 time=159ms TTL=119
Reply from 196.2.63.110: bytes=32 time=66ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=65ms TTL=119
Reply from 196.2.63.110: bytes=32 time=51ms TTL=119
Reply from 196.2.63.110: bytes=32 time=62ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=40ms TTL=119
Reply from 196.2.63.110: bytes=32 time=48ms TTL=119
Reply from 196.2.63.110: bytes=32 time=33ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=52ms TTL=119
Reply from 196.2.63.110: bytes=32 time=43ms TTL=119
Reply from 196.2.63.110: bytes=32 time=37ms TTL=119
Reply from 196.2.63.110: bytes=32 time=47ms TTL=119
Reply from 196.2.63.110: bytes=32 time=61ms TTL=119
Reply from 196.2.63.110: bytes=32 time=65ms TTL=119
Reply from 196.2.63.110: bytes=32 time=68ms TTL=119
Reply from 196.2.63.110: bytes=32 time=71ms TTL=119
Reply from 196.2.63.110: bytes=32 time=73ms TTL=119
Reply from 196.2.63.110: bytes=32 time=71ms TTL=119
Reply from 196.2.63.110: bytes=32 time=68ms TTL=119
Reply from 196.2.63.110: bytes=32 time=61ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=33ms TTL=119
Reply from 196.2.63.110: bytes=32 time=48ms TTL=119
Reply from 196.2.63.110: bytes=32 time=45ms TTL=119
Reply from 196.2.63.110: bytes=32 time=53ms TTL=119
Reply from 196.2.63.110: bytes=32 time=39ms TTL=119
Reply from 196.2.63.110: bytes=32 time=38ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=48ms TTL=119
Reply from 196.2.63.110: bytes=32 time=73ms TTL=119

Ping statistics for 196.2.63.110:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 171ms, Average = 63ms

C:\>

Will@MWEB · May 5, 2011

Sorry not familiar with STO, is that local, or international?

Kosmik · May 5, 2011

Will@MWEB said:
Sorry not familiar with STO, is that local, or international?

I think he means Star Trek Online, international as far as I know.

Will@MWEB · May 5, 2011

Wavelength said:
Some data:

Ping statistics for 41.203.21.137:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 50ms, Average = 38ms

Ping statistics for 196.2.63.110:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 171ms, Average = 63ms

C:\>

Hi Wavelength

That packetloss and a fair amount of jitter (ping fluctuating constantly) is not doing your gaming any good and is most likely a line related problem. I would suggest taking this up with Telkom, unless you're an all inclusive customer in which case PM MWEB Guy your details and ask him to get the ball rolling for you on a line fault.

Will@MWEB · May 5, 2011

Kosmik said:
I think he means Star Trek Online, international as far as I know.

Ok thanks

Wavelength · May 5, 2011

Will@MWEB said:
Hi Wavelength

That packetloss and a fair amount of jitter (ping fluctuating constantly) is not doing your gaming any good and is most likely a line related problem. I would suggest taking this up with Telkom, unless you're an all inclusive customer in which case PM MWEB Guy your details and ask him to get the ball rolling for you on a line fault.

Cool, I logged a fault with Telkom.

Will@MWEB · May 5, 2011

Wavelength said:
Cool, I logged a fault with Telkom.

Thanks

Let us know if you run into any problems and we'll try to assist.

Sillicur · May 5, 2011

The slow connection to ANY news server persists. Going on 5 days now.

Nookie · May 5, 2011

Hi Will,

My attenuation is at 55 however I doubt my line is the problem, it was fine before, here are some tests from my SAIX account:

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes o
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=34ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=34ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=34ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55
Reply from 41.203.21.137: bytes=32 time=32ms TTL=55
Reply from 41.203.21.137: bytes=32 time=33ms TTL=55

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

And from MWEB:

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=34ms TTL=51
Reply from 41.203.21.137: bytes=32 time=32ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=34ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=32ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=32ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=32ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=32ms TTL=51
Reply from 41.203.21.137: bytes=32 time=34ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=34ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=34ms TTL=51
Reply from 41.203.21.137: bytes=32 time=34ms TTL=51
Reply from 41.203.21.137: bytes=32 time=32ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=32ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=34ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51
Reply from 41.203.21.137: bytes=32 time=32ms TTL=51
Reply from 41.203.21.137: bytes=32 time=33ms TTL=51

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

Looks good for both right? However my SAIX account allows me to play WoW (350ms) and my MWEB does not (10000ms).

J0n0 · May 5, 2011

Im getting horrid latency on wow as well. Ive noticed with Netlimiter that wow only uses 0.4KB/s tops. :erm: HTTP uses 30KB/s when I load pages.

StevenC · May 5, 2011

Logged on for raid, 11k ms on MWEB =(
AxessLite going strong...

nelis · May 5, 2011

I see a lot of black ops servers are not working properly. Sometimes when a map is done the server does not go on to then ew map and just hangs. People then starts to quit the server. Also when I open the game it's just telling me fetching stats for a min or 2 then connects then for about 5min can't find server aswell.

Please MWEB I'm begging you fix the issue please

avert · May 5, 2011

my super awesome tunneling service seems pretty much unaffected by all this shena****ns(this really is the best word for this service)

**who word filters shenan-igans >;3

DurbanMonkey · May 5, 2011

started crapping up again. spoke to Luke from Mweb who clearly doesn't have a clue. Did admit there is a fault with Warcraft latency but couldn't understand why NZB is downloading at 5kb. when i switched servers on the fly using Grabit, Luke tells me that i need to shut down grabit and restart. really since when? i have never had to do that. clearly a junior tech still learning the ropes.

Will@mweb, i will be posting a complaint on HelloPeter as the lack of feedback and 3 days with the same issue is actually just disgusting!

nelis · May 5, 2011

DurbanMonkey said:
started crapping up again. spoke to Luke from Mweb who clearly doesn't have a clue. Did admit there is a fault with Warcraft latency but couldn't understand why NZB is downloading at 5kb. when i switched servers on the fly using Grabit, Luke tells me that i need to shut down grabit and restart. really since when? i have never had to do that. clearly a junior tech still learning the ropes.

Will@mweb, i will be posting a complaint on HelloPeter as the lack of feedback and 3 days with the same issue is actually just disgusting!

Mweb Guy just replied to me. The Game master is working from 8 to 5. So no gaming tonight this is unacceptable. Can I just play 1 game without issues thats all I ask.

DurbanMonkey · May 5, 2011

Works 8-5? Are you telling me they don't pull overtime? What kind of a business is this?

Anyone want to recommend another ISP? i dont have time for companies that claim 24/7 support but don't deliver.

i'm actually livid....

nelis said:
Mweb Guy just replied to me. The Game master is working from 8 to 5. So no gaming tonight this is unacceptable. Can I just play 1 game without issues thats all I ask.

Nicelag · May 5, 2011

I see the Lag is back, after all this time?

Nicelag · May 5, 2011

does someone know whats up with the wow server line then?

legionary · May 5, 2011

My WoW was running fine after i got back from work at about 5. just after 7 it started slowing down tremendously.

pingtest is fine at 277ms
WoW is telling me my home latency is 283ms while my world latency is between 3.8k and 21k ms (usually these are roughly the same)
Netlimiter shows WoW as starting off fine after logging in then its as if its being shaped down to less than 1 KB/s.
I am on a unshaped account so this shouldn't be happening

Join the MyBroadband community

Get started

MWEB Gaming Feedback

Well-Known Member

Well-Known Member

Expert Member

Honorary Master

Expert Member

Expert Member

Well-Known Member

Expert Member

Well-Known Member

Well-Known Member

Expert Member

Expert Member

Expert Member

Senior Member

Banned

Expert Member

Banned

Active Member

Active Member

Member