MWEB Gaming Feedback

Hi Mooler I play Bad Company 2 myself and I am based in Cape Town also on a 4mb shaped account. I haven't tried international servers in a while, however I last played on local servers this weekend and everything seemed fine. Can you take a look at your command line pings and traces while experiencing a problem and let us know the results?

Hi Will. Thanks for the reply.

Here are the traces. Both times were without torrents running.

WAGE Server:
Code:
[U]07:00[/U]

  1     1 ms     1 ms     1 ms  ...
  2     7 ms     6 ms     6 ms  41-133...dsl.mweb.co.za [41.133...]
  3     8 ms     8 ms     8 ms  Te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166]
  4     8 ms     9 ms    10 ms  Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
  5    12 ms    12 ms     9 ms  TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
  6     9 ms     9 ms     9 ms  196-28-178-137.adsl.mweb.co.za [196.28.178.137]
  7    24 ms     9 ms    10 ms  wa.cinx.net.za [198.32.214.45]
  8    10 ms    11 ms     9 ms  41.185.1.2
  9    10 ms    10 ms    11 ms  41.185.60.74

Server browser ping: 16ms
Actual in-game ping: 450ms

[U]16:30[/U]

  1     1 ms     1 ms     1 ms  ...
  2     7 ms    16 ms     7 ms  41-133...dsl.mweb.co.za [41.133...]
  3    17 ms    16 ms    16 ms  Te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166]
  4     8 ms     8 ms     8 ms  Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
  5    10 ms    12 ms     9 ms  TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.178.97]
  6     9 ms     9 ms     9 ms  196-28-178-137.adsl.mweb.co.za [196.28.178.137]
  7    13 ms     9 ms     9 ms  wa.cinx.net.za [198.32.214.45]
  8    22 ms    23 ms    26 ms  41.185.1.2
  9    24 ms    25 ms    23 ms  41.185.60.74

Server browser ping: 34ms
Actual in-game ping: 500ms

Gameservers server:
Code:
[U]07:00[/U]

  1     1 ms     1 ms     1 ms  ...
  2     7 ms     6 ms     6 ms  41-133...dsl.mweb.co.za [41.133...]
  3     8 ms     8 ms     7 ms  Te1-1-0.511.cpt-ipc-1.mweb.co.za [196.28.178.202]
  4     8 ms     8 ms     7 ms  Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
  5     9 ms     8 ms     9 ms  196-28-178-70.adsl.mweb.co.za [196.28.178.70]
  6     7 ms     9 ms     7 ms  cte-gw116-courts-megastor-548565000 [196.41.133.166]
  7     9 ms     8 ms     9 ms  196-28-169-79.adsl.mweb.co.za [196.28.169.79]

Server browser ping: 25ms
Actual in-game ping: 400ms (settles on 250ms for a few minutes before spiking again)


[U]16:30[/U]

  1     1 ms     1 ms     1 ms  ...
  2     7 ms    11 ms     6 ms  41-133...dsl.mweb.co.za [41.133...]
  3     8 ms     7 ms     8 ms  Te1-1-0.511.cpt-ipc-1.mweb.co.za [196.28.178.202]
  4     9 ms    17 ms     8 ms  Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
  5     9 ms     8 ms     8 ms  196-28-178-70.adsl.mweb.co.za [196.28.178.70]
  6     8 ms     8 ms     8 ms  cte-gw116-courts-megastor-548565000 [196.41.133.166]
  7     9 ms     9 ms     9 ms  196-28-169-79.adsl.mweb.co.za [196.28.169.79]

Server browser ping: 36ms
Actual in-game ping: 500ms (again, settles at around 250ms for a minute or two and then spikes up again)

Edit:
Just tried it again. Torrents and everything apart from Steam and BC2 are off. Server browser says 30ms but in-game it's 500ms.
Tried CS:S as well. 30ms in-game. This was immediately after trying to get a decent game of BC2 in.
 
Last edited:
Hi Will. I took a little sabatical from Star Trek Online, and on my return seem unable to play the game. I had spoken about this months back (via PM if I recall) and it seemed to be sorted out.
I can log into the game, but from there it takes soo long to retrieve maps, that I timeout before getting into the game.

Any help would be greatly appreciated!
 
Hi Will

ok obviously I can't LOTRO over a weekend
but I did some tests last night and it looks great +-260 latency

thanks guys
 
Re my STO post, here's a list of pretty much everything IP and port related for STO.

Star Trek info

EDIT: STO is still unplayable on mweb, but works fine with telkom.
 
Last edited:
Hi Mooler I play Bad Company 2 myself and I am based in Cape Town also on a 4mb shaped account. I haven't tried international servers in a while, however I last played on local servers this weekend and everything seemed fine. Can you take a look at your command line pings and traces while experiencing a problem and let us know the results?
But you don't play on Mweb servers obviously since they are always showing 0/32 or whatever.
 
Anyone else having issues with Bad Company 2? I used to get great latency on the local servers and found international servers to be more than playable, but now I'm getting over 500ms on the local servers and international ones are just a slideshow.

I'm on 4mb shaped in Cape Town. Other games seem to be fine.

I stay in the CBD, play BC2 on a range of local servers. I get 60 - 100ms ping on average. So no, no issues here. I never play FPS on international, as I don't see how a Saffer can beat some Europeans, when you are playing at 300ms+ versus their sub 10ms ping.

I have a 10mb telkom line, running the mweb uncapped 4mb shaped account.

I'm going to take a stab in the dark and say that you are most likely downloading torrents etc in the background. And if not you, someone else on your network is.
 
But you don't play on Mweb servers obviously since they are always showing 0/32 or whatever.

Not much I can do to change the habits of the community Lounger. Those servers have incredible performance, much better than the ones that tend to populate more frequently. A lot of our content is still brand new and communities take time to build, but we'll get there I'm sure.
 
I stay in the CBD, play BC2 on a range of local servers. I get 60 - 100ms ping on average. So no, no issues here. I never play FPS on international, as I don't see how a Saffer can beat some Europeans, when you are playing at 300ms+ versus their sub 10ms ping.

I have a 10mb telkom line, running the mweb uncapped 4mb shaped account.

I'm going to take a stab in the dark and say that you are most likely downloading torrents etc in the background. And if not you, someone else on your network is.

I don't know, man. I've tried it with and without torrents running and it made no difference whatsoever. Never used to affect it anyway.

Regarding international, it's surprisingly playable if you don't mind a 160-200ms ping. I used to get my Vietnam fix on European servers because the local servers are almost always empty.
 
Been raiding for 2 nights in a row on 25m now with Mweb Acc + WTFast (after upgrade to 1.75) and going smoothly... round 250ms average! Keep it up! *hope i didnt just jinx it!*
 
EDIT: Pays to test before posting. Thanks, seems to be working again :)
 
Last edited:
Yep getting bad lag in Age of Conan as well tonight. With wtfast its spiking constantly to 4800 without it 500 to 800 ping with spikes up to 1400.
 
Had some latency spikes on wow but the latency stabilized to the norm after a few minutes. I noticed it takes a few minutes for latency to start dropping considerably to good speeds.

Also noticed the background downloader popping up few times while playing.
 
my ping is spiking in black ops for the past 2 days now. please check for me not only me. a lot of people asking even radio stream is slow
 
Just my 2c.. Internet in general is a little slow of late. Gaming has been 'ok' but not great. elevated pings and the occasional glitch or teleport in Black Ops. HTTP downloads like my new nvidia drivers have been sloooooow, but over VPN, to work, everything is fantastic. hmmm...

If it stays the same im happy gaming wise, I just hope it does not get worse :(
 
Hi,

I am a WoW player and latency does concern me. I do use WTFast but for some reason it isn't satisfying enough. I get an average latency of Home: 250-270ms and World: 340-450ms without WTFast and World: 299-324 with WTFast and if I'm lucky it'll drop to 260-280. But even though my latency with WTFast on may seem promising, it isn't. I have quartz and it shows the latency(time) it took to start casting a spell after I pressed it to start casting and on average that is between 400-700ms. I did a tracert and pathping to my realm and it shows latency's well below what I'm currently getting, which I find wierd(but I may be wrong about finding it wierd). I've been all over Blizzard's forums to find some solution and was on the brink of posting my problem there, but instead figured I should probably ask my ISP first.

Here is the tracert I did :
Code:
Tracing route to 195.12.234.197 over a maximum of 30 hops

  1    <1 ms     1 ms     1 ms  192.168.1.1 
  2    11 ms    14 ms    15 ms  41-132-34-1.dsl.mweb.co.za [41.132.34.1] 
  3    17 ms    14 ms    14 ms  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218] 
  4    16 ms    17 ms    14 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3] 
  5    19 ms    18 ms    15 ms  TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.169.241] 
  6    19 ms    18 ms    21 ms  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.94] 
  7   242 ms   239 ms   239 ms  pos0-0-0-1.lon-up-1.mweb.co.za.175.22.196.in-addr.arpa [196.22.175.214] 
  8   330 ms   240 ms   442 ms  149.6.98.5 
  9   262 ms   243 ms   238 ms  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.165] 
 10   246 ms   241 ms   240 ms  te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134] 
 11   242 ms   282 ms   241 ms  ldn-b4-link.telia.net [213.248.70.237] 
 12   272 ms   243 ms   239 ms  ldn-bb2-link.telia.net [80.91.249.181] 
 13   254 ms   247 ms   248 ms  prs-bb2-link.telia.net [80.91.247.240] 
 14   262 ms   250 ms   249 ms  prs-b4-link.telia.net [213.248.65.226] 
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

I really have no idea why it times out from 15-30. If you could explain that to me as well it'll be great.

Here is the pathping I did:
Code:
Tracing route to 195.12.234.197 over a maximum of 30 hops

  0  L‚mon [192.168.1.101] 
  1  192.168.1.1 
  2  41-132-34-1.dsl.mweb.co.za [41.132.34.1] 
  3  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218] 
  4  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3] 
  5  TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.169.241] 
  6  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.94] 
  7  pos0-0-0-1.lon-up-1.mweb.co.za.175.22.196.in-addr.arpa [196.22.175.214] 
  8  149.6.98.5 
  9  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.165] 
 10  te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134] 
 11  ldn-b4-link.telia.net [213.248.70.237] 
 12  ldn-bb2-link.telia.net [80.91.249.181] 
 13  prs-bb2-link.telia.net [80.91.247.240] 
 14  prs-b4-link.telia.net [213.248.65.226] 
 15     *        *        *     
Computing statistics for 350 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           L‚mon [192.168.1.101] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1 
                                0/ 100 =  0%   |
  2   18ms     0/ 100 =  0%     0/ 100 =  0%  41-132-34-1.dsl.mweb.co.za [41.132.34.1] 
                                0/ 100 =  0%   |
  3   17ms     0/ 100 =  0%     0/ 100 =  0%  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218] 
                                0/ 100 =  0%   |
  4   15ms     0/ 100 =  0%     0/ 100 =  0%  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3] 
                                0/ 100 =  0%   |
  5   20ms     0/ 100 =  0%     0/ 100 =  0%  TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.169.241] 
                                0/ 100 =  0%   |
  6   28ms     0/ 100 =  0%     0/ 100 =  0%  tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.94] 
                                0/ 100 =  0%   |
  7  251ms     0/ 100 =  0%     0/ 100 =  0%  pos0-0-0-1.lon-up-1.mweb.co.za.175.22.196.in-addr.arpa [196.22.175.214] 
                                0/ 100 =  0%   |
  8  264ms     0/ 100 =  0%     0/ 100 =  0%  149.6.98.5 
                                0/ 100 =  0%   |
  9  261ms     0/ 100 =  0%     0/ 100 =  0%  te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.165] 
                                0/ 100 =  0%   |
 10  260ms     0/ 100 =  0%     0/ 100 =  0%  te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134] 
                                0/ 100 =  0%   |
 11  246ms     0/ 100 =  0%     0/ 100 =  0%  ldn-b4-link.telia.net [213.248.70.237] 
                                0/ 100 =  0%   |
 12  245ms     0/ 100 =  0%     0/ 100 =  0%  ldn-bb2-link.telia.net [80.91.249.181] 
                                0/ 100 =  0%   |
 13  252ms     0/ 100 =  0%     0/ 100 =  0%  prs-bb2-link.telia.net [80.91.247.240] 
                                0/ 100 =  0%   |
 14  251ms     0/ 100 =  0%     0/ 100 =  0%  prs-b4-link.telia.net [213.248.65.226] 

Trace complete.

And a screenshot of my latency ingame 1 min after the pathping completed:
2yujeia.jpg


I live in Pretoria and I am on a 4mb/s uncapped connection.

Thanks in advance.
 
@syxt. That's a little bit of a tough one to answer. Honestly the performance you're reporting all sounds well inside acceptable ranges - I haven't used quartz myself and usually use the latency mater on titan Panel to keep an eye on things.

Like I said though the scores you're reporting and all of your command line data looks well inside normal ranges. Perhaps you could try some of the higher grade suggestions in terms of looking at your tcp stack settings and network card configuration (Check out earlier posts from Pornholio and I think it was J0n0)?
 
Top
Sign up to the MyBroadband newsletter
X