MWEB Gaming Feedback

I'm not a gamer, but my pings from CT to London via SAT-3 are a solid 160ms, which is a significant improvement on the previous 250ms!

Increased traffic might affect these figures later in the day.
 
getting fantastic pings to the europe wow servers with a proxy, 180ms, usually 280
 
Looking good all round at the moment, thanks as always for the usdeful feedback Gordon :) A round of applause for the network techs who I hope are fast asleep now - it's been a long night for them.
 
Man oh man! I really hope it stays like this.
Logged on with my banking alt this morning, running around Stormwind. Doing a few AH scans and stuff.
Was online for about an hour and my latency never went over 350ms :D
AH scanning pushed it to about 350ms but without scanning, standing in a crowded Stormwind it stayed sub 300ms.
On 384k uncapped, no MTU settings or proxies.
 
238ms! i don't think i've ever been that low hahaha

EDIT:

202ms W T F ! ! ! WOOOOOOOOOOOOOOOOHOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
Last edited:
Will@MWEB said:
Testing in the middle of an upgrade which is running slightly over time is probably going to give you some whacky results gentlemen, also remember that route discovery can take some time to settle down - next time, get some sleep :)

Sillicur if you're getting dced at the moment I think it's time we started looking at that as an individual fault on your side, I've mentioned to you before that I don't think your poor experience is just about the network issue on our side.
Click to expand...

Tested my router at a friends house. Got my telkom line tested. When i log onto the free afrihost account its a solid 250ms with no problems. How can it be on my side in what possible way?
Also, people reporting very good ms, so i ask, will PE be under the CPT people ? Should i also see a drop in ms like some are reporting? 280ms pinging to london, same as always, or is PE not affected by this change?
 
Nope PE routes North Sillicur, if you do a tracert to bbc.co.uk you should see the London side goes via interroute. I really don't know what else to suggest for you then. The consensus from recent feedback here has been that this problem seemed to be isolated to our Cape Town network, we can ask the Gauteng based users to sound off again and let us know what their current experience is like as, barring the Telkom infrastrcuture between you and our network, yours should be the same.
 
Will@MWEB said:
Nope PE routes North Sillicur, if you do a tracert to bbc.co.uk you should see the London side goes via interroute. I really don't know what else to suggest for you then. The consensus from recent feedback here has been that this problem seemed to be isolated to our Cape Town network, we can ask the Gauteng based users to sound off again and let us know what their current experience is like as, barring the Telkom infrastrcuture between you and our network, yours should be the same.
Click to expand...

Okay Will, I know for a fact i have been told numerous times PE goes through CPT. I think by you as well, should i search through all the posts to confirm?
Im at 280 ms now, so i shouldnt expect lower and the CPT people get 190-200 just because?

Btw, im smelling bull**** from you now.
 
Run the tracert and post it please. I have no control over who goes North and who goes South, the split was made based on various capacity considerations - when we initially brought the Cape Town network on line a portion of the Eastern Cape was routed South but this did not turn out to be a good solution and was subsequently shifted back north, within the first week, or two. The routing split is made at the Telkom ESR level.
 
Last edited:
Will@MWEB said:
Run the tracert and post it please.
Click to expand...

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

1 27 ms 27 ms 26 ms 41-132-68-1.dsl.mweb.co.za [41.132.68.1]
2 57 ms 59 ms 60 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
3 57 ms 55 ms 56 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 61 ms 60 ms 59 ms tengig-0-0-0-0-11.vic-up-2.mweb.co.za [196.22.169.226]
5 60 ms 58 ms 61 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

6 283 ms 281 ms 280 ms ap2610-1-s12-denimtowers.mweb.net [196.22.163.234]
7 294 ms 281 ms 281 ms 79.141.38.37.available.above.net [79.141.38.37]

8 290 ms 287 ms 288 ms so-1-0-0.mpr1.lhr3.uk.above.net [64.125.28.37]
9 282 ms 279 ms 281 ms xe-2-0-0.mpr2.lhr3.uk.above.net [64.125.28.146]

10 285 ms 284 ms 284 ms bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.103]
11 285 ms 284 ms 284 ms 212.58.238.149
12 284 ms 284 ms 284 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

I dont see interoute, do you?
 
278ms in an uncrowed section of SW! PLEASE PRETTY PLEASE keep this as is :D Best steady latency I have ever got in SA, great work!

Is this expected to last?
 
Last edited:
Will@MWEB said:
Run the tracert and post it please. I have no control over who goes North and who goes South, the split was made based on various capacity considerations - when we initially brought the Cape Town network on line a portion of the Eastern Cape was routed South but this did not turn out to be a good solution and was subsequently shifted back north, within the first week, or two. The routing split is made at the Telkom ESR level.
Click to expand...

Pro move editing your post after I showed the tracert where i cant see interoute from "Run the tracert and post it please" to an explanation that you really have no control and blaming telkom.

Im going for a smoke. Guess your waiting for me to log off now or something stupid. Lets see.
 
Last edited:
Just confirmed what I have been thinking all alone. Thank you for that at least.

Well, guess I can just give up, Merry Xmas.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X