High latency with WiMax

pierreb

Member
Joined
Mar 10, 2009
Messages
13
Reaction score
0
Hello all

First post, so if I miss some info, please bear with me.

I have a WiMax ADSL with Imagine as an ISP. I use to use Webafrica, but found it difficult with there dual accounts (local/international).

When I was with Webafrica, my ping (got this from COD4) was sitting between 50 and 60. Currently my ping is sitting between 110 to 160 with the new ISP. I spoke to them and they said it is my line that is slow.

Can someone maybe tell me where to go look and what to look for. If you need any other info from me, please let me know, but keep in mind I'm not a network guru so I won't always know how to get the info required.

Thanks
 
The server is : 196.2.97.212:28963

I have done a tracert, but I did a print screen and saved it as an image. I can't figure out how to get the image on here though...
 
You can right click on command prompt and select "Mark". Then select the text and paste here. Here is my ping to your COD4 server over Wimax:

Pinging 196.2.97.212 with 32 bytes of data:
Reply from 196.2.97.212: bytes=32 time=77ms TTL=111
Reply from 196.2.97.212: bytes=32 time=73ms TTL=111
Reply from 196.2.97.212: bytes=32 time=59ms TTL=111
Reply from 196.2.97.212: bytes=32 time=82ms TTL=111

Ping statistics for 196.2.97.212:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 82ms, Average = 72ms
 
Is this a local server? Soz, I am at work and are unable to check.

Edit: Do you have Telkom WiMax, pierreb?
 
Yip, its local. As far as I know the servers are maintained by the iBurst guys.
 
Hello

Here is the tracrt from my system and right at the end a straight forward ping. Hope this will sched some light on te subject:

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\pierre>tracert 196.2.97.212

Tracing route to wbs-196-2-97-212.wbs.co.za [196.2.97.212]
over a maximum of 30 hops:

1 72 ms 79 ms 74 ms 196-210-136-1-rndf-esr-5.dynamic.isadsl.co.za [1
96.210.136.1]
2 53 ms 79 ms 75 ms cdsl1-rba-vl2157.ip.isnet.net [196.38.73.217]
3 104 ms 75 ms 54 ms 196.38.73.142
4 76 ms 85 ms 74 ms cdsl1-rba-vl52.ip.isnet.net [196.38.73.137]
5 88 ms 85 ms 74 ms core5a-rba-gi0-0-0.ip.isnet.net [196.26.0.42]
6 102 ms 82 ms 74 ms cp1-jinx-gi0-1.ip.isnet.net [196.26.0.253]
7 78 ms 88 ms 89 ms ge0-3.br1.jnb7.za.mtnbusiness.net [196.30.228.24
1]
8 87 ms 75 ms 83 ms ge0-1.cr1.jnb7.za.mtnbusiness.net [196.30.228.12
2]
9 101 ms 89 ms 74 ms ge5-0-2.cr6.jnb6.za.mtnbusiness.net [196.30.121.
82]
10 72 ms 84 ms 79 ms ge3-1.gw14.jnb6.za.mtnbusiness.net [196.30.1.34]

11 88 ms 74 ms 84 ms 66.8.42.22
12 * * * Request timed out.
13 64 ms 74 ms 89 ms 196.30.31.234
14 147 ms 74 ms 111 ms 196.30.31.218
15 63 ms 74 ms 79 ms wbs-196-2-97-212.wbs.co.za [196.2.97.212]

Trace complete.

C:\Users\pierre>tracert 196.2.97.212

Tracing route to wbs-196-2-97-212.wbs.co.za [196.2.97.212]
over a maximum of 30 hops:

1 121 ms 79 ms 68 ms 196-210-136-1-rndf-esr-5.dynamic.isadsl.co.za [1
96.210.136.1]
2 57 ms 74 ms 90 ms cdsl1-rba-vl2157.ip.isnet.net [196.38.73.217]
3 94 ms 73 ms 79 ms 196.38.73.142
4 78 ms 55 ms 73 ms cdsl1-rba-vl52.ip.isnet.net [196.38.73.137]
5 92 ms 60 ms 89 ms core5a-rba-gi0-0-0.ip.isnet.net [196.26.0.42]
6 102 ms 94 ms 64 ms cp1-jinx-gi0-1.ip.isnet.net [196.26.0.253]
7 83 ms 64 ms 79 ms ge0-3.br1.jnb7.za.mtnbusiness.net [196.30.228.24
1]
8 45 ms 78 ms 99 ms ge0-1.cr1.jnb7.za.mtnbusiness.net [196.30.228.12
2]
9 58 ms 74 ms 74 ms ge5-0-2.cr6.jnb6.za.mtnbusiness.net [196.30.121.
82]
10 63 ms 74 ms 84 ms ge3-1.gw14.jnb6.za.mtnbusiness.net [196.30.1.34]

11 63 ms 99 ms 89 ms 66.8.42.22
12 * * * Request timed out.
13 85 ms 84 ms 74 ms 196.30.31.234
14 88 ms 74 ms 89 ms 196.30.31.218
15 78 ms 74 ms 83 ms wbs-196-2-97-212.wbs.co.za [196.2.97.212]

Trace complete.

C:\Users\pierre>tracert 196.2.97.212

Tracing route to wbs-196-2-97-212.wbs.co.za [196.2.97.212]
over a maximum of 30 hops:

1 61 ms 100 ms 88 ms 196-210-136-1-rndf-esr-5.dynamic.isadsl.co.za [1
96.210.136.1]
2 57 ms 69 ms 89 ms cdsl1-rba-vl2157.ip.isnet.net [196.38.73.217]
3 63 ms 94 ms 78 ms 196.38.73.142
4 97 ms 59 ms 69 ms cdsl1-rba-vl52.ip.isnet.net [196.38.73.137]
5 63 ms 89 ms 89 ms core5a-rba-gi0-0-0.ip.isnet.net [196.26.0.42]
6 58 ms 84 ms 85 ms cp1-jinx-gi0-1.ip.isnet.net [196.26.0.253]
7 73 ms 89 ms 79 ms ge0-3.br1.jnb7.za.mtnbusiness.net [196.30.228.24
1]
8 88 ms 84 ms 74 ms ge0-1.cr1.jnb7.za.mtnbusiness.net [196.30.228.12
2]
9 58 ms 100 ms 108 ms ge5-0-2.cr6.jnb6.za.mtnbusiness.net [196.30.121.
82]
10 83 ms 78 ms 85 ms ge3-1.gw14.jnb6.za.mtnbusiness.net [196.30.1.34]

11 78 ms 100 ms 89 ms 66.8.42.22
12 * * * Request timed out.
13 58 ms 83 ms 84 ms 196.30.31.234
14 58 ms 89 ms 78 ms 196.30.31.218
15 88 ms 123 ms 59 ms wbs-196-2-97-212.wbs.co.za [196.2.97.212]

Trace complete.

C:\Users\pierre>ping 196.2.97.212

Pinging 196.2.97.212 with 32 bytes of data:
Reply from 196.2.97.212: bytes=32 time=63ms TTL=113
Reply from 196.2.97.212: bytes=32 time=59ms TTL=113
Reply from 196.2.97.212: bytes=32 time=98ms TTL=113
Reply from 196.2.97.212: bytes=32 time=83ms TTL=113

Ping statistics for 196.2.97.212:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 98ms, Average = 75ms
 
That is what I thought. But looking at the tracert, I do have some very slow spots in the route.

And when I log on to the game my ping sucks!! Yet the average speed of the ping from the other guys are sitting on from as low as 30 to about 60
 
I have tried the SGS servers and get exactly the same thing back.

I ran a ping last night while playing and every now and then I got a spike coming through (about 1 every 2 minutes) which shoots up to 140ms. I was pinging the router (which is not located at my premises)

So it does seem to be the WiMax giving me hassles.

Thanks for the help guys.
 
from what I was explained, the router does not sit in my premises, but with Telkom. So I don't have access to it.

What I did was to take the first IP from the tracert and ping that. I assumed that would be my router. Please note, I'm not a guru, just working on assumptions.
 
Top
Sign up to the MyBroadband newsletter
X