Extremely High Latency

P

Preacher

Well-Known Member
Joined
Jun 20, 2007
Messages
104
Reaction score
0
Location
Little Falls, Johannesburg
I am having a problem which at first I thought was a seacom issue but seeing as it has been apparently sorted, I am hoping that someone can maybe shed some light.

Firstly, I stay in Joburg in the Westrand. I have a 4 meg DSL connection...

Now my problem... it doesn't matter which ISP I use, I am getting very high latency and some websites dont even wanna load up. Pings vary from maybe 600 - over 2000. I check my router status and it says all is clear, no errors... my ISP say it is a network error in my area. I don't know if maybe telkoms DSL 10 meg upgrades might be causing the problems but I am frustrated.

Any ideas? :/
 
please post a traceroute so i can have a look. in windows --> start --> command prompt --> type: traceroute www.google.co.za and enter. :]
 
We also need to look at the modem / router.

How new is it?
What is it?

Have you tried with a different modem / router?

Have you tried with a different computer?

This is very strange...
 
i'm also in the west rand, and i'm also experiencing latency and throughput problems. i've tried with two different routers and two different accounts (mweb and axxess), so the common denominator happens to be telkom.


imajin said:

Code: 
Pinging www.mybroadband.co.za [41.203.21.136] with 32 bytes of data:
Reply from 41.203.21.136: bytes=32 time=1021ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1071ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1123ms TTL=50
Reply from 41.203.21.136: bytes=32 time=909ms TTL=50
Reply from 41.203.21.136: bytes=32 time=826ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1078ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1126ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1055ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1036ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1123ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1178ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1133ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1105ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1329ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1424ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1426ms TTL=50

Ping statistics for 41.203.21.136:
    Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 826ms, Maximum = 1426ms, Average = 1122ms
Code: 
Tracing route to www.mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:

  1     3 ms     2 ms     5 ms  192.168.1.1
  2   842 ms  1038 ms  1036 ms  41-133-82-1.dsl.mweb.co.za [41.133.82.1]
  3  1298 ms  1125 ms   958 ms  tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
  4  1057 ms  1085 ms  1002 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   877 ms   834 ms   708 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   726 ms   675 ms   649 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
  7   949 ms   960 ms   849 ms  rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.
43.8.198]
  8   723 ms   767 ms   802 ms  196.43.25.138
  9   969 ms   833 ms   734 ms  ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
]
 10   919 ms  1056 ms   997 ms  196.30.1.21
 11   975 ms   915 ms   920 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
 12   810 ms   899 ms   938 ms  196.30.213.108
 13   925 ms  1019 ms  1145 ms  firewall1.jnb2.host-h.net [196.7.216.173]
 14  1436 ms  1770 ms  1941 ms  mybroadband.co.za [41.203.21.136]

Trace complete.
Click to expand...
 
Thanks portcullis, I will try that tonight.

I am pretty much getting similar pings to imajin... as for my router details, I bought a new NetGear DGN 1000 (I think) about 6 weeks ago... but even when I got back to my old router, same story. I get the same results on my laptop. Will try your trace route suggestion and will post my results here asap.

thanks
 
i have no idea what happened, but my line seems to be okay now:
Code: 
Pinging www.myadsl.co.za [41.203.21.136] with 32 bytes of data:
Reply from 41.203.21.136: bytes=32 time=17ms TTL=50
Reply from 41.203.21.136: bytes=32 time=30ms TTL=50
Reply from 41.203.21.136: bytes=32 time=14ms TTL=50
Reply from 41.203.21.136: bytes=32 time=126ms TTL=50
Reply from 41.203.21.136: bytes=32 time=54ms TTL=50
Reply from 41.203.21.136: bytes=32 time=41ms TTL=50
Reply from 41.203.21.136: bytes=32 time=53ms TTL=50
Reply from 41.203.21.136: bytes=32 time=65ms TTL=50
Reply from 41.203.21.136: bytes=32 time=17ms TTL=50
Reply from 41.203.21.136: bytes=32 time=191ms TTL=50
Reply from 41.203.21.136: bytes=32 time=128ms TTL=50
Reply from 41.203.21.136: bytes=32 time=153ms TTL=50
Reply from 41.203.21.136: bytes=32 time=90ms TTL=50
Reply from 41.203.21.136: bytes=32 time=26ms TTL=50
Reply from 41.203.21.136: bytes=32 time=42ms TTL=50
Reply from 41.203.21.136: bytes=32 time=131ms TTL=50

Ping statistics for 41.203.21.136:
    Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 191ms, Average = 73ms
Code: 
Tracing route to www.mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:

  1     5 ms     3 ms     3 ms  192.168.1.1
  2   128 ms   102 ms    66 ms  41-133-82-1.dsl.mweb.co.za [41.133.82.1]
  3    30 ms    31 ms    66 ms  tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
  4    13 ms    10 ms     9 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5    16 ms    21 ms    12 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6    11 ms    12 ms    11 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
  7    11 ms    10 ms    12 ms  rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.
43.8.198]
  8    11 ms    14 ms    11 ms  196.43.25.138
  9    12 ms    13 ms    14 ms  ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
]
 10    16 ms    15 ms    14 ms  ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.2
2]
 11    17 ms    13 ms    13 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
 12    26 ms    53 ms    48 ms  196.30.213.108
 13    22 ms    23 ms    34 ms  firewall1.jnb2.host-h.net [196.7.216.173]
 14   117 ms    80 ms    84 ms  mybroadband.co.za [41.203.21.136]

Trace complete.
 
Still the first two hops are worrying, it shouldnt spike to 128 then back to 11, it should be constant. Local DSL pings should never get above 20 when on a 4 meg line

Edit: the ping to your router should also be less than 1 ms.
 
Last edited:
Runeblood said:
Still the first two hops are worrying, it shouldnt spike to 128 then back to 11, it should be constant. Local DSL pings should never get above 20 when on a 4 meg line

Edit: the ping to your router should also be less than 1 ms.
Click to expand...

i think the ping being 3ms to the router is because of a wireless link in my network.
 
yea. im running through powerline with a wireless hop from the firewall to my router. ~5ms.

not a gamer though. more like a streamer.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X