MWEB Gaming Feedback

Hi Will,

All my characters is on Draenor (Location: Paris). Created a new character last night, on Magtheridon which is suggested for new players (Location: Frankfurt), have the same latency problems regardless of realm or lvl of character.
 
Frustrated

Will@MWEB said:
Something else I found out which may shed some light or be of interest is that South African players should have a much better experience on Realms which are hosted in Paris.
Click to expand...

I play on Dunemaul (Paris) Bloodscalp (Paris) Chamber of Aspects (Hamburg) Bronzebeard (Paris 2) Aerie Peak (Stockholm) and I'm having the same trouble as everyone else on every server.

If this worked it would also require me to spend roughly R2400 to transfer all of my level 80's (not that I could fit them all on one server anyway). I hope you aren't seriously recommending this as a solution.

If this latency problem isn't sorted out in the next couple of days (by the time I pay my account) I am going to be cancelling and moving onto the prepaid stuff from engen garages (no latency problems at all).

I just can't believe that a piece of paper from a petrol station is outperforming your service.

It's ridiculous.

The only reason I have internet at home is for WoW. I can do all my email, browsing, etc at work. This is a deal breaker for me.

P.S. I have tried the latency fix (two different ones), the new toon fix, messing with MTU's, blocking all blizzard downloaders and launchers with my firewall, rolling on different servers, and any other suggestion I could find. Unfortunately the problem isn't (and never has been) on my side. I know this because my mweb account is the only one I get this problem on.

Getting an uncapped account with you guys is starting to feel like a huge mistake.

Account: 512 uncapped shaped

Edit: I'd also like to add that the only reason I even got uncapped was so that I could run skype continuously while I play (uses more bandwidth than wow), for patches and to pre-order and download the digital copies of the expansions. I chatted to your sales people several times before I decided on the package I took, they assured me that the shaping wouldn't affect my gaming. I guess they spoke too soon.
 
Last edited:
Located in Paris as well for me.

Honestly this is a very deep problem and nothing easy will fix it. Going on for a very long time now too. This wont ever be fixed by some stupid "quick fix" this can only be fixed by mweb fixing it. NO end user tips will help. Tried everything, allot of us have. Need some real answers please.

Is it really going to get fixed? If not, just say so, otherwise your costing us all money. It is now the 31st of the month. Need to know that it will be fixed before the end of November so we can all cancel our accounts. Sorry to say this, but if its not fixed by end of November i cant see how allot of us would have a choice. Really really want to stay on mweb, but you cant blame us. The service which we pay for no longer works. It used to work fine. Btw its not suppose to be a threatening post in any sense, i really appreciate your help trying to sort it out Will, but you must understand its now becoming an issue paying for a broken service and being kept on a line/in the dark is actually costing us all money each month.
 
I give up.

So I have a few days off this week, nice long weekend, and wanted to play a bit of WoW.
With the current issues on my Mweb account, I decided to try a unshaped pre paid account from WebAfrica.
What a joke!!!!
I can hardly even open pages on their own website:
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 192.168.0.1
2 1934 ms 1960 ms 1958 ms wblv-ip-esr-3.ipnet.wa.co.za [41.185.83.1]
3 1964 ms 1987 ms 1984 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 2002 ms 1995 ms 2043 ms vl32.er.gw.cpt.za.wa.co.za [41.185.0.26]
5 2051 ms 2033 ms 2059 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 2236 ms 2264 ms 2288 ms lon-ip-dir-telecity-pos-1-1-1.telkom-ipnet.co.za [196.43.9.138]
7 2286 ms 2387 ms 2325 ms ldn-tch-i1-link.telia.net [213.155.141.153]
8 * 2363 ms 2404 ms ldn-b5-link.telia.net [80.91.250.209]
9 * 2405 ms 2411 ms ldn-bb1-link.telia.net [80.91.249.179]
10 2423 ms 2445 ms 2465 ms prs-bb1-link.telia.net [80.91.247.6]
11 * 2525 ms 2538 ms ffm-bb1-link.telia.net [80.91.246.204]
12 2534 ms 2552 ms 2483 ms ffm-b10-link.telia.net [80.91.247.187]
13 * * * Request timed out.

Think it's time to see if my very old 8bit gaming console is still working :p
 
Jovs that is not an ISP problem. Your latency is through the roof at the command line right from the word go. Either your Line is in very bad shape , or you have massive Telkom congestion, or you have something running locally that is maxing out your connection.
 
Sillicur said:
Located in Paris as well for me.

Honestly this is a very deep problem and nothing easy will fix it. Going on for a very long time now too. This wont ever be fixed by some stupid "quick fix" this can only be fixed by mweb fixing it. NO end user tips will help. Tried everything, allot of us have. Need some real answers please.

Is it really going to get fixed? If not, just say so, otherwise your costing us all money. It is now the 31st of the month. Need to know that it will be fixed before the end of November so we can all cancel our accounts. Sorry to say this, but if its not fixed by end of November i cant see how allot of us would have a choice. Really really want to stay on mweb, but you cant blame us. The service which we pay for no longer works. It used to work fine. Btw its not suppose to be a threatening post in any sense, i really appreciate your help trying to sort it out Will, but you must understand its now becoming an issue paying for a broken service and being kept on a line/in the dark is actually costing us all money each month.
Click to expand...

Sillicur I understand exactly where you're coming from and @MindSlyde no I'm not suggesting that you migrate realms, I'm just trying to eliminate all possible causes of the problem. If the experience for customers hosted in Paris was different to say, Frankfurt, then this would point to an upstream routing issue.

No-one is trying to keep you in the dark, or keep you on a line. I've shared as much information as I possibly can in terms of the fixes we've attempted so far. This problem is really at the point now where it completely defies logic and the intermittent test results are not helping. As I type this I am idling on Twilight Hammer with a 550 MS ping and have been for the last hour. All I can promise you at this point is that we will keep looking for a solution, or a workaround, but I can't tell you how long that is going to take.

EDIT: I have just installed the Curse Client and will load some add-ons and move into a heavily populate area as I've been told that inter-addon communication with mods such as Gearscore, can play a big part in latency.
 
Last edited:
Will@MWEB said:
Jovs that is not an ISP problem. Your latency is through the roof at the command line right from the word go. Either your Line is in very bad shape , or you have massive Telkom congestion, or you have something running locally that is maxing out your connection.
Click to expand...

Hi Will,
doesn't look like a line problem, trace routes from MWeb account is still pretty normal. Unless there's some HUGE difference between the way I connect to MWeb vs WebAfrica at the 2nd hop:
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 192.168.0.1
2 20 ms 19 ms 19 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
3 18 ms 19 ms 20 ms 196-28-178-178.adsl.mweb.co.za [196.28.178.178]
4 43 ms 43 ms 46 ms 196.22.169.45
5 42 ms 41 ms 41 ms 196.22.169.61
6 43 ms 46 ms 44 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 56 ms 54 ms 54 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
8 263 ms 264 ms 265 ms 196.22.175.214
9 271 ms 272 ms 273 ms 149.6.98.17
10 294 ms 454 ms 293 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 * 268 ms * te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
12 264 ms 264 ms 265 ms ldn-b4-link.telia.net [213.248.70.237]
13 271 ms 347 ms 302 ms ldn-bb1-link.telia.net [80.91.249.77]
14 281 ms 281 ms 283 ms prs-bb1-link.telia.net [80.91.254.209]
15 280 ms 283 ms 284 ms ffm-bb1-link.telia.net [80.91.254.204]
16 283 ms 307 ms 281 ms ffm-b10-link.telia.net [80.91.251.250]
17 * * * Request timed out.

I also close all other bandwidth using applications while playing WoW
 
Last edited:
Will you got a high level character on TH ?? The addon stuff is true yeh, it used to have some effect (especially in raids). GS was "fixed" recently and the addon doesnt spam data so much. Just for the record me and most of my friends have been running default bliz UI without any mods while we test latency.

I have found when making a new character on a realm the latency is 100% fine. Logging in with any old characters is the problem. Btw, you on a shaped uncapped account or unshaped uncapped account? (just so i know your on the same type of account as we are).
 
I am on Dunemaul right now with latency jumping between 1.2k and 6k.

Trace Route

Tracing route to host-37.wow-europe.com [80.239.179.37]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 19 ms 19 ms 19 ms 41-132-0-1.dsl.mweb.co.za [41.132.0.1]
3 49 ms 49 ms 50 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 50 ms 50 ms 50 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 54 ms 52 ms 51 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 55 ms 55 ms 55 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 274 ms 273 ms 274 ms 196.22.175.214
8 273 ms 274 ms 275 ms 149.6.98.5
9 * 310 ms 299 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 271 ms * * te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 273 ms 272 ms 271 ms ldn-b4-link.telia.net [213.248.70.237]
12 275 ms 273 ms 273 ms ldn-bb2-link.telia.net [80.91.254.21]
13 344 ms 281 ms 280 ms prs-bb1-link.telia.net [80.91.247.6]
14 * 282 ms 282 ms prs-b1-link.telia.net [80.91.250.249]
15 281 ms 281 ms 281 ms prs-tc-i1-link-telia.net [80.91.250.30]
16 * * 80-239-174-106.customer.teliacarrier.com [80.239.174.106] reports: Destination net unreachable.
Trace complete.

It's almost identical to my traces pre-patch.
 
Hi Sillicur no I gave away my WoW account when I stopped playing so this is a 'virgin' installation. Also the new vs old character issue is confusing and not consistent as I have seen the problem with a level one character standing in the street in Stormwind - this was on Lightbringer and the latency stayed over 2000 even after leaving the city and running all the way down to the Abbey, which was empty of other players.

What's even stranger is that I then created a new character on Doomhammer in the Night Elf Start area, with low latency, logged, went back to Lightbringer and the Latency was gone.
 
For me, issues started since patch 4.0.1 went live. They changed or broke something for sure.

In US they complaining about latency issues since 4.0.1 for ages now without a resolution.

My main issue is zoning into areas, I wait ages to zone in. When I zone in my latency jumps to 2k-6k ms and then normalizes to 350-400ms after good 15-20 minutes. Sometimes I disconnect when zoning in. Most of the time latency will normalize, but sometimes it will still try to catchup to whats going around you for like 30 minutes.

The 2k-6k is fake latency, its the server acting up when zoning in.
 
Last edited:
@MindSlyde If I create a level one on Dunemaul could you arrange transport for me to a heavily populated area - also please tell me Horde or Alliance?
 
Sure can. Alliance side. I can meet you on a mage and portal you to wherever, character: Malevola.

Might be slow going though, I have 13k latency right now in Ironforge.
 
ok thanks - I will create quickly and whisper you


I have a level one sitting on horde side right now with below 600ms - will be interesting to see this...
 
Apparently you don't accept whispers from low levels :p

Thaschom Level 1 Dwarf Pally, LFG :)
 
All this is good and all, but I just wanna know this one thing.
Why does wow work without any lag on a specific port and with insane lag on port 10800. How could it be anything else if as SOON as wow runs though a different port its 100% fine and playable 290ms. As soon as wow runs through port 10800 its instant 5k ping. Been switching back and forth like 10 times in this hour now, every time 10800 and the default wow server port (dunno what that is) is used, insane lag. As soon as the port gets changed its instant playable.
Doesnt it HAVE to be a prioritizing thing for that port or a shaping thing, i mean, i know you said the gaming ports are not being shaped, but doesnt it HAVE to be to give this test result?

Will, any chance u could maybe tell us whats the difference in rules / prioritizing / shaping of port 10800 to lets say, for example port 80.
 
Sillicur the big difference there is not the port. Normal wow traffic operates on multiple ports and communicates with multiple destinations. The tunneling service wraps it all up in a neat bundle and takes it to a point which is much closer to the WoW servers.

At this point my level 1 is standing in Dalaran on Dunemaul with 560ms latency, MindSlyde's is ranging from 1.6k and all the way up anywhere in game. All theories welcome?
 
Yeh i understand, but with the tunneling service on port 10800 its 5k ms and with the tunneling service on another port its 290ms. Both instances the tunneling service is running, only thing changing is the port used. Specifically the one connected to the game server, not login / char screen / launcher which all connect to different ports.

Dunno if that might help
 
I have noticed that incoming data to the game is being shaped more than the out going.
*Only Mweb gives me this problem. Not other ISPs yes other players(other countries) have noted it but keep in mind Telkom, Open Web do not.
*The problem is to do with the shaping policies. (No external fixes will work, might be possible but I doubt it.) Wow obviously changed their data stream type.

*I will give this program a ago today and see what I can pick up.
http://www.wowwiki.com/ChatThrottleLib:
ChatThrottleLib is a small, embeddable library by Mikk that keeps outbound chat and addon communication from exceeding the output rate limit in WoW that otherwise causes players to disconnect from the server. It also has a number of features that will help you make your addon communication run smoother!

Benefits of using ChatThrottleLib:

* You keep players from getting disconnected when your addon sends too much data
* You can easily prioritize your traffic in three priorities
* Communication to different peers is handled as individual flows. A long stream of data to "Alice" doesn't interrupt short bursts of traffic to "Bob".
* All AddOns using ChatThrottleLib count toward the same maximum, so multiple addons can't cause an overload. Priorities ensure that real-time traffic is still real-time. And addons are given a fair share of bandwidth, so one addon can't lock all others out.

I will also log the times I get spikes, when I get shaped. How it happens full progression report.
I have now gotten a program called net-limiter, I am able to see each incoming data, from where, the type, what is being shaped etc.
I will run though dungeons, different areas, different characters as there is a difference with their data types.



This down here, is a very good discussion for you to look at Will@MWEB
http://forum.o2.co.uk/viewtopic.php?f=12&t=54097&sid=addf8f224c579e3575ddbe62ba2b4ff2

Thank you for all the effort m8.
 
Last edited:
Thanks, that was actually one of the threads I did pick up on last week, but I'll give it a fresh read to see if any new information has come to light.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X