-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Do you bet on sports?
MWEB Gaming Feedback
- Thread starter Will@MWEB
- Start date
Arzy
Honorary Master
Ok, so I play on the Lightbringer EU Server (213.248.127.130), I've tried this with 2 ISP's now. The first is my MWEB Uncapped Unshaped account and the second an Axxess Uncapped account. Both tracerts are with WoW running, but nothing else. Results as follows:
MWEB Uncapped Unshaped 384, in game latency displayed as 606ms, tracert:
1 <1 ms <1 ms <1 ms ***.***.***.***
2 21 ms 18 ms 26 ms ***.***.***.***.dsl.mweb.co.za [***.***.***.***]
3 22 ms 19 ms 20 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 22 ms 23 ms 22 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 24 ms 29 ms 24 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 47 ms 77 ms 58 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 260 ms 450 ms 258 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 259 ms 265 ms 259 ms 149.6.98.17
9 463 ms 436 ms 286 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 278 ms 277 ms 281 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 279 ms 278 ms 280 ms ldn-b4-link.telia.net [213.248.70.237]
12 259 ms 265 ms 262 ms ldn-bb2-link.telia.net [80.91.251.14]
13 270 ms 271 ms 267 ms prs-bb2-link.telia.net [80.91.247.240]
14 292 ms 278 ms 279 ms ffm-bb1-link.telia.net [80.91.247.39]
15 295 ms 294 ms 295 ms ffm-b10-link.telia.net [80.91.251.122]
Axxess Uncapped (Not the premium unshaped one), in game latency displayed as 373ms, tracert:
1 <1 ms <1 ms <1 ms ***.***.***.***
2 20 ms 19 ms 27 ms ***-***-***-***.telkomadsl.co.za [***.***.***.***]
3 20 ms 21 ms 20 ms 196.38.73.85
4 24 ms 25 ms 22 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 23 ms 21 ms 21 ms core2b-rba-te2-0-0.ip.isnet.net [196.26.0.182]
6 291 ms 291 ms 291 ms mi-za-rba-p6-gi2-0-0-310.ip.isnet.net [168.209.164.39]
7 292 ms 290 ms 291 ms mi-us-25b-p2-po1-3-0.ip.isnet.net [168.209.163.9]
8 286 ms 288 ms 288 ms core2a-ny-gi1-0-19-310.ip.isnet.net [168.209.164.72]
9 289 ms 291 ms 288 ms 168.209.244.3
10 288 ms 289 ms 287 ms xe-6-1.r02.nycmny03.us.bb.gin.ntt.net [129.250.193.253]
11 463 ms 298 ms 450 ms xe-8-4.r03.nycmny01.us.bb.gin.ntt.net [129.250.2.46]
12 287 ms 288 ms 290 ms nyk-b1-link.telia.net [213.248.69.53]
13 289 ms 288 ms 288 ms nyk-bb1-link.telia.net [80.91.248.149]
14 291 ms 311 ms 290 ms prs-bb1-link.telia.net [80.91.251.97]
15 321 ms 319 ms 316 ms ffm-bb1-link.telia.net [80.91.252.230]
16 297 ms 318 ms 317 ms ffm-b10-link.telia.net [80.91.251.122]
Ok, and then last but not least, MWEB again with WTFast running, in game latency displayed as 255ms, tracert:
1 <1 ms <1 ms <1 ms ***.***.***.***
2 18 ms 21 ms 21 ms ***-***-***-***.dsl.mweb.co.za [***.***.***.***]
3 20 ms 21 ms 22 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 21 ms 21 ms 22 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 22 ms 22 ms 26 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 24 ms 26 ms 26 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 262 ms 261 ms 261 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 259 ms 262 ms 261 ms 149.6.98.17
9 280 ms 278 ms 281 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 278 ms 278 ms 283 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 284 ms 277 ms 277 ms ldn-b4-link.telia.net [213.248.70.237]
12 276 ms 261 ms 260 ms ldn-bb1-link.telia.net [80.91.250.234]
13 266 ms 270 ms 267 ms prs-bb2-link.telia.net [80.91.247.240]
14 296 ms 294 ms 294 ms ffm-bb2-link.telia.net [80.91.246.180]
15 278 ms 295 ms 277 ms ffm-b10-link.telia.net [80.91.251.250]
MWEB Uncapped Unshaped 384, in game latency displayed as 606ms, tracert:
1 <1 ms <1 ms <1 ms ***.***.***.***
2 21 ms 18 ms 26 ms ***.***.***.***.dsl.mweb.co.za [***.***.***.***]
3 22 ms 19 ms 20 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 22 ms 23 ms 22 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 24 ms 29 ms 24 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 47 ms 77 ms 58 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 260 ms 450 ms 258 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 259 ms 265 ms 259 ms 149.6.98.17
9 463 ms 436 ms 286 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 278 ms 277 ms 281 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 279 ms 278 ms 280 ms ldn-b4-link.telia.net [213.248.70.237]
12 259 ms 265 ms 262 ms ldn-bb2-link.telia.net [80.91.251.14]
13 270 ms 271 ms 267 ms prs-bb2-link.telia.net [80.91.247.240]
14 292 ms 278 ms 279 ms ffm-bb1-link.telia.net [80.91.247.39]
15 295 ms 294 ms 295 ms ffm-b10-link.telia.net [80.91.251.122]
Axxess Uncapped (Not the premium unshaped one), in game latency displayed as 373ms, tracert:
1 <1 ms <1 ms <1 ms ***.***.***.***
2 20 ms 19 ms 27 ms ***-***-***-***.telkomadsl.co.za [***.***.***.***]
3 20 ms 21 ms 20 ms 196.38.73.85
4 24 ms 25 ms 22 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 23 ms 21 ms 21 ms core2b-rba-te2-0-0.ip.isnet.net [196.26.0.182]
6 291 ms 291 ms 291 ms mi-za-rba-p6-gi2-0-0-310.ip.isnet.net [168.209.164.39]
7 292 ms 290 ms 291 ms mi-us-25b-p2-po1-3-0.ip.isnet.net [168.209.163.9]
8 286 ms 288 ms 288 ms core2a-ny-gi1-0-19-310.ip.isnet.net [168.209.164.72]
9 289 ms 291 ms 288 ms 168.209.244.3
10 288 ms 289 ms 287 ms xe-6-1.r02.nycmny03.us.bb.gin.ntt.net [129.250.193.253]
11 463 ms 298 ms 450 ms xe-8-4.r03.nycmny01.us.bb.gin.ntt.net [129.250.2.46]
12 287 ms 288 ms 290 ms nyk-b1-link.telia.net [213.248.69.53]
13 289 ms 288 ms 288 ms nyk-bb1-link.telia.net [80.91.248.149]
14 291 ms 311 ms 290 ms prs-bb1-link.telia.net [80.91.251.97]
15 321 ms 319 ms 316 ms ffm-bb1-link.telia.net [80.91.252.230]
16 297 ms 318 ms 317 ms ffm-b10-link.telia.net [80.91.251.122]
Ok, and then last but not least, MWEB again with WTFast running, in game latency displayed as 255ms, tracert:
1 <1 ms <1 ms <1 ms ***.***.***.***
2 18 ms 21 ms 21 ms ***-***-***-***.dsl.mweb.co.za [***.***.***.***]
3 20 ms 21 ms 22 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 21 ms 21 ms 22 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 22 ms 22 ms 26 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 24 ms 26 ms 26 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 262 ms 261 ms 261 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 259 ms 262 ms 261 ms 149.6.98.17
9 280 ms 278 ms 281 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 278 ms 278 ms 283 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 284 ms 277 ms 277 ms ldn-b4-link.telia.net [213.248.70.237]
12 276 ms 261 ms 260 ms ldn-bb1-link.telia.net [80.91.250.234]
13 266 ms 270 ms 267 ms prs-bb2-link.telia.net [80.91.247.240]
14 296 ms 294 ms 294 ms ffm-bb2-link.telia.net [80.91.246.180]
15 278 ms 295 ms 277 ms ffm-b10-link.telia.net [80.91.251.250]
Okay, so i logged onto Laughing skull with a level 1 toon. Ping is 300 on that with WTfast, I log onto Twilights hammer EU and boom, insane latency. Now, before we think its a wow server issue, on telkom its still 270 on TH EU.
I did a ipconfig /dnsflush then renew and release.
On mweb its still insane latency aka 5k + on twilights hammer. So how can this be? If i run battleping 20 min trail + mweb its 300ms on TH EU. If i dont use a tunneling service its 5k+ on TH EU.
Will, i have reset my router many times, many many many. Every few hours when i want to check how the ping is now. Anything else i can do?
To recap, its fine on Telkom, its fine with battleping and mweb. Its fine on telkom and WTfast.
Its not fine on mweb or mweb with wtfast.
Its fine on Laughing skull EU. Its not fine on the realm i have all my characters.
Edit: My mweb connection and my LAN connection both have DNS set to automatic, using bridge mode to connect.
I did a ipconfig /dnsflush then renew and release.
On mweb its still insane latency aka 5k + on twilights hammer. So how can this be? If i run battleping 20 min trail + mweb its 300ms on TH EU. If i dont use a tunneling service its 5k+ on TH EU.
Will, i have reset my router many times, many many many. Every few hours when i want to check how the ping is now. Anything else i can do?
To recap, its fine on Telkom, its fine with battleping and mweb. Its fine on telkom and WTfast.
Its not fine on mweb or mweb with wtfast.
Its fine on Laughing skull EU. Its not fine on the realm i have all my characters.
Edit: My mweb connection and my LAN connection both have DNS set to automatic, using bridge mode to connect.
Last edited:
freaker76
Well-Known Member
Hi Will
I stopped all downloads , bribed my wife and kid off facebook, reset the router and connected up with a 4meg uncapped mweb account my ping in wow started at 27000
after a few minutes it settles to around 8k
i am in Cape town Muizenberg
i am on emerald dream realm EU
I stopped all downloads , bribed my wife and kid off facebook, reset the router and connected up with a 4meg uncapped mweb account my ping in wow started at 27000
after a few minutes it settles to around 8k
i am in Cape town Muizenberg
i am on emerald dream realm EU
Last edited:
Jovs
Senior Member
Hi Will,
logged in a few times again, restarting WoW/PC/router makes no difference. Have absolutely nothing else downloading/using the internet while I play WoW.
DNS on PC/router is on auto, also did a flushdns.
Problem for me started since the latest patch from Blizzard.
Seems like WoW is using a few different IPs to connect to my realm - Draenor:
Also got a few screen shots of the in-game latency meter (from about 18:20-18:50):
Trace routes to the 3 IPs used the first time I logged in:
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 18 ms 19 ms 26 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
3 20 ms 21 ms 20 ms 196-28-178-190.adsl.mweb.co.za [196.28.178.190]
4 61 ms 67 ms 66 ms 196.22.169.45
5 48 ms 41 ms 43 ms 196.22.169.61
6 43 ms 46 ms 43 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 78 ms 89 ms 95 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
8 261 ms 261 ms 264 ms 196.22.175.214
9 394 ms 413 ms 457 ms 149.6.98.17
10 297 ms 286 ms 296 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 262 ms 261 ms 321 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
12 291 ms 297 ms 299 ms ldn-b4-link.telia.net [213.248.70.237]
13 267 ms 263 ms 273 ms ldn-bb1-link.telia.net [80.91.249.77]
14 332 ms 269 ms 269 ms prs-bb2-link.telia.net [80.91.247.240]
15 342 ms 278 ms 280 ms ffm-bb2-link.telia.net [80.91.246.184]
16 297 ms 296 ms 276 ms ffm-b10-link.telia.net [80.91.247.189]
17 * * * Request timed out.
Tracing route to 213.12.234.177 over a maximum of 30 hops
1 <1 ms <1 ms 4 ms 192.168.0.1
2 22 ms 21 ms 20 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
3 20 ms 20 ms 23 ms 196-28-178-178.adsl.mweb.co.za [196.28.178.178]
4 40 ms 42 ms 42 ms 196.22.169.49
5 45 ms 39 ms 42 ms 196.22.169.61
6 44 ms 44 ms 42 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249] reports: Destination host unreachable.
Trace complete.
Tracing route to 213.12.234.176 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 41 ms 29 ms 21 ms 196-28-178-178.adsl.mweb.co.za [196.28.178.178]
4 48 ms 42 ms 54 ms 196.22.169.45
5 51 ms 45 ms 80 ms 196.22.169.61
6 59 ms 43 ms 61 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249] reports: Destination host unreachable.
Trace complete.
Staying in Gordons Bay, Western Cape and playing on MWeb 384kbs uncapped without any tunnelling services.
Please let me know if there's any other info that you require.
Last edited:
Ok just logged in at 10:15PM tonight on MWEB account in Borean Tundra on an alt to get a "fair" reading. I have done a reboot on router and PC, no downloads running.
The following screenshot of ingame latency follows:
which shows 11382ms latency.
Tracert is as follows:
Tracing route to 195.12.244.200 over a maximum of 30 hops
1 * * * Request timed out.
2 19 ms 19 ms 19 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 132 ms 138 ms 142 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 176 ms 176 ms 166 ms 196.22.169.45
5 223 ms 185 ms 196 ms 196.22.169.61
6 140 ms 148 ms 154 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 236 ms 233 ms 231 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
8 362 ms 346 ms 343 ms 196.22.175.222
9 362 ms 362 ms 391 ms 149.6.98.17
10 416 ms 397 ms 373 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 421 ms 428 ms * te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
12 434 ms 414 ms 404 ms ldn-b4-link.telia.net [213.248.70.237]
13 411 ms 417 ms 431 ms ldn-bb1-link.telia.net [80.91.249.77]
14 387 ms 385 ms 401 ms adm-bb1-link.telia.net [80.91.245.107]
15 372 ms 373 ms 364 ms adm-b7-link.telia.net [80.91.245.135]
16 * * * Request timed out.
17 * * * Request timed out.
Downloading Battleping now - running at full line speed just to note so no problem on the HTTP side of things.
Posting results as follows (after reboot, leaving post here).
Running at a comfy 425ms, with some of the best performance I have ever seen in WoW. I might even consider an account with these guys!
Screenshot:
Tracert:
Tracing route to 195.12.244.200 over a maximum of 30 hops
1 * * * Request timed out.
2 20 ms 18 ms 21 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 95 ms 94 ms 93 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 162 ms 172 ms 179 ms 196.22.169.45
5 196 ms 191 ms 185 ms 196.22.169.61
6 220 ms 176 ms 168 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 139 ms 132 ms 123 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
8 375 ms 397 ms 413 ms 196.22.175.222
9 396 ms 398 ms 423 ms 149.6.98.17
10 416 ms 418 ms 431 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 * 380 ms 374 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
12 411 ms 424 ms 433 ms ldn-b4-link.telia.net [213.248.70.237]
13 413 ms 409 ms 411 ms ldn-bb1-link.telia.net [80.91.249.77]
14 417 ms 415 ms 409 ms adm-bb3-link.telia.net [80.91.250.84]
15 394 ms 389 ms 394 ms adm-b7-link.telia.net [80.91.245.135]
16 * * * Request timed out.
17 * * * Request timed out.
So there you have it then, some info for the techies. I am playing on Eonar EU realm, suffering bad latency there.
The WoWWiki page for the server is as follows: http://www.wowwiki.com/Server:Eonar_Europe
The List of all the WoW EU IP Addresses is found on this page: http://www.wowwiki.com/EU_English_realms_info
I see Eonar is actually 213.248.123.49 =( Maybe because it is in Sweden it may have something to do with differing latency reports between the realms.
1 moar edit: Loaded up a lvl 1 toon on Laughing Skull, very playable 600ms without Battleping, just normal MWEB account.
The following screenshot of ingame latency follows:
which shows 11382ms latency.Tracert is as follows:
Tracing route to 195.12.244.200 over a maximum of 30 hops
1 * * * Request timed out.
2 19 ms 19 ms 19 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 132 ms 138 ms 142 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 176 ms 176 ms 166 ms 196.22.169.45
5 223 ms 185 ms 196 ms 196.22.169.61
6 140 ms 148 ms 154 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 236 ms 233 ms 231 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
8 362 ms 346 ms 343 ms 196.22.175.222
9 362 ms 362 ms 391 ms 149.6.98.17
10 416 ms 397 ms 373 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 421 ms 428 ms * te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
12 434 ms 414 ms 404 ms ldn-b4-link.telia.net [213.248.70.237]
13 411 ms 417 ms 431 ms ldn-bb1-link.telia.net [80.91.249.77]
14 387 ms 385 ms 401 ms adm-bb1-link.telia.net [80.91.245.107]
15 372 ms 373 ms 364 ms adm-b7-link.telia.net [80.91.245.135]
16 * * * Request timed out.
17 * * * Request timed out.
Downloading Battleping now - running at full line speed just to note so no problem on the HTTP side of things.
Posting results as follows (after reboot, leaving post here).
Running at a comfy 425ms, with some of the best performance I have ever seen in WoW. I might even consider an account with these guys!
Screenshot:
Tracert:
Tracing route to 195.12.244.200 over a maximum of 30 hops
1 * * * Request timed out.
2 20 ms 18 ms 21 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 95 ms 94 ms 93 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 162 ms 172 ms 179 ms 196.22.169.45
5 196 ms 191 ms 185 ms 196.22.169.61
6 220 ms 176 ms 168 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 139 ms 132 ms 123 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
8 375 ms 397 ms 413 ms 196.22.175.222
9 396 ms 398 ms 423 ms 149.6.98.17
10 416 ms 418 ms 431 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 * 380 ms 374 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
12 411 ms 424 ms 433 ms ldn-b4-link.telia.net [213.248.70.237]
13 413 ms 409 ms 411 ms ldn-bb1-link.telia.net [80.91.249.77]
14 417 ms 415 ms 409 ms adm-bb3-link.telia.net [80.91.250.84]
15 394 ms 389 ms 394 ms adm-b7-link.telia.net [80.91.245.135]
16 * * * Request timed out.
17 * * * Request timed out.
So there you have it then, some info for the techies. I am playing on Eonar EU realm, suffering bad latency there.
The WoWWiki page for the server is as follows: http://www.wowwiki.com/Server:Eonar_Europe
The List of all the WoW EU IP Addresses is found on this page: http://www.wowwiki.com/EU_English_realms_info
I see Eonar is actually 213.248.123.49 =( Maybe because it is in Sweden it may have something to do with differing latency reports between the realms.
1 moar edit: Loaded up a lvl 1 toon on Laughing Skull, very playable 600ms without Battleping, just normal MWEB account.
Last edited:
Well it's 12am, just saw the message now and tried it out. Created a new toon, had about 600-700ms in game (durotar). Abilities were fast casting. Not using Battleping.
Will wait till evening again to give it a better try when things are more congested.
Also, your name seems familiar, you didn't happen to play a druid on some of the South African / Namibian realms back in early Vanilla did you?
Will wait till evening again to give it a better try when things are more congested.
Also, your name seems familiar, you didn't happen to play a druid on some of the South African / Namibian realms back in early Vanilla did you?
Hehe, no steven i did not 
Thou i have played allot of games in the SA community over the years like sc, war3 and dota Thx for checking.
Btw yeh, for some reason battleping avoids the error on an mweb account, i dont have a creditcard thou so cant really get an account with them
Thou i have played allot of games in the SA community over the years like sc, war3 and dota Thx for checking.Btw yeh, for some reason battleping avoids the error on an mweb account, i dont have a creditcard thou so cant really get an account with them
WGS2010
Active Member
I have spent the last hour trying to log into WoW - unsuccessfully. When I finally get in on my wife's account the latency is through the roof again.
So much for this issue being sorted out.
So much for this issue being sorted out.
Playing on laughing skull and still getting like 1000 to 2000 lat. :-(
WGS2010
Active Member
Still not able to even log into WoW. After an initial login on two accounts and super high latency followed by a DC, the game does not allow me to log in. Two hours that I'll never get back! This is something new and very unpleasnt.
I'm tired of this. Does anyone at MWeb actually know what they are doing?
Does anyone have advice about which ISP gives a consistent connection and decent support, as MWeb clearly are missing the boat here.
Here is trace:
1 1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 30 ms 29 ms 29 ms 41-133-42-1.dsl.mweb.co.za [41.133.42.1]
3 53 ms 58 ms 60 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 52 ms 58 ms 60 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 57 ms 58 ms 60 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 83 ms 83 ms 83 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 279 ms 281 ms 277 ms 196.22.175.210
8 285 ms 281 ms 278 ms 149.6.98.17
9 281 ms 277 ms 281 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 285 ms 280 ms 328 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 279 ms 281 ms 278 ms ldn-b4-link.telia.net [213.248.70.237]
12 278 ms 278 ms 281 ms ldn-bb2-link.telia.net [80.91.251.14]
13 287 ms 291 ms 288 ms prs-bb1-link.telia.net [80.91.247.254]
14 291 ms 290 ms 290 ms prs-b-link.telia.net [80.91.251.47]
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.
I'm tired of this. Does anyone at MWeb actually know what they are doing?
Does anyone have advice about which ISP gives a consistent connection and decent support, as MWeb clearly are missing the boat here.
Here is trace:
1 1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 30 ms 29 ms 29 ms 41-133-42-1.dsl.mweb.co.za [41.133.42.1]
3 53 ms 58 ms 60 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 52 ms 58 ms 60 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 57 ms 58 ms 60 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 83 ms 83 ms 83 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 279 ms 281 ms 277 ms 196.22.175.210
8 285 ms 281 ms 278 ms 149.6.98.17
9 281 ms 277 ms 281 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 285 ms 280 ms 328 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 279 ms 281 ms 278 ms ldn-b4-link.telia.net [213.248.70.237]
12 278 ms 278 ms 281 ms ldn-bb2-link.telia.net [80.91.251.14]
13 287 ms 291 ms 288 ms prs-bb1-link.telia.net [80.91.247.254]
14 291 ms 290 ms 290 ms prs-b-link.telia.net [80.91.251.47]
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.
The optimization I mentioned on Friday for traffic to certain realms was put in place this morning at 06h00 as a test
The following Realms have been put on the list:
DragonBlight
LightBringer
Draenor
Steamwheedle Cartel
Emerald Dream
Twilight Hammer
Eonar
This is just a test so please could users on those realms let us know what their experience is.
Thanks
Will
The following Realms have been put on the list:
DragonBlight
LightBringer
Draenor
Steamwheedle Cartel
Emerald Dream
Twilight Hammer
Eonar
This is just a test so please could users on those realms let us know what their experience is.
Thanks
Will
WGS2010
Active Member
Finally got on to WoW (Steamwheedle Cartel EU) - it appears the login issues had more to do with Blizzard than MWeb, so my apologies at getting angry at MWeb 
(Europeans obviously sleep in on Sundays).
The latency issue continues to be problematic though, even after router resets. Started the game with 23 000ms latency. It's unplayable!
Yesterday the game had playable latency of 650ms, which is normal for me. So whatever MWeb had in place Friday evening and Saturday seemed to work. Today is a different story though.
(Europeans obviously sleep in on Sundays).The latency issue continues to be problematic though, even after router resets. Started the game with 23 000ms latency. It's unplayable!
Yesterday the game had playable latency of 650ms, which is normal for me. So whatever MWeb had in place Friday evening and Saturday seemed to work. Today is a different story though.
WGS2010
Active Member
WoW (Steamwheedle Cartel EU) is TOTALLY unplayable today. I have had constantly high latency (over 5000ms) and huge spikes of over 40sec.
Hopefully the 'solution' worked on last week will point the MWeb techs in the right direction now. How complex is this problem if it has taken a couple of weeks to get us nowhere?
Hopefully the 'solution' worked on last week will point the MWeb techs in the right direction now. How complex is this problem if it has taken a couple of weeks to get us nowhere?
Gents I really just have to put this on the table again in response to WGS2010. There is still the possiblity that these are at least partially Blizzard patch related issues and that they have introduced something into their netcode which is not agreeable with certain ISP networks.
I've just been back to the Blizzard EU forums and there are numerous threads about xxK latency since the patch and I saw several mentions of a sudden spike in latency at certain times in the evening.
These users are all also reporting that traces are clean and they can find no logical cause for the issue.
We will put WoW back on the test bench again tomorrow and run a full analysis of the traffic to see if there is anything we have overlooked, but we have made some very significant changes already and the list of things we can still try is getting very short.
I've just been back to the Blizzard EU forums and there are numerous threads about xxK latency since the patch and I saw several mentions of a sudden spike in latency at certain times in the evening.
These users are all also reporting that traces are clean and they can find no logical cause for the issue.
We will put WoW back on the test bench again tomorrow and run a full analysis of the traffic to see if there is anything we have overlooked, but we have made some very significant changes already and the list of things we can still try is getting very short.
WGS2010
Active Member
I appreciate the quick response and effort on your part, Will.
What about MWeb speaking to other SA ISPs who are NOT having this issue? South Africans on Telkom and Axxess seem not to be experiencing the same issues at all. What are they doing that MWeb is doing, which is certainly part of the problem?
I am not keen to jump ship to another ISP, primarily through innate laziness (and an awareness of Greener Grass Syndrome) rather than a deep-seated brand loyalty, but the frustration is certainly coming to a head.
The primary difference there would be that their networks arent IPC based, which immediately means that we manage traffic in a completely different way to them and you're comparing apples and pears. What concerns me here is that clients of Virgin Media, O2 and BE to name a few are reporting similar issues in Europe, we will keep trying our best to crack this, but if so many people worldwide are suddenly having issues when does the onus fall onto Blizzard's shoulders to acknowledge and at least explain the problem so that we can put workarounds in place? Their forum reps are in complete denial that anything significant has changed on the connectivity side and there doesn't even seem to be any willingness on their part to open discussions with these ISPS to work together on solving the problem.
If we don't make any significant headway tomorrow I will attempt to approach Blizzard myself to see if I can get a response out of them on the matter.
Kind Regards
Will
If we don't make any significant headway tomorrow I will attempt to approach Blizzard myself to see if I can get a response out of them on the matter.
Kind Regards
Will
Jovs
Senior Member
Logged into Draenor realm a few times, give it some time to see if latency will settle down, but latency still very high.
12:15, 4601ms:
12:38, 5231ms:
13:00, 6562ms:
Have logged the problem with Blizzard about a week ago, but their response wasn't much of a help
The first thing I would recommend is that you contact your Internet Service Provider as this is happening outside of our own Network. I will however try my best to give you some advice to stabilize your connection and hopefully lower your ms or latency.
Making some small changes to the way your network controller handles data can help improve your connection.
First, follow these steps to reach the configuration area for your network controller:
- Click Start then Control Panel (ensure that you're on Classic View)
- Open 'Network and Sharing Centre'
- Click 'Manage network connections' (found in the left-hand menu)
- Right-click your 'Local Area Connection' (which shows Connected as the Status) and left-click Properties
- On the new window, click the Configure button
- On the next new window, click the Advanced tab
Once on the configuration page, set the Values of any Properties that mention 'Checksum Offload' or 'Hardware Checksumming' (or other similarly worded options) to Disable. If you have a 'Speed and Duplex' Property, setting the Value for this to '100mb Full' may also help.
After making any changes, click OK to save them, your connection will restart causing you to lose Internet connectivity during this time.
Next, we need to lower the Max MTU size of your connection.
1) Download and run DrTCP -> http://www.dslreports.com/drtcp
2) Select your Network Adapter and change MaxMTU to 1400. (Default value is 1500)
3) Press 'Apply' and try the game again.
I hope this helps and have a nice day.
If the problem continues, please reply to this email with the exact content of the error message you receive, and information on which of the above steps you were able to try.
Best Regards,
Blizzard
Entertainment Europe
Erik A.
Technical Support
http://eu.blizzard.com/support/
12:15, 4601ms:
12:38, 5231ms:
13:00, 6562ms:
Have logged the problem with Blizzard about a week ago, but their response wasn't much of a help
The first thing I would recommend is that you contact your Internet Service Provider as this is happening outside of our own Network. I will however try my best to give you some advice to stabilize your connection and hopefully lower your ms or latency.
Making some small changes to the way your network controller handles data can help improve your connection.
First, follow these steps to reach the configuration area for your network controller:
- Click Start then Control Panel (ensure that you're on Classic View)
- Open 'Network and Sharing Centre'
- Click 'Manage network connections' (found in the left-hand menu)
- Right-click your 'Local Area Connection' (which shows Connected as the Status) and left-click Properties
- On the new window, click the Configure button
- On the next new window, click the Advanced tab
Once on the configuration page, set the Values of any Properties that mention 'Checksum Offload' or 'Hardware Checksumming' (or other similarly worded options) to Disable. If you have a 'Speed and Duplex' Property, setting the Value for this to '100mb Full' may also help.
After making any changes, click OK to save them, your connection will restart causing you to lose Internet connectivity during this time.
Next, we need to lower the Max MTU size of your connection.
1) Download and run DrTCP -> http://www.dslreports.com/drtcp
2) Select your Network Adapter and change MaxMTU to 1400. (Default value is 1500)
3) Press 'Apply' and try the game again.
I hope this helps and have a nice day.
If the problem continues, please reply to this email with the exact content of the error message you receive, and information on which of the above steps you were able to try.
Best Regards,
Blizzard
Entertainment Europe
Erik A.
Technical Support
http://eu.blizzard.com/support/
Last edited: