MWEB Gaming Feedback

Hi Will

Tonight pings on SGS COD4 server (196.4.79.79) very erratic.

50- 180ms


Tracing route to 196.4.79.79 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 * * * Request timed out.
3 8 ms 9 ms 9 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]
4 77 ms 79 ms 77 ms 196.22.169.41
5 65 ms 64 ms 150 ms 196.22.169.61
6 117 ms 125 ms 99 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 84 ms 82 ms 83 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
8 70 ms 70 ms 73 ms tpr-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.10.86]
9 tpr-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.10.86] reports: Destination net unreachable.


Tracing route to 196.4.79.79 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 * * * Request timed out.
3 9 ms 8 ms 8 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]
4 36 ms 36 ms 36 ms 196.22.169.41
5 88 ms 84 ms 85 ms 196.22.169.61
6 103 ms 114 ms 93 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 66 ms 65 ms 65 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
8 93 ms 95 ms 96 ms tpr-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.10.86]
9 tpr-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.10.86] reports: Destination net unreachable.

Trace complete.

please have a look and see if u can fix

thanks
 
Can confirm WoW EU latency was horrid.
Able to login but actually doing anything was pointless, is this a permanent shaping policy?

SA WoW Server (an actual legit Blizzard one) would be win, but alas, no such luck in this lifetime. As there isn't a single server in the Southern Hemisphere (as I am aware)
 
Please hang in there gents, we are waiting on two major issues which i think will have an all round positive impact:

The finalization of load balancing between the North and South links, which I'm hoping will be completed by Thursday.

The "lighting up" of an additional 1.2gb of Seacom capacity, which should take place during the first week of October.

Cheers
Will
 
tried to update city of heroes the other day, 8m file took 5 hours!
speedtest failed to even load!

970596119.png
 
So is there any way to actually get steam to perform adequately? Logging in should not take 30min - forever
 
on @mweb.co.za or @dslmweb.co.za after deleting clientregistry.blob i get a fantastic 6-8KB/s (steadily dropping down to 0 as it times out) from steam.wa.co.za Can you guys please just allow us to CONNECT to the damn thing?
 
Not sure if this should go here or somewhere else. But can you guys please have a look at the shaping of gog.com. Since the relaunch it has been slow during the day when downloading. No such issues with steam.
 
Please hang in there gents, we are waiting on two major issues which i think will have an all round positive impact:

The finalization of load balancing between the North and South links, which I'm hoping will be completed by Thursday.

The "lighting up" of an additional 1.2gb of Seacom capacity, which should take place during the first week of October.

Cheers
Will

To those who whined after this post...READ AGAIN. :p
 
impossible to host/join and login with ubisoft's servers for rainbow 6 vegas 2.

216.98.48.18
216.98.48.56
216.98.48.57
216.98.48.102

do the racert just now

216.98.48.18
tracert 216.98.48.18

Tracing route to lb-ws.ubisoft.com [216.98.48.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 * * * Request timed out.
3 13 ms 12 ms 18 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 34 ms 13 ms 17 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 47 ms 44 ms 35 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 40 ms 23 ms 19 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

7 258 ms 237 ms 240 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 251 ms 247 ms 237 ms 130.117.136.1
9 243 ms 236 ms 258 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50
.117]
10 311 ms 312 ms 311 ms te0-5-0-1.ccr22.jfk02.atlas.cogentco.com [154.54
.30.134]
11 311 ms 312 ms 311 ms te4-8.ccr02.jfk05.atlas.cogentco.com [154.54.7.1
0]
12 327 ms * * teleglobe.jfk05.atlas.cogentco.com [154.54.12.94
]
13 324 ms 322 ms 315 ms if-13-0-0-475.core2.NTO-NewYork.as6453.net [216.
6.97.89]
14 324 ms 319 ms 319 ms if-5-0.mcore4.MTT-Montreal.as6453.net [216.6.115
.21]
15 321 ms 322 ms 319 ms if-3-0.mcore3.MTT-Montreal.as6453.net [216.6.114
.1]
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.

Trace complete.


216.98.48.56
tracert 216.98.48.56

Tracing route to lb-lsg-prod.ubisoft.com [216.98.48.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 * * * Request timed out.
3 11 ms 12 ms 11 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
4 12 ms 24 ms 16 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 50 ms 48 ms 60 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 40 ms 45 ms 34 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

7 239 ms 239 ms 245 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 236 ms 236 ms 236 ms 130.117.136.1
9 402 ms 412 ms 427 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50
.117]
10 311 ms 312 ms 316 ms te0-5-0-1.ccr22.jfk02.atlas.cogentco.com [154.54
.30.134]
11 311 ms 311 ms 328 ms te8-8.ccr02.jfk05.atlas.cogentco.com [154.54.26.
66]
12 328 ms 323 ms 324 ms teleglobe.jfk05.atlas.cogentco.com [154.54.12.94
]
13 316 ms 315 ms 315 ms if-12-0-0-13.core2.NTO-NewYork.as6453.net [216.6
.97.45]
14 437 ms 336 ms 504 ms if-5-0.mcore4.MTT-Montreal.as6453.net [216.6.115
.21]
15 320 ms 319 ms 320 ms if-3-0.mcore3.MTT-Montreal.as6453.net [216.6.114
.1]
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.

Trace complete.


216.98.48.57
tracert 216.98.48.57

Tracing route to lb-stun-prod.ubisoft.com [216.98.48.57]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 * * * Request timed out.
3 11 ms 11 ms 12 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
4 12 ms 11 ms 25 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 14 ms 17 ms 20 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 61 ms 65 ms 61 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

7 237 ms 240 ms 237 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 252 ms 237 ms 236 ms 130.117.136.1
9 240 ms 237 ms 237 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50
.117]
10 312 ms 325 ms 312 ms te0-0-0-1.ccr22.jfk02.atlas.cogentco.com [154.54
.30.21]
11 307 ms 308 ms 308 ms te8-8.ccr02.jfk05.atlas.cogentco.com [154.54.26.
66]
12 * * 312 ms teleglobe.jfk05.atlas.cogentco.com [154.54.12.94
]
13 311 ms 312 ms 311 ms if-12-0-0-13.core2.NTO-NewYork.as6453.net [216.6
.97.45]
14 602 ms 519 ms 719 ms if-5-0.mcore4.MTT-Montreal.as6453.net [216.6.115
.21]
15 322 ms 315 ms 315 ms if-3-0.mcore3.MTT-Montreal.as6453.net [216.6.114
.1]
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.

Trace complete.



216.98.48.102
tracert 216.98.48.102

Tracing route to lb-agora.ubisoft.com [216.98.48.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 * * * Request timed out.
3 11 ms 11 ms 11 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
4 12 ms 11 ms 11 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 31 ms 64 ms 54 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 48 ms 30 ms 56 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

7 240 ms 240 ms 239 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 237 ms 237 ms 236 ms 130.117.136.33
9 247 ms 237 ms 236 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50
.117]
10 312 ms 311 ms 311 ms te0-0-0-1.ccr22.jfk02.atlas.cogentco.com [154.54
.30.21]
11 311 ms 432 ms 451 ms te4-8.ccr02.jfk05.atlas.cogentco.com [154.54.7.1
0]
12 315 ms * * teleglobe.jfk05.atlas.cogentco.com [154.54.12.94
]
13 312 ms 312 ms 312 ms if-15-0-0-23.core2.NTO-NewYork.as6453.net [216.6
.97.65]
14 315 ms 315 ms 315 ms if-5-0.mcore4.MTT-Montreal.as6453.net [216.6.115
.21]
15 316 ms 316 ms 315 ms if-3-0.mcore3.MTT-Montreal.as6453.net [216.6.114
.1]
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.

Trace complete.
 
Last edited:
Not sure if this should go here or somewhere else. But can you guys please have a look at the shaping of gog.com. Since the relaunch it has been slow during the day when downloading. No such issues with steam.

Hi Stefan

How do Gog deliver the files to you? Is it a normal http download, or do they have a client like Steam? If it's http it shouldn't be shaped. If you'd like to do a test with me PM me your account details and then once I've confirmed run a download with nothing else interfering on your connection and let me know the exact times so that I can see how the traffic was shaped.
 
@Necuno

is this an MWEB specific issue? I'm only asking because I seem to recall the Internet play on the original Vegas being generally unstable.
 
@Necuno

is this an MWEB specific issue? I'm only asking because I seem to recall the Internet play on the original Vegas being generally unstable.

i've readup/talked about this and you are right that vegas does have auth issues. guess i'll see how it goes then, it's just annoying when it turns out flat and you can't auth or play. i posted this because i thought initially it might be because of some of the ipc issues mweb had be having/upgrading/fixing.
 
Hi Stefan

How do Gog deliver the files to you? Is it a normal http download, or do they have a client like Steam? If it's http it shouldn't be shaped. If you'd like to do a test with me PM me your account details and then once I've confirmed run a download with nothing else interfering on your connection and let me know the exact times so that I can see how the traffic was shaped.

GOG (www.gog.com) is direct download from their location to your pc. there is no p2p/"steam like client" invovled. well that's how it was when i used them few times.
 
i've readup/talked about this and you are right that vegas does have auth issues. guess i'll see how it goes then, it's just annoying when it turns out flat and you can't auth or play. i posted this because i thought initially it might be because of some of the ipc issues mweb had be having/upgrading/fixing.

I hear you.

If you can highlight anything specific that you'd like us to look at please let me know and we can arrange some testing.
 
I'm currently having issues with my international going down periodically causing me to drop from Starcraft 2 games on battle.net.

Quite a pain. When I start timing out I alt tab and open up netlimiter - bw usage is minimal so it's not the line being maxed, next I ping 196.25.1.1 which is fine (~70ms) and news.bbc.co.uk which times out. Not sure if anyone else is experiencing this.

I'm in Rondebosch, phone number is 021 685 ...

Let me know what additional info would be helpful. It's just happened twice in 10 minutes.
 
Hi rsd

I'm showing a ping of 265ms to news.bbc from our test bench. Starcraft is generally going to be a tricky one to troubleshoot all I can really look at is the connection as far as our London side and your route to your opponent could be going anywhere from there. We had some reports of slow logins to Battlenet initially, however I have had the game for myself for about 2 weeks now and haven't noticed this yet myself.

It's possible you are picking up some Telkom latency at this time of day as it has been an issue in that area recently. I would suggest checking some tracerts to see if you can see a bottleneck anywhere.
 
International has been going down, but it comes back after a minute or so.

That's exactly the issue I had. It went down (pings timing out) then came back after a minute. Unfortunately a minute is all it takes to get dropped. Glad it's not just me experiencing it. It's definitely not a problem specific to starcraft 2. Will post here if it happens again.
 
Top
Sign up to the MyBroadband newsletter
X