MWEB Gaming Feedback

Sorry I couldn't resist that one :)

Seriously though as soon as I get this patched up I will spend some time trying to pull together as much information as I can in a controlled environment to see if we can isolate what's causing this.

Edit : I have actually played before - I had a couple of 70's on the Sylvanas Realm, I stopped just before Lich King came out.
 
Last edited:
Played WoW from 17:30 and had good latency for 30 minutes, but as soon as 18:00 hit the latency went up to 5000ms and the lag spikes became very problematic.

Will, I understand your comment about the part that Blizzard has to play in this matter, but the shift at 18:00 is purely MWEb. It's as if a new set of rules kicks in at 18:00 and it is one of these that causes the issue at hand. This may be completely ignorant, but what function does the new rule set perform and why can't we not just have the rules that apply for 08:00 - 18:00 during the week?

I appreciate the lengths you seem to be going to resolve this, including the re-installation of WoW.
 
Ok, my report for the day as well, got home at about 17:30 and logged on with a 1000ms ping didn't do a tracert though (had to cook dinner).

Now here are the current details, as before all tracerts are done while I am logged on.

Server: Lightbringer
Time: 20:02

MWEB 384 Uncapped Unshaped
In game latency displayed as 6512ms (it actually dropped to 1978ms for about 2 seconds), tracert:
Tracing route to 213-248-127-130.customer.teliacarrier.com [213.248.127.130]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ***.***.***.***
2 28 ms 23 ms 21 ms ***-***-***-***.dsl.mweb.co.za [***.***.***.***]
3 25 ms 20 ms 105 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 22 ms 33 ms 25 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 134 ms 27 ms 32 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 67 ms 93 ms 38 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 245 ms 244 ms 246 ms 196.22.175.222
8 318 ms 247 ms 243 ms 149.6.98.5
9 275 ms 299 ms 251 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 291 ms 292 ms 246 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 283 ms 255 ms 245 ms ldn-b4-link.telia.net [213.248.70.237]
12 245 ms 244 ms 242 ms ldn-bb1-link.telia.net [80.91.251.18]
13 269 ms 375 ms 268 ms prs-bb2-link.telia.net [80.91.247.240]
14 260 ms 310 ms 259 ms ffm-bb1-link.telia.net [80.91.247.39]
15 317 ms 312 ms 260 ms ffm-b10-link.telia.net [80.91.251.250]

Switched over to Axxess account, no unshaped, in game latency displayed as 315ms, tracert:
Tracing route to 213-248-127-130.customer.teliacarrier.com [213.248.127.130]
over a maximum of 30 hops:

1 7 ms 2 ms 4 ms ***.***.***.***
2 15 ms 20 ms 19 ms ***-***-***-***.telkomadsl.co.za [***.***.***.***]
3 19 ms 22 ms 22 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
4 21 ms 23 ms 22 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 19 ms 23 ms 22 ms core2b-rba-te2-0-1.ip.isnet.net [168.209.1.182]
6 304 ms 300 ms 300 ms mi-za-rba-p6-gi2-0-0-302.ip.isnet.net [168.209.164.173]
7 298 ms 299 ms 298 ms mi-us-25b-p2-po2-1.ip.isnet.net [168.209.160.213]
8 306 ms 307 ms 300 ms core2a-ny-gi1-0-19-302.ip.isnet.net [168.209.164.124]
9 298 ms 296 ms 295 ms 168.209.245.1
10 303 ms 303 ms 318 ms xe-6-1.r02.nycmny03.us.bb.gin.ntt.net [129.250.193.253]
11 * * * Request timed out.
12 298 ms 301 ms 302 ms nyk-b1-link.telia.net [213.248.69.53]
13 366 ms 301 ms 323 ms nyk-bb1-link.telia.net [80.91.248.141]
14 298 ms 300 ms 300 ms prs-bb1-link.telia.net [80.91.253.121]
15 313 ms 312 ms 309 ms ffm-bb1-link.telia.net [80.91.246.206]
16 333 ms 305 ms 308 ms ffm-b10-link.telia.net [80.91.251.120]

Ok and then again MWEB 384 Uncapped Unshaped running with WTFast, ingame latency displayed as 250ms, tracert:
Tracing route to 213-248-127-130.customer.teliacarrier.com [213.248.127.130]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ***.***.***.***
2 19 ms 23 ms 23 ms ***-***-***-***.dsl.mweb.co.za [***.***.***.***]
3 19 ms 26 ms 23 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 24 ms 53 ms 24 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 22 ms 25 ms 25 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 49 ms 49 ms 57 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 245 ms 243 ms 248 ms 196.22.175.222
8 258 ms 251 ms 246 ms 149.6.98.5
9 337 ms 256 ms 249 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 248 ms 243 ms 246 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 244 ms 246 ms 245 ms ldn-b4-link.telia.net [213.248.70.237]
12 245 ms 242 ms 244 ms ldn-bb2-link.telia.net [80.91.249.133]
13 258 ms 338 ms 269 ms prs-bb1-link.telia.net [80.91.247.34]
14 262 ms 274 ms 268 ms ffm-bb1-link.telia.net [80.91.247.232]
15 281 ms 262 ms 277 ms ffm-b10-link.telia.net [80.91.247.185]
 
Hi WGS.

The thing is I'm not entirely convinced that the 18h00 shift is purely ours as I saw some mentions on the EU forums of problems during early evening when it becomes raiding prime time. There are obviously things that happen on our network at these times. Its early evening and the allocation to shaped traffic increases, but we have been over these numbers repeatedly over the last few days and there is more than sufficient allocation for priority traffic. We've also given gaming traffic the highest priority possible, we've tried completely bypassing the traffic manager for the test realms and even bypassed our caching servers as of this evening and it has made hardly a noticeable difference. If you look at the latency figures on our network at the moment they are actually excellent and if there was a congestion, or overutilization problem anywhere on our network causing this I can't imagine that I wouldn't have the FPS players in here screaming blue murder as well as those games should be far more sensitive to issues like this.

There is obviously a logical explanation for this, but at the moment it is particularly elusive one. We will keep looking though.
 
Last edited:
I'm sure this must have been covered before, but why would using a service like WTFast improve an unshaped MWEB connection?
 
@Arzy, I'm pretty sure that 213-248-127-130 is just the Blizzard authentication server. Run a NETSTAT in Command Prompt to get the actual realm IPs (usually 2 of them on the same subnet.
 
StevenC said:
Have a free IP table on me for all the realms!
http://www.wowwiki.com/EU_English_realms_info#WikiaArticle

Enjoy :)

Or for faster referencing - 80.239.185.26 for Lightbringer.
Click to expand...

Those are likely to be wrong. They are definitely wrong for Steamwheadle Cartel (actually 195.12.237.28 through 195.12.237.31 from what I have seen rather than 80.239.181.20) . Do a Netstat to check. Apart from which there is now an IP range rather than a single address - maybe since the recent patch. I never checked before then.
 
Last edited:
I've created an account purely to also drop a message to say that I can't play on [EU Laughing Skull] with my mweb shaped uncapped account. But I have to admit what Blustorm said on page 42 is probably the key to this whole issue . (IMO this is what mweb need to check out) - If I chat in guild, trade etc its almost instantaneous, however the game itself is just complete lag. Casting, interacting with the world will range from 10k latency all the way to 30k plus. I am at work right now, so posting pics and netstat tests arent possible, but I will try do something about it tonight.

I am finding it really tough at the moment having to switch to my WA account every time I want to log onto wow. I have already capped the account 3 times this month, due to it still running in the background instead of having mweb as my main account. Unfortunately, and don't take this as a threat or w/e, but I did not purchase my mweb account only for downloading. I do a lot of online gaming, and having an uncapped account for patches/ updates/ teamspeak/ and the game itself. If my mweb account is null and void in this regard, I really don't see the reason why I need to continue using this package. I'm forking out cash for something I'm barely using. My WA account was supposed to only be used for raiding on heavily slow nights or when I need a speedy response in game. Right now, I cannot play at all unless I connect to WA.

Another thing to bring in to the equation is that yes, this lag did start when they (Blizzard) released 4.0.1 but my thoughts were that the lag was from everyone needing to download the patch etc. Its been 3 odd weeks already, and no improvement/changes on the Mweb side of things.

@Will@Mweb, other than screenshots and netstat, traceroutes... There HAS to be something else you might need from us. As it appears the info we have provided so far, doesn't help.
 
Same issues

To add my 2c, I recently started WOW again and have thusfar been unable to play since I bought my 2 month game card 3 weeks ago.
I too am using Mweb uncapped 384k and on the odd occasion that I can actually login, pings are anything from 6k to 30k, and then I get disconnected.
I used a trial account with Battleping to get a 20min (before they disconnect me) fix and check my auctions and mail.
I am on Twilight's Hammer EU and have tried reinstallation, repair of game files, deleting caches, addons, etc.
Today I bought 5Gb of unshaped data from Axxess and BAM, I have 300ms ping without Battleping...

MWEB, come on hey.. fix the issue, and if you can't, get an outside consultant from say, Axxess to fix it for you...
 
Ok guys an interesting piece of news.

So a tunneling service im using uses Port 10800 which is fine during the day and after 6pm it goes to hell. Now heres the interesting part, this same service changed the port they used on one server to another port and now i have 300-350ms any time during the day. With normal mweb (without tunneling service) it also goes to hell. So what does this mean for us?

Well this has to mean that "rules" change on ports right after 6, on certain ports and not on others or those ports get shaped after 6pm. That seems like the only solution that makes sense to me. So clearly the port mweb without a tunneling servers uses to connect to our specific servers we play on also gets its "rules" changed or gets shaped after 6pm and gets changed back at 8am each morning.

Please lemme know...
 
smokemaryjane said:
I am finding it really tough at the moment having to switch to my WA account every time I want to log onto wow. I have already capped the account 3 times this month, due to it still running in the background instead of having mweb as my main account..
Click to expand...

Easy fix , leave mweb account on your router, then create a pppoe dialup with your WA details and connect when nessasary. Been doing it like that for about 3 weeks now myself.
 
Last edited:
freaker76 said:
Easy fix , leave mweb account on your router then create a pppoe dialup with you WA details and connect when nessasary. Windows will as a rule use pppoe dialup before asking the router. Been doing it like that for about 3 weeks now myself.
Click to expand...

Yes true, and I am doing that already. BUT.. I keep forgetting its connected (btw have you noticed my username?)

I have other pc's in my house, that connect using mweb from the router (as they don't do online gaming)
But with my pc I have to constantly switch connections, depending on if I want to log onto WOW. It gets a bit much at times.

If I want to stream some internet radio (which I do a lot of) I can't do it now during a gaming session. Or I just eat up my WA bandwidth. I am so used to having my router be connected, that I overlook the fact that I'm still connected on the pc.

Another thing to bear in mind: I have had to replace my telkom router since this whole fiasco kicked in, as I used to just switch pppoe to bridged on the router, every time I need to connect to WOW. Since then, I have bought a new router that supports 'half-bridged' mode. ie stay connected via mweb on the router, and have the functionality to dialup from the pc at the same time.

More costs involved than what's required, but I thought the problem was first on my side.
 
well

my connection was fine whole week and i could play during the night as well now everything is back to normal 2k ping yay <3 this
 
Played happily from 17:00 to 18:00 and then, like clockwork DC'd and returned to 5000ms latency - unplayable. :wtf:
 
Oh Look... 18:00 bug hit...

C:\Documents and Settings\DummyMe>netstat

Active Connections

Proto Local Address Foreign Address State
TCP DummyMe:2950 213-248-127-130.customer.teliacarrier.com:1119 ESTABLISHED
TCP DummyMe:2952 195.12.234.241:1119 ESTABLISHED
TCP DummyMe:3047 195.12.234.240:6112 TIME_WAIT
TCP DummyMe:3057 195.12.235.141:1119 ESTABLISHED
TCP DummyMe:3412 DummyMe:3413 ESTABLISHED
TCP DummyMe:3413 DummyMe:3412 ESTABLISHED
TCP DummyMe:3414 DummyMe:3415 ESTABLISHED
TCP DummyMe:3415 DummyMe:3414 ESTABLISHED
TCP DummyMe:4722 DummyMe:12080 CLOSE_WAIT
TCP DummyMe:12080 DummyMe:3055 TIME_WAIT
TCP DummyMe:12080 DummyMe:3058 TIME_WAIT

C:\Documents and Settings\DummyMe>tracert 195.12.234.240

Tracing route to 195.12.234.240 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 10.0.0.1
2 9 ms 9 ms 9 ms 41-132-10-1.dsl.mweb.co.za [41.132.10.1]
3 244 ms 244 ms 236 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 * * * Request timed out.
5 465 ms * * tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * 1097 ms 41-132-10-1.dsl.mweb.co.za [41.132.10.1]
11 773 ms 3636 ms * 41-132-10-1.dsl.mweb.co.za [41.132.10.1]
12 * * 269 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
13 3741 ms * * tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
14 * 767 ms 796 ms prs-b4-link.telia.net [80.91.251.45]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 244 ms * * 149.6.98.17
19 * 3235 ms * ldn-b4-link.telia.net [213.248.70.237]
20 * 244 ms * ldn-bb1-link.telia.net [80.91.250.234]
21 1799 ms * * prs-bb2-link.telia.net [80.91.247.240]
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.

C:\Documents and Settings\DummyMe>tracert 213-248-127-130.customer.
teliacarrier.com

Tracing route to 213-248-127-130.customer.teliacarrier.com [213.248.127.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * 275 ms * vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 548 ms 533 ms * tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * 243 ms 242 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 241 ms 241 ms 240 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 * * * Request timed out.
12 * * 242 ms ldn-bb2-link.telia.net [80.91.251.14]
13 * * 252 ms prs-bb1-link.telia.net [80.91.247.254]
14 251 ms 250 ms 250 ms ffm-bb2-link.telia.net [80.91.246.180]
15 251 ms 331 ms 251 ms ffm-b10-link.telia.net [80.91.251.120]
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.

And now even chat didn't happen....
Now a BIG screenshot (215kb) of what it's like... notice all the buffs and debuffs on 0sec... yet only 1133ms latency.... not...
album.php


Oh, and Boss died at 18:00.... this screenie is from 2 mins later...

Then, after a restart of the router...

C:\Documents and Settings\DummyMe>tracert 213-248-127-130.customer.
teliacarrier.com

Tracing route to 213-248-127-130.customer.teliacarrier.com [213.248.127.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.42
2 9 ms 8 ms 9 ms 41-132-10-1.dsl.mweb.co.za [41.132.10.1]
3 10 ms 10 ms 10 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 27 ms 28 ms 26 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 21 ms 19 ms 21 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 61 ms 53 ms 47 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]

7 280 ms 265 ms 6 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 419 ms 127 ms 278 ms 149.6.98.5
9 249 ms 249 ms 250 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
10 1072 ms 266 ms 301 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.
74]
11 264 ms 265 ms 257 ms ldn-b4-link.telia.net [213.248.70.237]
12 273 ms 273 ms 276 ms ldn-bb1-link.telia.net [80.91.250.234]
13 * 301 ms 266 ms prs-bb1-link.telia.net [80.91.247.34]
14 300 ms 281 ms 280 ms ffm-bb2-link.telia.net [80.91.246.180]
15 292 ms 318 ms 108 ms prs-b4-link.telia.net [80.91.247.51]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
 
Wow, and here I thought it was just me. So I see others suffer from the same 18h00 bug, where all connectivity goes for a ball and takes about 3/4 minutes to rectify itself.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X