Web Africa ADSL general feedback

Hi all,

Following up with our networking guys about the slow speeds now.
We're aware of the Diablo 3 latency issues, these are busy being looked into. We're also reviewing and running tests with the other mentioned slow speeds.
 
This is really terrible. Couldn't give a toss about the Diablo people right now TBH, the resolution of problems with basic business protocols like HTTP should be the highest priority at the moment.
 
Hi all,

Following up with our networking guys about the slow speeds now.
We're aware of the Diablo 3 latency issues, these are busy being looked into. We're also reviewing and running tests with the other mentioned slow speeds.

Jeff, FYI - have Axxes and Mweb friends whom have the exact same latency as my WA account (between 350ms to 400ms) - we think the high load on the servers is adding about 150ms to ping times. During off (gaming) peak my latency is about 200ms
 
Jeff, FYI - have Axxes and Mweb friends whom have the exact same latency as my WA account (between 350ms to 400ms) - we think the high load on the servers is adding about 150ms to ping times. During off (gaming) peak my latency is about 200ms

Nope, tested last night with a Axxess account and WA account.

WA account was on 500+ms Axxess account was on 200ms
 
Nope, tested last night with a Axxess account and WA account.

WA account was on 500+ms Axxess account was on 200ms

Weird, all of ours were hovering at 400-350ms (all playing at the same time)

EDIT: and early this morning I was getting 200ms on WA
 
Last edited:
Seems like the links to MTN weren't 100% stable earlier this morning. Traffic graphing looks better on our side as of about 20 mins ago.
 
A tracert might be able to help WA find the weakest link too, I'll tracert my side too, server login name is eu.logon.battle.net

Won't really help with in game latency issues.

To find the server's IP run the following in command prompt:
netstat -naob -p tcp

Look for the IP's Diablo3.exe is connecting to.
 
Won't really help with in game latency issues.

To find the server's IP run the following in command prompt:
netstat -naob -p tcp

Look for the IP's Diablo3.exe is connecting to.

It uses port 1119 TCP to establish it's connections on.
 
Still messed in Jhb - took me 4 refreshes to be able to get to the post reply option:


Tracing route to www.mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 8 ms 8 ms tprn-ip-esr-2.ipnet.wa.co.za [41.185.76.1]
3 33 ms 32 ms 32 ms 196.220.59.222
4 35 ms 34 ms 34 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 52 ms 33 ms 35 ms wnls-cr1-vl-10.wa.co.za [41.185.0.42]
6 69 ms 35 ms 34 ms wbs-ip-hsll-1-vl-102.telkom-ipnet.co.za [196.220
.59.230]
7 35 ms 35 ms 34 ms 196.43.11.218
8 33 ms 33 ms 33 ms 196.43.25.206
9 85 ms 33 ms 33 ms mtn-gw.telkom-ipnet.co.za [196.25.165.198]
10 37 ms 34 ms 66 ms tb-cr-1.za--tb-pr-1.za-a.mtnns.net [196.44.18.14
0]
11 39 ms 37 ms 68 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

12 79 ms 63 ms 111 ms rb-cr-1.za--ct-cr-1.za.mtnns.net [196.44.31.128]

13 91 ms 89 ms 62 ms 196.44.31.97
14 93 ms 64 ms 64 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.2
2]
15 69 ms 62 ms 62 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
16 110 ms 64 ms 63 ms core-router1.jnb2.host-h.net [196.30.213.108]
17 68 ms 66 ms 65 ms 41.72.136.53
18 101 ms 64 ms 65 ms mybroadband.co.za [41.203.21.137]

Trace complete.

C:\Documents and Settings\User>
 
To CNN:


C:\Documents and Settings\User>tracert www.cnn.com

Tracing route to www.cnn.com [157.166.226.26]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 8 ms tprn-ip-esr-2.ipnet.wa.co.za [41.185.76.1]
3 35 ms 34 ms 34 ms 196.220.59.214
4 50 ms 36 ms 33 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 32 ms 92 ms 52 ms 41-66-150-177-b1.WC-RO-DCE-2-to-WEB001-CPE.afric
ainx.net [41.66.150.177]
6 186 ms 183 ms 186 ms CORE_GB-LD-GS-MEC-1_TO_GB-LD-GS-MSC-1_AINX_P2P__
1G_gb [41.84.12.141]
7 198 ms 186 ms 220 ms 195.50.122.217
8 247 ms 184 ms 189 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]

9 211 ms 187 ms 238 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]

10 272 ms 253 ms 257 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

11 309 ms 267 ms 281 ms ae-10-10.ebr2.Washington12.Level3.net [4.69.148.
50]
12 275 ms 259 ms 311 ms ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
13 276 ms 305 ms 273 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
14 299 ms 270 ms 317 ms ae-1-51.edge4.Atlanta2.Level3.net [4.69.150.13]

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.

Trace complete.

C:\Documents and Settings\User>
 
Seems like the links to MTN weren't 100% stable earlier this morning. Traffic graphing looks better on our side as of about 20 mins ago.
No noticeable difference here. It does seem to be affecting people in Jhb more.
 
Likewise here -- MyBB starts the page and then just hangs -- other sites hardly load at all. ( Now using my Telkom account -- which NEVER fails )

Seems to me that the shaping -- whatever they using -- is misconfigured -- unless they just want to get rid of us all ?

I hate churn -- but maybe time to cut losses and get another Telkom account -- maybe a SAIX one ?

Still experiencing something similar here. Yet the status on their website claims that everything is peachy. Hmm...
 
If this continues for much longer, I'm going to recommend to our management that we change providers. Can't work like this.
 
Experiencing these frequent time-outs as well in Cape Town. Really not happy - will probably move to MWEB if this continues. Started a few days ago.
 
Top
Sign up to the MyBroadband newsletter
X