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.