MWEB Gaming Feedback

I am on Twilights Hammer EU. If its a realm routing issue how do I fix it?
 
Blackhand said:
Its not only me as well. I have 3 IRL friends and a lot of guild mates who play on Mweb accounts, they've also had to resort to a tunneling service. Its a recent problem, like +-4 days ago. I actually went from level 1-83 without any problems at all on my Mweb account. Then I logged in after work and it was broken again, just like before the upgrades to Cape Town.

I'm a technical guy Will (Software Engineer) and I've had my DSL line pretty much since DSL has been in SA, so I know how to diagnose when there's a problem my side or when its out of my hands. In this case its out of my hands other than using a tunneling service. But I'll oblige and post some ping tests from Cape Town:

Local ping tests:

Pinging axxess.co.za [196.34.95.131] with 32 bytes of data:
Reply from 196.34.95.131: bytes=32 time=35ms TTL=50
Reply from 196.34.95.131: bytes=32 time=34ms TTL=50
Reply from 196.34.95.131: bytes=32 time=34ms TTL=50
Reply from 196.34.95.131: bytes=32 time=34ms TTL=50
Reply from 196.34.95.131: bytes=32 time=33ms TTL=50
Reply from 196.34.95.131: bytes=32 time=33ms TTL=50
Reply from 196.34.95.131: bytes=32 time=34ms TTL=50

Ping statistics for 196.34.95.131:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 35ms, Average = 33ms

ping www.mweb.co.za -t

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121
Reply from 196.2.63.110: bytes=32 time=12ms TTL=121

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 12ms, Average = 12ms

International ping test:

ping eu.darkfallonline.com -t

Pinging eu.darkfallonline.com [77.95.25.53] with 32 bytes of data:
Reply from 77.95.25.53: bytes=32 time=180ms TTL=45
Reply from 77.95.25.53: bytes=32 time=180ms TTL=45
Reply from 77.95.25.53: bytes=32 time=180ms TTL=45
Reply from 77.95.25.53: bytes=32 time=181ms TTL=45
Reply from 77.95.25.53: bytes=32 time=180ms TTL=45
Reply from 77.95.25.53: bytes=32 time=180ms TTL=45
Reply from 77.95.25.53: bytes=32 time=180ms TTL=45

Ping statistics for 77.95.25.53:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 181ms, Average = 180ms


ping bbc.co.uk -t

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=163ms TTL=112
Reply from 212.58.224.138: bytes=32 time=163ms TTL=112
Reply from 212.58.224.138: bytes=32 time=163ms TTL=112
Reply from 212.58.224.138: bytes=32 time=164ms TTL=112
Reply from 212.58.224.138: bytes=32 time=163ms TTL=112

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

And finally an international traceroute:

tracert eu.darkfallonline.com

Tracing route to eu.darkfallonline.com [77.95.25.53]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 11 ms 11 ms 196-28-178-178.adsl.mweb.co.za [196.28.178.178]

4 12 ms 11 ms 11 ms 196-28-179-11.adsl.mweb.co.za [196.28.179.11]
5 13 ms 13 ms 12 ms 196-28-178-97.adsl.mweb.co.za [196.28.178.97]
6 163 ms 162 ms 162 ms 196.22.164.2
7 164 ms 164 ms 164 ms 149.6.98.5
8 163 ms 163 ms 163 ms te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.
169]
9 163 ms 163 ms 163 ms te7-2.mpd02.lon01.atlas.cogentco.com [130.117.0.
97]
10 163 ms 163 ms 163 ms ldn-b4-link.telia.net [213.248.70.237]
11 163 ms 163 ms 162 ms ldn-bb1-link.telia.net [80.91.252.197]
12 172 ms 171 ms 185 ms prs-bb1-link.telia.net [80.91.247.254]
13 179 ms 179 ms 179 ms ffm-bb1-link.telia.net [80.91.245.102]
14 180 ms 179 ms 180 ms ffm-b8-link.telia.net [80.91.254.73]
15 179 ms 179 ms 179 ms fusionstorm-ic-139913-ffm-b8.c.telia.net [213.24
8.66.70]
16 180 ms 180 ms 180 ms publicweb.darkfallonline.com [77.95.25.53]

Trace complete.

As you can see, my latency across the board is excellent with at most 1ms jitter. Definitely no bandwidth hogging apps running that are congesting my line. My exchange (thank god) isn't falling apart. Yet WoW still gets 20k+ms and suffers from serious packet loss (as of +-4 days ago). Also worth mentioning is that once again, ITS JUST WoW with this problem. League of Legends, Heroes of Newerth, Starcraft II, Bad Company 2 etc. all run smoothly with excellent in game latencies (180ms to international, 30ms-50ms local). In case you missed it in my previous posts, using a tunneling service such as BattlePing resolves the problem resulting in a stable 180ms in game, indicative of shaping or poor routing.

All the information in hand, it should be clear there isn't anything I can do to resolve the issue on my end. Its kind of frustrating since there was this "window" where WoW was running very well, enough to get me from 1-83 and I was hoping I could stop paying for tunneling services. Now at random, its broken again.

Thanks for your time Will, I very much hope you will take another look into this.
Click to expand...
Sounds like Blizzard changed something in the protocol again, which make sense since they release hotfixes the whole time, and now the QoS equipment again can't classify the traffic correctly causing it to fall into a lower priority category.
 
Hey Will, everything was fine last night after correspondence with Operations after Telkom asked to check with the client. (i.e me)
I replied last night only to find that today my pings and things are all messed again after I confirmed it to all be working.. argh. what now?... please take a look at these stats and let me know what u think?

trace:



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 217 ms 178 ms 203 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 369 ms 406 ms 360 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
5 200 ms 192 ms 188 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 467 ms 343 ms 285 ms tengig-0-0-0-0-12.vic-up-2.mweb.co.za [196.22.169.242]
7 289 ms 314 ms 338 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
8 664 ms 600 ms 396 ms ap2610-1-s12-denimtowers.mweb.net [196.22.163.234]
9 523 ms 620 ms 575 ms 149.6.98.5
10 1004 ms 630 ms 592 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 648 ms 743 ms 781 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
12 2165 ms 839 ms 632 ms ldn-b4-link.telia.net [213.248.70.237]
13 742 ms 728 ms 507 ms ldn-bb2-link.telia.net [80.91.252.209]
14 523 ms 608 ms 716 ms ldn-b3-link.telia.net [80.91.254.17]
15 539 ms 621 ms 604 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 723 ms 672 ms 758 ms 212.58.238.133
17 457 ms 606 ms 545 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.


and the ping:



Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=652ms TTL=110
Reply from 212.58.224.138: bytes=32 time=554ms TTL=110
Reply from 212.58.224.138: bytes=32 time=423ms TTL=110
Reply from 212.58.224.138: bytes=32 time=515ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=419ms TTL=110
Reply from 212.58.224.138: bytes=32 time=492ms TTL=110
Reply from 212.58.224.138: bytes=32 time=474ms TTL=110
Reply from 212.58.224.138: bytes=32 time=465ms TTL=110
Reply from 212.58.224.138: bytes=32 time=526ms TTL=110
Reply from 212.58.224.138: bytes=32 time=467ms TTL=110
Reply from 212.58.224.138: bytes=32 time=522ms TTL=110
Reply from 212.58.224.138: bytes=32 time=627ms TTL=110
Reply from 212.58.224.138: bytes=32 time=639ms TTL=110
Reply from 212.58.224.138: bytes=32 time=469ms TTL=110
Reply from 212.58.224.138: bytes=32 time=422ms TTL=110
Reply from 212.58.224.138: bytes=32 time=425ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=438ms TTL=110
Reply from 212.58.224.138: bytes=32 time=392ms TTL=110

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


Edit: I'm on a 512k uncapped, unshaped account, and i'd like to know if these pings are in line with this type of account. I'm only asking cos Blackhand has posted pings of sub 100ms?.... I dream of these pings....

Here are mine:



Pinging axxess.co.za [196.34.95.131] with 32 bytes of data:
Request timed out.
Reply from 196.34.95.131: bytes=32 time=309ms TTL=52
Reply from 196.34.95.131: bytes=32 time=341ms TTL=52
Reply from 196.34.95.131: bytes=32 time=164ms TTL=52
Request timed out.
Reply from 196.34.95.131: bytes=32 time=246ms TTL=52
Reply from 196.34.95.131: bytes=32 time=289ms TTL=52
Reply from 196.34.95.131: bytes=32 time=493ms TTL=52
Reply from 196.34.95.131: bytes=32 time=227ms TTL=52
Reply from 196.34.95.131: bytes=32 time=191ms TTL=52
Reply from 196.34.95.131: bytes=32 time=208ms TTL=52
Reply from 196.34.95.131: bytes=32 time=318ms TTL=52
Reply from 196.34.95.131: bytes=32 time=178ms TTL=52
Reply from 196.34.95.131: bytes=32 time=174ms TTL=52
Reply from 196.34.95.131: bytes=32 time=293ms TTL=52
Reply from 196.34.95.131: bytes=32 time=304ms TTL=52
Reply from 196.34.95.131: bytes=32 time=142ms TTL=52
Reply from 196.34.95.131: bytes=32 time=327ms TTL=52
Reply from 196.34.95.131: bytes=32 time=179ms TTL=52
Reply from 196.34.95.131: bytes=32 time=22ms TTL=52

Ping statistics for 196.34.95.131:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 493ms, Average = 244ms





Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=302ms TTL=117
Reply from 196.2.63.110: bytes=32 time=335ms TTL=117
Reply from 196.2.63.110: bytes=32 time=355ms TTL=117
Reply from 196.2.63.110: bytes=32 time=594ms TTL=117
Reply from 196.2.63.110: bytes=32 time=582ms TTL=117
Reply from 196.2.63.110: bytes=32 time=286ms TTL=117
Reply from 196.2.63.110: bytes=32 time=251ms TTL=117
Reply from 196.2.63.110: bytes=32 time=303ms TTL=117
Reply from 196.2.63.110: bytes=32 time=399ms TTL=117
Reply from 196.2.63.110: bytes=32 time=672ms TTL=117
Reply from 196.2.63.110: bytes=32 time=343ms TTL=117
Reply from 196.2.63.110: bytes=32 time=425ms TTL=117
Reply from 196.2.63.110: bytes=32 time=406ms TTL=117
Reply from 196.2.63.110: bytes=32 time=207ms TTL=117
Reply from 196.2.63.110: bytes=32 time=327ms TTL=117
Reply from 196.2.63.110: bytes=32 time=364ms TTL=117
Reply from 196.2.63.110: bytes=32 time=674ms TTL=117
Request timed out.
Reply from 196.2.63.110: bytes=32 time=354ms TTL=117
Reply from 196.2.63.110: bytes=32 time=341ms TTL=117

Ping statistics for 196.2.63.110:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 207ms, Maximum = 674ms, Average = 395ms






Pinging eu.darkfallonline.com [77.95.25.53] with 32 bytes of data:
Reply from 77.95.25.53: bytes=32 time=597ms TTL=43
Reply from 77.95.25.53: bytes=32 time=553ms TTL=43
Reply from 77.95.25.53: bytes=32 time=781ms TTL=43
Reply from 77.95.25.53: bytes=32 time=729ms TTL=43
Reply from 77.95.25.53: bytes=32 time=531ms TTL=43
Reply from 77.95.25.53: bytes=32 time=737ms TTL=43
Reply from 77.95.25.53: bytes=32 time=909ms TTL=43
Reply from 77.95.25.53: bytes=32 time=958ms TTL=43
Reply from 77.95.25.53: bytes=32 time=535ms TTL=43
Reply from 77.95.25.53: bytes=32 time=774ms TTL=43
Reply from 77.95.25.53: bytes=32 time=504ms TTL=43
Reply from 77.95.25.53: bytes=32 time=391ms TTL=43
Reply from 77.95.25.53: bytes=32 time=783ms TTL=43
Reply from 77.95.25.53: bytes=32 time=652ms TTL=43
Reply from 77.95.25.53: bytes=32 time=435ms TTL=43
Reply from 77.95.25.53: bytes=32 time=786ms TTL=43
Reply from 77.95.25.53: bytes=32 time=864ms TTL=43
Reply from 77.95.25.53: bytes=32 time=675ms TTL=43
Reply from 77.95.25.53: bytes=32 time=655ms TTL=43
Reply from 77.95.25.53: bytes=32 time=519ms TTL=43

Ping statistics for 77.95.25.53:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 391ms, Maximum = 958ms, Average = 668ms






Tracing route to eu.darkfallonline.com [77.95.25.53]
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 343 ms 275 ms 215 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 208 ms 247 ms 251 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
5 353 ms 332 ms 337 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 255 ms 240 ms 227 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
7 * 236 ms 206 ms 196.22.169.94
8 485 ms 519 ms 459 ms ap2610-1-s12-denimtowers.mweb.net [196.22.163.234]
9 601 ms 602 ms 587 ms 149.6.98.5
10 575 ms 542 ms 410 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 688 ms 546 ms 404 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
12 491 ms 645 ms 552 ms ldn-b4-link.telia.net [213.248.70.237]
13 338 ms 329 ms 365 ms ldn-bb1-link.telia.net [80.91.252.205]
14 699 ms 413 ms 338 ms prs-bb1-link.telia.net [80.91.247.6]
15 620 ms 502 ms 487 ms ffm-bb1-link.telia.net [80.91.245.104]
16 584 ms 805 ms 452 ms ffm-b8-link.telia.net [80.91.254.73]
17 542 ms 501 ms 588 ms fusionstorm-ic-139913-ffm-b8.c.telia.net [213.248.66.70]
18 483 ms 509 ms 600 ms publicweb.darkfallonline.com [77.95.25.53]

Trace complete.


There's nothing else using my network, no other pc's there is no line damage, no phones or faxes connected, I double checked all my data with netlimiter and nothing else was consuming any bandwidth... I really need this fixed. Will, help me out here.... MTU's don't help either. :( 4.5k latency in both retail and private WoW servers...
 
Last edited:
I've been getting terrible delays in instances for some reason, and it's definitely not server-related. I'm not sure if it's related, as my latency is still normal.
 
That's almost definitely something happening at the exchange level ultraviolet , look at this for comparison:

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=10ms TTL=121
Reply from 196.2.63.110: bytes=32 time=9ms TTL=121
Reply from 196.2.63.110: bytes=32 time=10ms TTL=121
Reply from 196.2.63.110: bytes=32 time=8ms TTL=121

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 10ms, Average = 9ms

Pinging eu.darkfallonline.com [77.95.25.53] with 32 bytes of data:
Reply from 77.95.25.53: bytes=32 time=177ms TTL=45
Reply from 77.95.25.53: bytes=32 time=177ms TTL=45
Reply from 77.95.25.53: bytes=32 time=177ms TTL=45
Reply from 77.95.25.53: bytes=32 time=178ms TTL=45

Ping statistics for 77.95.25.53:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 178ms, Average = 177ms

Tracing route to eu.darkfallonline.com [77.95.25.53]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.254]
2 7 ms 9 ms 6 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 12 ms 11 ms 9 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]

4 8 ms 9 ms 9 ms 196-28-179-11.adsl.mweb.co.za [196.28.179.11]
5 16 ms 12 ms 10 ms 196-28-178-97.adsl.mweb.co.za [196.28.178.97]
6 160 ms 160 ms 203 ms 196.22.164.2
7 161 ms 162 ms 160 ms 149.6.98.17
8 159 ms 163 ms 161 ms te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.169]
9 160 ms 160 ms 164 ms te7-2.mpd02.lon01.atlas.cogentco.com [130.117.0.97]
10 160 ms 160 ms 160 ms ldn-b4-link.telia.net [213.248.70.237]
11 160 ms 159 ms 160 ms ldn-bb1-link.telia.net [80.91.249.179]
12 168 ms 168 ms 187 ms prs-bb1-link.telia.net [80.91.254.209]
13 176 ms 176 ms 176 ms ffm-bb1-link.telia.net [80.91.245.100]
14 177 ms 177 ms 177 ms ffm-b8-link.telia.net [80.91.254.73]
15 177 ms 176 ms 182 ms fusionstorm-ic-139913-ffm-b8.c.telia.net [213.248.66.70]
16 179 ms 177 ms 177 ms publicweb.darkfallonline.com [77.95.25.53]

Trace complete.

You can see on the trace how your latency ramps up from hop 2 onwards, whereas mine remains below 20ms until it reaches international routing. I'll follow up with the team tomorrow and see what else we can do to get some answers out of Telkom for you as to what's causing this.
 
Will@MWEB said:
You can see on the trace how your latency ramps up from hop 2 onwards, whereas mine remains below 20ms until it reaches international routing. I'll follow up with the team tomorrow and see what else we can do to get some answers out of Telkom for you as to what's causing this.
Click to expand...

Will, I would really appreciate this. Hopefully we can get this sorted out before the end of the month.

Edit: Will, I would like to thank you for your speedy response and care in sorting out this issue. You're a great asset to MWEB.

Kindest Regards
 
Last edited:
Thanks ultraviolet :) I'm back in the office tomorrow after a nice rest, will see if I can get some fires lit under this one for you.
 
Ok, now its just getting worse... :(
Download speeds dropped to like 5Kbps...

Just for interest sake:


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 * 860 ms 959 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 506 ms 515 ms 668 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
5 393 ms 309 ms 439 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 539 ms 657 ms 511 ms tengig-0-0-0-0-11.vic-up-2.mweb.co.za [196.22.169.226]
7 367 ms 435 ms 674 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
8 598 ms 402 ms 465 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
9 698 ms * 523 ms 149.6.98.5
10 975 ms 1624 ms 593 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 713 ms 851 ms 922 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
12 846 ms * 762 ms ldn-b4-link.telia.net [213.248.70.237]
13 561 ms 506 ms 660 ms ldn-bb1-link.telia.net [80.91.252.205]
14 617 ms 753 ms 765 ms ldn-b3-link.telia.net [80.91.249.170]
15 463 ms 761 ms 694 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 615 ms 833 ms 652 ms 212.58.238.149
17 782 ms 807 ms 916 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=554ms TTL=110
Reply from 212.58.224.138: bytes=32 time=754ms TTL=110
Reply from 212.58.224.138: bytes=32 time=802ms TTL=110
Reply from 212.58.224.138: bytes=32 time=553ms TTL=110
Reply from 212.58.224.138: bytes=32 time=789ms TTL=110
Reply from 212.58.224.138: bytes=32 time=746ms TTL=110
Reply from 212.58.224.138: bytes=32 time=547ms TTL=110
Reply from 212.58.224.138: bytes=32 time=713ms TTL=110
Reply from 212.58.224.138: bytes=32 time=626ms TTL=110
Reply from 212.58.224.138: bytes=32 time=528ms TTL=110
Reply from 212.58.224.138: bytes=32 time=567ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=621ms TTL=110
Reply from 212.58.224.138: bytes=32 time=742ms TTL=110
Reply from 212.58.224.138: bytes=32 time=647ms TTL=110
Reply from 212.58.224.138: bytes=32 time=812ms TTL=110
Reply from 212.58.224.138: bytes=32 time=814ms TTL=110
Reply from 212.58.224.138: bytes=32 time=831ms TTL=110
Reply from 212.58.224.138: bytes=32 time=621ms TTL=110
Reply from 212.58.224.138: bytes=32 time=534ms 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 = 528ms, Maximum = 831ms, Average = 673ms
 
And it continues...



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 209 ms 288 ms 210 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 227 ms 331 ms 213 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
5 555 ms 546 ms 336 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 91 ms 72 ms 82 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 196 ms 428 ms 162 ms tengig-0-0-0-0-41.vic-up-2.mweb.co.za [196.22.169.210]
8 672 ms 450 ms 445 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
9 465 ms 512 ms 452 ms 149.6.98.17
10 539 ms 536 ms 832 ms te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.169]
11 491 ms 622 ms 444 ms te7-2.mpd02.lon01.atlas.cogentco.com [130.117.0.97]
12 604 ms 564 ms 1437 ms ldn-b4-link.telia.net [213.248.70.237]
13 484 ms 522 ms 567 ms ldn-bb1-link.telia.net [80.91.248.217]
14 983 ms 1128 ms 1018 ms ldn-b3-link.telia.net [80.91.249.170]
15 816 ms * 646 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 451 ms 559 ms 499 ms 212.58.238.133
17 484 ms 525 ms 873 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=877ms TTL=110
Reply from 212.58.224.138: bytes=32 time=594ms TTL=110
Reply from 212.58.224.138: bytes=32 time=1155ms TTL=110
Reply from 212.58.224.138: bytes=32 time=615ms TTL=110
Reply from 212.58.224.138: bytes=32 time=527ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=456ms TTL=110
Reply from 212.58.224.138: bytes=32 time=565ms TTL=110
Reply from 212.58.224.138: bytes=32 time=394ms TTL=110
Reply from 212.58.224.138: bytes=32 time=487ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=320ms TTL=110
Reply from 212.58.224.138: bytes=32 time=358ms TTL=110
Reply from 212.58.224.138: bytes=32 time=430ms TTL=110
Reply from 212.58.224.138: bytes=32 time=566ms TTL=110
Reply from 212.58.224.138: bytes=32 time=528ms TTL=110
Reply from 212.58.224.138: bytes=32 time=524ms TTL=110
Reply from 212.58.224.138: bytes=32 time=383ms TTL=110
Reply from 212.58.224.138: bytes=32 time=481ms TTL=110
Reply from 212.58.224.138: bytes=32 time=934ms TTL=110

Ping statistics for 212.58.224.138:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 320ms, Maximum = 1155ms, Average = 566ms
 
Here's the ping to the exchange.... looks um, pa-the-tic



Pinging 41.133.74.1 with 32 bytes of data:
Reply from 41.133.74.1: bytes=32 time=159ms TTL=253
Reply from 41.133.74.1: bytes=32 time=294ms TTL=253
Request timed out.
Reply from 41.133.74.1: bytes=32 time=243ms TTL=253
Reply from 41.133.74.1: bytes=32 time=225ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Reply from 41.133.74.1: bytes=32 time=595ms TTL=253
Reply from 41.133.74.1: bytes=32 time=112ms TTL=253
Reply from 41.133.74.1: bytes=32 time=220ms TTL=253
Reply from 41.133.74.1: bytes=32 time=69ms TTL=253
Reply from 41.133.74.1: bytes=32 time=710ms TTL=253
Reply from 41.133.74.1: bytes=32 time=387ms TTL=253
Reply from 41.133.74.1: bytes=32 time=436ms TTL=253
Reply from 41.133.74.1: bytes=32 time=380ms TTL=253
Reply from 41.133.74.1: bytes=32 time=388ms TTL=253
Reply from 41.133.74.1: bytes=32 time=413ms TTL=253
Reply from 41.133.74.1: bytes=32 time=603ms TTL=253
Reply from 41.133.74.1: bytes=32 time=157ms TTL=253

Ping statistics for 41.133.74.1:
Packets: Sent = 20, Received = 16, Lost = 4 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 710ms, Average = 336ms


Will, just for interest sake, I'm gonna do a tracert to bbc and ping to the exchange at like 2am or 3am, when usage is completely offpeak and see if what the latency looks like to the exchange. Also my router reports for:
Line Attenuation 25.5db downstream 14.0db upstream
Noise Margin 34.5db downstream 16db upstream
 
Last edited:
@Ultraviolet150: Your noise margin and line attenuation are excellent, well above the usual SA standards, your latency however is extremely poor. This normally indicates some kind of congestion. It could either be on your end or a problem at your exchange (oversubscribed).

To rule it out, I suggest you install a bandwidth monitor such as NetLimiter on all your home PCs and disconnect any devices from your network that could be using bandwidth such as game consoles, smarthphones etc. Once you have ruled out your own network as a culprit of congestion, all you can do is pray that Telkom sorts out the exchange in a timely manner.
 
Blackhand said:
@Ultraviolet150: Your noise margin and line attenuation are excellent, well above the usual SA standards, your latency however is extremely poor. This normally indicates some kind of congestion. It could either be on your end or a problem at your exchange (oversubscribed).

To rule it out, I suggest you install a bandwidth monitor such as NetLimiter on all your home PCs and disconnect any devices from your network that could be using bandwidth such as game consoles, smarthphones etc. Once you have ruled out your own network as a culprit of congestion, all you can do is pray that Telkom sorts out the exchange in a timely manner.
Click to expand...


I have had net limiter installed since i discovered internet and i can assure you there are no other devices connected. I have ruled it out to be at the exchange and just now, i discovered this and it kinda reinforces what we all suspect. Check hop 3. thats from my modem to the exchange, hop6 and 7 though confuse me slightly as these are local connections and shouldnt be that high if you consider hop4 and 5 are sub 100ms?... what do u think?



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 181 ms 175 ms 200 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 100 ms 65 ms 51 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
5 42 ms 42 ms 61 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 96 ms 104 ms 167 ms tengig-0-0-0-0-12.vic-up-2.mweb.co.za [196.22.169.242]
7 * 238 ms 218 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
8 429 ms 437 ms 427 ms ap2610-1-s12-denimtowers.mweb.net [196.22.163.234]
9 639 ms 494 ms 495 ms 149.6.98.5
10 502 ms 398 ms 264 ms te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.169]
11 449 ms 549 ms 618 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48.153]
12 477 ms 528 ms 442 ms ldn-b4-link.telia.net [213.248.70.237]
13 375 ms 382 ms 431 ms ldn-bb1-link.telia.net [80.91.248.217]
14 494 ms 412 ms 474 ms ldn-b3-link.telia.net [80.91.247.86]
15 403 ms 540 ms 425 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 529 ms 421 ms 297 ms 212.58.238.149
17 441 ms 427 ms 376 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
 
Haven't been on all weekend but I have noticed it is pretty crap tonight with an ingame latency in SW of over 5k.

Here is the tracert, from what little I know it appears that the latency is occurring from a South African IP.

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

1 * * * Request timed out.
2 21 ms 19 ms 19 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 25 ms 21 ms 25 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]

4 33 ms 23 ms 21 ms 196-28-179-11.adsl.mweb.co.za [196.28.179.11]
5 25 ms 21 ms 23 ms 196-28-178-97.adsl.mweb.co.za [196.28.178.97]
6 173 ms 174 ms 176 ms 196.22.164.2
7 173 ms 174 ms 175 ms 149.6.98.5
8 174 ms 174 ms 175 ms te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.
169]
9 172 ms 174 ms 174 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48
.153]
10 243 ms 175 ms 174 ms ldn-b4-link.telia.net [213.248.70.237]
11 172 ms 276 ms 274 ms ldn-bb2-link.telia.net [80.91.247.93]
12 181 ms 180 ms 182 ms prs-bb2-link.telia.net [80.91.247.240]
13 262 ms 189 ms 190 ms ffm-bb2-link.telia.net [80.91.246.180]
14 188 ms 188 ms 212 ms ffm-b10-link.telia.net [80.91.251.250]
15 * * * Request timed out.

/sigh, time to switch out account >.<
 
More people pouring in with issues. Still looking like an isolated case ?
 
Hi Steven please confirm, was your connection ok last week? I have been in and out of game over the course of the day and no sign of trouble - I saw a brief spike now while banking in Ironforge but after reconnecting it seems to have settled back to normal (mid 200s). I will play for a bit now and see if I can see any sign of further problems. I'll have a long chat with the network guys tomorrow and see if they're aware of any issues that might have occured over the last week. Sillicur, please PM me your preferred contact details - I will call you tomorrow to discuss your problems.
 
With a proxy service my WoW seems fine, but I really prefer not having to pay for a tunneling service like Battleping for 2 reasons. No.1 being that its extra money, No.2 and this is the big one is:

Greetings Wessel,

We are writing to inform you that, after a careful investigation of your account closure, we have agreed to remove the permanent suspension of your account from the World of Warcraft servers.

This change has already been put into effect, and your account should again be available for play.

Following an investigation into actions taken against this account we believe this account may have been accessed via a Proxy Service.

We appreciate there are circumstances when use of a Proxy can be beneficial however such services are routinely used to attempt to hide the actions of Online Trading companies and users attempting to use exploitative third party programs. As such, we do not support the use of Proxy services and if you continue to use these, we regret that this may result in further suspensions placed on your account.

If you wish to review our current Rules and Policies, they can be found at:

http://eu.blizzard.com/support/index/wow_policy

http://eu.blizzard.com/en-gb/company/about/termsofuse.html

Thats the email i got today after spending a hour on the phone with blizzard and getting my account unbanned. Im using battleping btw.
So now allot of people can understand, not only do I have to pay extra for a tunneling service so I can play WoW, but I also run the risk of being permanently banned cause of it, although the risk is slim. Thats why im raging more than usual today, the service I was almost forced to get so I can play wow with a reasonable latency almost cost me countless hours of play and my wow account :(
 
Last edited:
Will@MWEB said:
Hi Steven please confirm, was your connection ok last week? I have been in and out of game over the course of the day and no sign of trouble - I saw a brief spike now while banking in Ironforge but after reconnecting it seems to have settled back to normal (mid 200s). I will play for a bit now and see if I can see any sign of further problems. I'll have a long chat with the network guys tomorrow and see if they're aware of any issues that might have occured over the last week. Sillicur, please PM me your preferred contact details - I will call you tomorrow to discuss your problems.
Click to expand...

Will, It's me again. Just a quick one, Its currently offpeak and everything is great(ish). Only problem I'm still having is the latency to the exchange/DSLAM. All is okish except for the 3rd hop being the exchange.




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

1 <1 ms 3 ms 3 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 10 ms 1 ms 2 ms 192.168.0.1
3 124 ms 191 ms 144 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 66 ms 18 ms 16 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
5 28 ms 18 ms 25 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 25 ms 19 ms 30 ms tengig-0-0-0-0-12.vic-up-2.mweb.co.za [196.22.169.242]
7 21 ms 21 ms 22 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
8 240 ms 238 ms 254 ms ap2610-1-s12-denimtowers.mweb.net [196.22.163.234]
9 238 ms 241 ms 253 ms 149.6.98.5
10 380 ms 421 ms 388 ms te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.169]
11 576 ms 374 ms 313 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48.153]
12 256 ms 253 ms 240 ms ldn-b4-link.telia.net [213.248.70.237]
13 257 ms 1134 ms 295 ms ldn-bb1-link.telia.net [80.91.248.217]
14 249 ms 260 ms 240 ms ldn-b3-link.telia.net [80.91.247.86]
15 254 ms 257 ms 241 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 310 ms 257 ms 247 ms 212.58.238.149
17 239 ms 251 ms 246 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
 
Last edited:
Sillicur said:
.....Thats why im raging more than usual today, the service I was almost forced to get so I can play wow with a reasonable latency almost cost me countless hours of play and my wow account :(
Click to expand...

Its really crap to hear about that Sillicur, just for interest sake, where are you located and do you mind posting a ping and tracert to bbc.co.uk (due to my laziness to search for it) also what is your line speed and are you shaped or unshaped?
 
Line speed, 384, Mweb uncapped 384 deal (shaped i guess, thou it was stated these accounts dont have their gaming traffic shaped). Im located close to PE, in a small town called Despatch, not allot of adsl users so cant see my exchange being over used. Ping is around 210 - 220 to bbc.co.uk. Cant really post a tracert now, busy downloading a file without resume support :(

Any other ISP i could think of shows no issues in wow except for my mweb account. (telkom, axxess, matrix, webafrica and afrihost.) With the proxy service and mweb i just get the dc while loading issue, but when its in game its fine. Problem is, proxy services can lose you your account.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X