MWEB Gaming Feedback

Thanks for that Sash. I'm not sure if you saw my post earlier today but there will be an adjustment to bandwidth allocations early tomorrow morning, which we hope will improve the experience from tomorrow night. I'd be interested to see what that message said. I'll go and take another look at the Blizzard forums, but if anyone has a link to it that would be great.
 
I just took a screenie of the messages, apparently blizzard have restarted some of the realms this evening to see if it helps they / users are experiencing.

Please PM me if you need the screenshot.

Anyway... point was there is definately something happening today / evening, so its not a good time to benchmark performance - could be totally unrelated.
 
Hello :)

I just want to give some feedback over here. I play Call of Duty on Xbox LIVE. In the past I used to get 2 yellow bars worth of latency. That wasn't too bad actually. Sometimes I get red bar as well, and that is almost similar to the feeling of 2 yellow bars.

Recently though, I only ever get 1 red bar and isn't like the old red bar I used to get. This is some serious lag. Based on my previous experience I could roughly estimate the latency at 1000ms currently. It is a full second worth of lag. I just wanted to bring this to your attention. Thanks for keeping us up to date.

If you need someone to report back to you on Xbox LIVE on a regular basis and give detailed feedback, please let me know. I am more than willing to help you solve the issue.
 
@TheGrimReaper

Thanks :) Is the DotA experience also affected in the evenings?

I have experienced the occasional lag and drop but for the past couple of days that hasn't happened oh and my roommate plays Starcraft 2 and he is satisfied except for the lag and drop. For the past couple of days i haven't experienced that much lag in DotA.
 
Hello :)

I just want to give some feedback over here. I play Call of Duty on Xbox LIVE. In the past I used to get 2 yellow bars worth of latency. That wasn't too bad actually. Sometimes I get red bar as well, and that is almost similar to the feeling of 2 yellow bars.

Recently though, I only ever get 1 red bar and isn't like the old red bar I used to get. This is some serious lag. Based on my previous experience I could roughly estimate the latency at 1000ms currently. It is a full second worth of lag. I just wanted to bring this to your attention. Thanks for keeping us up to date.

If you need someone to report back to you on Xbox LIVE on a regular basis and give detailed feedback, please let me know. I am more than willing to help you solve the issue.


Hi Tegnik, is this constant, or only at certain times of the day?
 
Code:
C:\>TRACERT CINX.SAIX.NET

TRACING ROUTE TO CINX.SAIX.NET [67.215.65.132]
OVER A MAXIMUM OF 30 HOPS:

  1     3 MS    <1 MS    <1 MS  UNKNOWN [192.168.1.1]
  2     *        *        *     REQUEST TIMED OUT.
  3    37 MS    36 MS    36 MS  TENGIG-0-0-0-107.VIC-IPC-1.MWEB.CO.ZA [196.22.16
9.158]
  4    36 MS    36 MS    36 MS  VL-92.VIC-HSCORE-2.MWEB.CO.ZA [196.22.189.3]
  5    42 MS    40 MS    42 MS  TENGIG-0-0-0-0-12.VIC-UP-1.MWEB.CO.ZA [196.22.16
9.241]
  6    40 MS    40 MS    41 MS  TENGIG-0-2-0-0.MID-1.MWEB.CO.ZA [196.22.169.219]

  7   259 MS   259 MS   258 MS  PO9-0.LON-001-ACCESS-1.INTEROUTE.NET [89.202.130
.181]
  8   259 MS   279 MS   259 MS  XE-1-3-0-0.LON-001-SCORE-1-RE0.INTEROUTE.NET [84
.233.218.178]
  9   261 MS   261 MS   268 MS  212.113.16.109
 10   259 MS   259 MS   259 MS  AE-34-52.EBR2.LONDON1.LEVEL3.NET [4.69.139.97]
 11   268 MS   268 MS   268 MS  AE-46-46.EBR2.AMSTERDAM1.LEVEL3.NET [4.69.143.73
]
 12   268 MS   273 MS   267 MS  AE-2-52.EDGE4.AMSTERDAM1.LEVEL3.NET [4.69.139.17
0]
 13   269 MS   269 MS   268 MS  SPLICE-COMM.EDGE4.AMSTERDAM1.LEVEL3.NET [212.72.
40.98]
 14   268 MS   255 MS   255 MS  HIT-NXDOMAIN.OPENDNS.COM [67.215.65.132]

TRACE COMPLETE.

C:\>TRACERT RIGAMING.ZA.NET

TRACING ROUTE TO RIGAMING.ZA.NET [196.220.57.101]
OVER A MAXIMUM OF 30 HOPS:

  1    <1 MS    <1 MS    <1 MS  UNKNOWN [192.168.1.1]
  2     *        *        *     REQUEST TIMED OUT.
  3    36 MS    35 MS    36 MS  TENGIG-0-0-0-110.VIC-IPC-1.MWEB.CO.ZA [196.22.16
9.170]
  4    36 MS    36 MS    37 MS  VL-92.VIC-HSCORE-1.MWEB.CO.ZA [196.22.189.2]
  5    69 MS    75 MS    72 MS  TENGIG-0-0-0-0-11.VIC-UP-1.MWEB.CO.ZA [196.22.16
9.225]
  6    37 MS    36 MS    37 MS  RRBA-IP-HSLL-1-WAN.TELKOM-IPNET.CO.ZA [196.25.8.
249]
  7    61 MS    61 MS    61 MS  196.43.39.78
  8    62 MS    62 MS    61 MS  VL101.ER.GW.CPT.ZA.WA.CO.ZA [196.220.59.225]
  9    62 MS    61 MS    61 MS  VL34.CR.GW.CPT.ZA.WA.CO.ZA [41.185.0.33]
 10    63 MS    63 MS    62 MS  FE0.ER1.GW.CPT.ZA.WADNS.NET [41.185.0.4]
 11    62 MS    62 MS    62 MS  WA-ACC1.WADNS.NET [196.220.39.253]
 12    63 MS    51 MS    49 MS  PLESK8.WADNS.NET [196.220.57.101]

TRACE COMPLETE.
C:\>TRACERT JINX.SAIX.NET

TRACING ROUTE TO JINX.SAIX.NET [67.215.65.132]
OVER A MAXIMUM OF 30 HOPS:

  1    <1 MS    <1 MS    <1 MS  UNKNOWN [192.168.1.1]
  2     *        *        *     REQUEST TIMED OUT.
  3    37 MS    35 MS    36 MS  TENGIG-0-0-0-107.VIC-IPC-1.MWEB.CO.ZA [196.22.16
9.158]
  4    37 MS    36 MS    37 MS  VL-92.VIC-HSCORE-2.MWEB.CO.ZA [196.22.189.3]
  5    39 MS    38 MS    42 MS  TENGIG-0-0-0-0-12.VIC-UP-1.MWEB.CO.ZA [196.22.16
9.241]
  6    62 MS    67 MS    67 MS  TENGIG-0-2-0-0.MID-1.MWEB.CO.ZA [196.22.169.219]

  7   259 MS   259 MS   259 MS  PO9-0.LON-001-ACCESS-1.INTEROUTE.NET [89.202.130
.181]
  8   259 MS   260 MS   259 MS  XE-1-3-0-0.LON-001-SCORE-1-RE0.INTEROUTE.NET [84
.233.218.178]
  9   385 MS   261 MS   261 MS  212.113.16.109
 10   270 MS   259 MS   266 MS  AE-34-52.EBR2.LONDON1.LEVEL3.NET [4.69.139.97]
 11   268 MS   268 MS   268 MS  AE-46-46.EBR2.AMSTERDAM1.LEVEL3.NET [4.69.143.73
]
 12   268 MS   267 MS   268 MS  AE-2-52.EDGE4.AMSTERDAM1.LEVEL3.NET [4.69.139.17
0]
 13   268 MS   281 MS   268 MS  SPLICE-COMM.EDGE4.AMSTERDAM1.LEVEL3.NET [212.72.
40.98]
 14   269 MS   255 MS   255 MS  HIT-NXDOMAIN.OPENDNS.COM [67.215.65.132]

TRACE COMPLETE.
 
@Anthropoid

The addresses CINX.SAIX.NET & JINX.SAIX.NET do not really exist. As you are using OpenDNS, they are resolving them to a 'unavaliable' place holder address (their own search page website overseas).
 
Hi, I started the issue of high latency with wow on the 15th that went up to like 8000k+ in the evenings. Tried again last night as I do every night and the issue still persists. During the day latency on Mweb is fine during the evening its not. Telkom is always fine. But worse with my webafrica account I can not even log on. The web africa issue has been ongoing for months and I actually cancelled that account. I am playing on the US servers though and not the EU servers as most ppl here do. If you need some1 for testing during the week day or night, I am available. Give me your email address Will (if you need a tester) and I can send you contact info as I don't read this thread on a daily basis.

Ps. I know that WoW has some issues after the patch, but none of that is latency related issues. Its mostly DC issues esp in the Headless Horseman event currently running. I have checked with other players (from us and europe) whom have very little latency and as I said, no issues with latency on my telkom account so its not the wow network issue thats to blame here.
 
Last edited:
Lounger I'm really sorry. I have done my best to explain these concepts to you, however I'm afraid that these matters are extremely complex and require a fair degree of technical insight to grasp. Please trust me when I say that we will endeavour to give gaming traffic the best treatment possible and don't concern yourself with the technicalities as they are clearly causing you a great deal of stress, which was not my intention when attempting to explain this.

Will, as a final word on this because getting nowhere isn't amusing.

You've got it completely wrong. The fact that you are NOT giving us the technicalities is, I believe, the cause of misunderstandings and frustration. You're treating us like dummies, even though many of the posts on here are quite technical. We are also quite capable of using Google to find out anything unfamiliar.

Certainly my experience of Mweb technicians is that they are very limited in the areas assigned to them, and struggle to explain problems in a consistent and plausible way.

I reiterate my advice to you and your colleagues to be more forthcoming and transparent and to stop trying to dress things up to look better. If you're shaping, say so. Don't call it a small pool of limited bandwidth that is middle-prioritised. It's just shaping under a different guise. And if other reps have said gaming is unshaped then do try and stick to one story.
 
Thanks for your feedback Lounger your opinion is noted. I have said this to you several times now however I will state it once more for the record that I have made no attempt to mislead you at any point and have provided an accurate high level explanation of the manner in which traffic is managed. I previously explained that gaming traffic was not being shaped (ie it was in the middle tier which was accurate at the time) It has now been moved to the top tier (prioritized), which I have also made very clear to you. there are other optimizations which can be made to bandwidth allocation over and above this which we are currently working on.
Please understand that this is now my final word on the subject and I am under no obligation to provide you with any more detail on the matter.
 
Im having serious trouble.. Latencey is betweek 3.5k - 25k. frequent disconects.

Currantly Idle faraway from ther players and chat channels, 1k+ ping.

Please what is going on?

ive noticed my telkom acc is no better either.
 
Amvios can you show us a tracert to an international website please, from both your mweb and telkom acc.
 
Hi Will,

My ping in wow last (12 PM)night was about 400-800ms <-- should not be this if im correct and this is with the WTFast proxy service, today I played with a ping of between 230-270ms constantly, this is during Office hours. Now the changes will be made tonight and I will check again tonight what my ping is.

Oddly enough 7 PM last night my friend (using the same mweb acc) got a ping of 240-300ms O_o, dont know how this works......anycase just an update on this :D

thanks for all your help thus far.
 
according to http://www.wowwiki.com/EU_English_realms_info wow EU realms list is as follows:

Vek'nilash 213.248.123.73 how accurate this I dont know bt I know its a very trustworthy site. many of its info on the community site is 99% accurate.

Traceroute

C:\Users\Amvios>tracert 213.248.123.73

Tracing route to 213-248-123-73.customer.teliacarrier.com [213.248.123.73]
over a maximum of 30 hops:

1 20 ms 18 ms 19 ms 41-132-76-1.dsl.mweb.co.za [41.132.76.1]
2 116 ms 117 ms 119 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
3 * 183 ms 119 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 148 ms 134 ms 167 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
5 122 ms 119 ms 125 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

6 341 ms 339 ms 339 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
7 384 ms 378 ms 346 ms 149.6.98.5
8 340 ms 366 ms 339 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
9 * * 339 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.
74]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

the rest just timed out..

How ever ive noticed game ping is now 900+

C:\Users\Amvios>tracert 213.248.123.73

Tracing route to 213-248-123-73.customer.teliacarrier.com [213.248.123.73]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms sx762.dummy.porta.siemens.net [10.0.0.2]
2 20 ms 18 ms 19 ms dsl-145-64-01.telkomadsl.co.za [41.145.64.1]
3 19 ms 21 ms 19 ms 196.43.21.194
4 * * * Request timed out.
5 28 ms 24 ms 26 ms 196.43.10.130
6 114 ms 109 ms 114 ms 196.43.33.5
7 291 ms 295 ms 298 ms lon-ip-dir-telecity-gig-1-0-2.telkom-ipnet.co.za
[196.43.9.217]
8 363 ms 357 ms 363 ms ldn-tch-i1-link.telia.net [213.155.141.153]
9 * * * Request timed out.
10 ldn-tch-i1-link.telia.net [213.155.141.153] reports: Destination host unre
achable.

Trace complete.
 
Hi Amvios

You're picking up latency very quickly in the very early stages of your trace on both accounts, which is generally an indication that there is some Telkom congestion going on in your area - if you send me a PM with your telkom line number I can try and check the status of this for you.
 
Hey guys, so the changes are set for 6pm tonight? Should one reconnect or reset router before that time? Btw, its so good during the day now, 270ms, which is awesome. Just praying it will stay the same after 6 !
 
Hey guys, so the changes are set for 6pm tonight? Should one reconnect or reset router before that time? Btw, its so good during the day now, 270ms, which is awesome. Just praying it will stay the same after 6 !

guess you should reset your router just to refresh the connection...my guess anyways :D
 
HI Will@Mweb

Just a quick question have you guys changed anything today that would affect bandwidth and latency? For some reason my WoW latency was fine at around 310-450ms this afternoon but now it is at around 800-1000ms I noticed my connection went down and when it came back up it had a new DNS IP 196.28.75.200 any reason why? Also running a Torrent in the background at a limited speed of 30KB/s seems to destroy my latency and I have to shut that down it feels almost as if I only have 30KB/s to work with. Here is a tracert if it helps any.
Tracing route to host-166.wow-europe.com [80.239.179.166]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms www.routerlogin.com
2 8 ms 7 ms 7 ms 41-132-6-1.dsl.mweb.co.za [41.132.6.1]
3 18 ms 19 ms 19 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 19 ms 19 ms 20 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 22 ms 23 ms 21 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 22 ms 22 ms 22 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]

7 242 ms 246 ms 243 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 256 ms 274 ms 408 ms 149.6.98.5
9 243 ms 242 ms 242 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
10 244 ms 244 ms 244 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.
225]
11 311 ms 306 ms 304 ms ldn-b4-link.telia.net [213.248.70.237]
12 310 ms 301 ms 301 ms ldn-bb2-link.telia.net [80.91.249.133]
13 309 ms 312 ms 310 ms prs-bb2-link.telia.net [80.91.247.240]
14 317 ms 312 ms 310 ms prs-b1-link.telia.net [80.91.250.249]
15 312 ms 309 ms 314 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.

Thanks for any help or info

Regards
Hellhound
 
Top
Sign up to the MyBroadband newsletter
X