MWEB Gaming Feedback

Will@MWEB said:
Hi Freaker, still looking for some detail on the nature of the problems you're having?
Click to expand...
hi Will just tried it again my ping was about 350 i fired up a nntp download (linux distro):-) and within about 5 min my ping was at 2500, i then closed the nntp download and my ping went back down to 300-350 this was around 7 tonight. Im on 4 meg uncapped shaped the only odd thing i do have set is my mtu, it is at 750 (last time i checked i needed that setting to get wow working)
Thx

Sent from my GT-I9000 using MyBroadband Android App
 
Hi Freaker

As a general rule you should stop all downloads when gaming to ensure an optimal experience. The 750 MTU setting should no longer be necessary and I would recommend reverting to default values. Let me know if this causes any problems for you.
 
OMG what happened?! D:

9k ms in WoW holy moly!
was okish today...



Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=240ms TTL=110
Reply from 212.58.224.138: bytes=32 time=238ms TTL=110
Reply from 212.58.224.138: bytes=32 time=240ms TTL=110
Reply from 212.58.224.138: bytes=32 time=239ms TTL=110
Reply from 212.58.224.138: bytes=32 time=239ms TTL=110
Reply from 212.58.224.138: bytes=32 time=242ms TTL=110
Reply from 212.58.224.138: bytes=32 time=247ms TTL=110
Reply from 212.58.224.138: bytes=32 time=240ms TTL=110
Reply from 212.58.224.138: bytes=32 time=241ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=238ms TTL=110
Reply from 212.58.224.138: bytes=32 time=238ms TTL=110
Reply from 212.58.224.138: bytes=32 time=239ms TTL=110
Reply from 212.58.224.138: bytes=32 time=240ms TTL=110
Reply from 212.58.224.138: bytes=32 time=238ms TTL=110
Reply from 212.58.224.138: bytes=32 time=240ms TTL=110
Reply from 212.58.224.138: bytes=32 time=239ms TTL=110
Reply from 212.58.224.138: bytes=32 time=242ms TTL=110
Reply from 212.58.224.138: bytes=32 time=240ms TTL=110
Request timed out.

Ping statistics for 212.58.224.138:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 238ms, Maximum = 247ms, Average = 240ms





Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.0.1
3 19 ms 16 ms 16 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 17 ms 17 ms 18 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
5 17 ms 17 ms 17 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 20 ms 21 ms 49 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
7 20 ms 21 ms 18 ms 196.22.169.94
8 457 ms 389 ms 439 ms 196.22.175.210
9 336 ms 401 ms 416 ms 149.6.98.5
10 503 ms 311 ms 242 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 275 ms 277 ms 241 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
12 239 ms 242 ms 239 ms ldn-b4-link.telia.net [213.248.70.237]
13 241 ms * 377 ms ldn-bb2-link.telia.net [80.91.246.146]
14 238 ms 320 ms 377 ms ldn-b3-link.telia.net [80.91.247.27]
15 285 ms 336 ms 246 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 239 ms 261 ms 257 ms 212.58.238.133
17 240 ms 239 ms 240 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
 
@ultraviolet

Your line fault is still open, just spoke to my guy looking after it and asked him to apply some pressure for you.
 
Will@MWEB said:
@ultraviolet

Your line fault is still open, just spoke to my guy looking after it and asked him to apply some pressure for you.
Click to expand...

Hey Will, yes thanx, Telkom has serviced the query this morning, the technician gave me a call this morning and asked what the problem was. He inturn said he will sort it out and I have received an sms reporting that my Telkom ADSL has been restored. But will keep an eye on what goes on and see what will happen from now on. Although it already looks a lot better.




Kindest Regards and Sincere Thanks.
 
Last edited:
Hi Will, been a while since I posted here. Having an epic mweb gaming experience since the fix, thanks. Just a quick question, would it be possible for you to perhaps look into setting up a dedicated server for the upcoming game Brink (http://www.brinkthegame.com/)
Would be most awsome.
Thanks.
 
ultraviolet150 said:
Hey Will, yes thanx, Telkom has serviced the query this morning, the technician gave me a call this morning and asked what the problem was. He inturn said he will sort it out and I have received an sms reporting that my Telkom ADSL has been restored. But will keep an eye on what goes on and see what will happen from now on. Although it already looks a lot better.




Kindest Regards and Sincere Thanks.
Click to expand...

That does look a lot healthier, please keep me posted on further developments and let me know if you're still experiencing any issues :)
 
Vaughan42 said:
Hi Will, been a while since I posted here. Having an epic mweb gaming experience since the fix, thanks. Just a quick question, would it be possible for you to perhaps look into setting up a dedicated server for the upcoming game Brink (http://www.brinkthegame.com/)
Would be most awsome.
Thanks.
Click to expand...

Hey Vaughan really glad to hear that, my webwasher doesn't like that URL (it is a game right? :o ), but I'll have a look on the test bench later and pass it on to our Gamesmaster for consideration. If you saw the recent interview with Derek Hershaw that was published you will have seen that gaming is definitely going to get a lot of attention this year and while I can't make promises about specific games and timelines I can certainly tell you that we are in for an exciting year as MWEB gamers - bring on the new toys! :D (now if my GTX580 would just arrive already)

edit:Just took a quick look now, looks very interesting :)
 
Last edited:
Ultraviolet, I take it the cause of your WoW latency was a line fault? Reason I'm asking is because I have been experiencing the same latency as of Wednesday night, say about past 21h00. A friend of mine that also plays on our server, and lives in my area, and that also use MWEB as an ISP, have the same problem as I.

Will, just for the record, before Wednesday, I've been getting smooth latencies : 270ms average when not raiding, and with Teamspeak off. 350ms average latency during raiding with Teamspeak on. I have changed my MTU back to the default, but have kept the leatrix fix installed. And this is on a 384k line with a Telkom Mega 105 router.

I will test again when we raid on Sunday night, and post my feedback here. Expect to hear from me sooner if the problem happens only in raids, as know then that it is my fault and will humbly apologize, but until then Mweb is guilty until proven innocent, Telkom also for that matter, just to be on the safe side :D
 
Last edited:
Hi Beanbag please do let me know if you're still having a problem and give me as much detail as possible, realm played on time problem experience, physical location and tracert and continuous ping tests taken at the time you were having a problem.
 
What the deal between MWeb and Telkom?

I play Fifa 11 online (PS3) and whenever I play someone on the telkom network the connection is always rated red [red=bad orange=ok green=good] yet with other SA isp's it's normally green and generally orange with European gamers.

I'm on a 4mb uncapped home connection and it's sometimes impossible to play some of my mates on telkom.
 
bmchunu said:
What the deal between MWeb and Telkom?

I play Fifa 11 online (PS3) and whenever I play someone on the telkom network the connection is always rated red [red=bad orange=ok green=good] yet with other SA isp's it's normally green and generally orange with European gamers.

I'm on a 4mb uncapped home connection and it's sometimes impossible to play some of my mates on telkom.
Click to expand...

Telkom are greedy fatcats and refuse to openly peer with Mweb, so all traffic between Telkom & Mweb is routed overseas to Europe and back. The distance the data has to travel is actually twice as far as when just playing with someone in Europe. Basically, double the normal international latency and one more reason to give Telkom the finger.
 
freaker76 said:
hi Will just tried it again my ping was about 350 i fired up a nntp download (linux distro):-) and within about 5 min my ping was at 2500, i then closed the nntp download and my ping went back down to 300-350 this was around 7 tonight. Im on 4 meg uncapped shaped the only odd thing i do have set is my mtu, it is at 750 (last time i checked i needed that setting to get wow working)
Thx

Sent from my GT-I9000 using MyBroadband Android App
Click to expand...

This is normal. If your downloading and trying to game at the same time the router doesn't know which packets to prioritize and the download effectively bottlenecks your line causing spikes and high response times in other applications. It gets significantly worse if your uploading something.
 
Beanbag said:
Ultraviolet, I take it the cause of your WoW latency was a line fault? Reason I'm asking is because I have been experiencing the same latency as of Wednesday night, say about past 21h00. A friend of mine that also plays on our server, and lives in my area, and that also use MWEB as an ISP, have the same problem as I....
Click to expand...


Hey Beanbag, It was indeed a line fault/DSLAM issue ie, the gateway. At night it still slows down a little but it is indeed much better.
 
Will@MWEB said:
That does look a lot healthier, please keep me posted on further developments and let me know if you're still experiencing any issues :)
Click to expand...

Hey again Mr Will(iam) xD
The net is indeed much better although at night I still get latencies a little higher that during the day. I'm however not complaining. Usually get around 320-380ms during the day, tonight its around 400-600ms. Take a look at the ping and tracert after the repairs today.



Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=274ms TTL=110
Reply from 212.58.224.138: bytes=32 time=342ms TTL=110
Reply from 212.58.224.138: bytes=32 time=306ms TTL=110
Reply from 212.58.224.138: bytes=32 time=264ms TTL=110
Reply from 212.58.224.138: bytes=32 time=257ms TTL=110
Reply from 212.58.224.138: bytes=32 time=287ms TTL=110
Reply from 212.58.224.138: bytes=32 time=276ms TTL=110
Reply from 212.58.224.138: bytes=32 time=272ms TTL=110
Reply from 212.58.224.138: bytes=32 time=262ms TTL=110
Reply from 212.58.224.138: bytes=32 time=276ms TTL=110
Reply from 212.58.224.138: bytes=32 time=266ms TTL=110
Reply from 212.58.224.138: bytes=32 time=260ms TTL=110
Reply from 212.58.224.138: bytes=32 time=258ms TTL=110
Reply from 212.58.224.138: bytes=32 time=357ms TTL=110
Reply from 212.58.224.138: bytes=32 time=263ms TTL=110
Reply from 212.58.224.138: bytes=32 time=470ms TTL=110
Reply from 212.58.224.138: bytes=32 time=564ms TTL=110
Reply from 212.58.224.138: bytes=32 time=358ms TTL=110
Reply from 212.58.224.138: bytes=32 time=302ms TTL=110
Reply from 212.58.224.138: bytes=32 time=277ms TTL=110

Ping statistics for 212.58.224.138:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 257ms, Maximum = 564ms, Average = 309ms




Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 2 ms 2 ms 2 ms 192.168.0.1
3 16 ms 15 ms 16 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 29 ms 17 ms 16 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
5 17 ms 19 ms 18 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 41 ms 61 ms 53 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 52 ms 38 ms 32 ms 196.22.169.94
8 453 ms 393 ms 404 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
9 413 ms 272 ms 258 ms 149.6.98.17
10 279 ms 277 ms 278 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 271 ms 264 ms 258 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
12 317 ms 256 ms 263 ms ldn-b4-link.telia.net [213.248.70.237]
13 280 ms 291 ms 285 ms ldn-bb2-link.telia.net [80.91.247.93]
14 346 ms 417 ms 385 ms ldn-b3-link.telia.net [80.91.245.29]
15 275 ms 278 ms 286 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 296 ms 267 ms 285 ms 212.58.238.133
17 259 ms 257 ms 266 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
 
Will, everything seemed to be sorted out. the issue remains to continue throughout sundays... its the same issue as before. My WoW is unplayable on sundays and general browsing is also extremely sluggish. take a look at what i mean, this is the scene throughout the whole day.



Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.0.1
3 568 ms 839 ms 432 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 294 ms 234 ms 295 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
5 518 ms 605 ms 450 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 338 ms 145 ms 186 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 177 ms 340 ms 381 ms 196.22.169.94
8 661 ms 721 ms 838 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
9 562 ms 319 ms 289 ms 149.6.98.17
10 630 ms 950 ms 949 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 761 ms 814 ms 567 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
12 507 ms 412 ms 416 ms ldn-b4-link.telia.net [213.248.70.237]
13 851 ms 665 ms 683 ms ldn-bb2-link.telia.net [80.91.247.93]
14 756 ms 718 ms 858 ms ldn-b3-link.telia.net [80.91.245.29]
15 * 483 ms 539 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 * 636 ms 681 ms 212.58.238.133
17 * 923 ms 610 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.




Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=1179ms TTL=110
Reply from 212.58.224.138: bytes=32 time=1187ms TTL=110
Reply from 212.58.224.138: bytes=32 time=563ms TTL=110
Reply from 212.58.224.138: bytes=32 time=850ms TTL=110
Reply from 212.58.224.138: bytes=32 time=428ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=1024ms TTL=110
Reply from 212.58.224.138: bytes=32 time=604ms TTL=110
Reply from 212.58.224.138: bytes=32 time=941ms TTL=110
Reply from 212.58.224.138: bytes=32 time=980ms TTL=110
Reply from 212.58.224.138: bytes=32 time=874ms TTL=110
Reply from 212.58.224.138: bytes=32 time=1360ms TTL=110
Reply from 212.58.224.138: bytes=32 time=872ms TTL=110
Reply from 212.58.224.138: bytes=32 time=814ms TTL=110
Reply from 212.58.224.138: bytes=32 time=770ms TTL=110
Reply from 212.58.224.138: bytes=32 time=881ms TTL=110
Reply from 212.58.224.138: bytes=32 time=1128ms TTL=110
Reply from 212.58.224.138: bytes=32 time=609ms TTL=110
Reply from 212.58.224.138: bytes=32 time=884ms TTL=110
Reply from 212.58.224.138: bytes=32 time=767ms TTL=110

Ping statistics for 212.58.224.138:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 428ms, Maximum = 1360ms, Average = 879ms


Will this clearly shows there is still an issue here. Sundays are terrible for my net connection. Please help... (again)
 
I have 990 MS suddenly in LoL, It takes ages for browsers to connect. All was fine At three pm

Edit: Took me about 3 mins to actually load the edit post page, anyway. I finished the game with 2050ms...
 
Last edited:
LOL had some spikes last night, but i had 180ms, think it was the server, the actions was clicked and i got the kill but i only saw the kill after a few sec :P

was only 1 match at the end, no other matches , and played LOL the whole weekend, had some buds over to play with.

LOL= league of legends yes
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X