384k ADSL Ping

[D3x]

Do a continuous ping to hop 2: 41.185.74.1
If that looks ok then it's an ISP issue. From your traceroutes it looks like there's something wrong on WA's side.


WA: 2 dsl-185-74-1.dynamic.wa.co.za (41.185.74.1) 53.350 ms 64.145 ms 74.117 ms
STILL ON WA: 3 vl105.cr.gw.cpt.za.wa.co.za (196.220.59.250) 106.157 ms 113.596 ms 123.637 ms <<< Look at those latencies!
STILL ON WA: 4 vl32.er.gw.cpt.za.wa.co.za (41.185.0.26) 135.677 ms 144.178 ms 154.228 ms
STILL ON WA: 5 upstream.vl102.gw.cpt.za.wa.co.za (196.220.59.230) 164.114 ms upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 174.124 ms upstream.vl102.gw.cpt.za.wa.co.za (196.220.59.230) 184.235 ms
ON TELKOM: 6 lon-ip-dir-telecity-pos-7-0-2.telkom-ipnet.co.za (196.43.9.150) 357.548 ms 235.427 ms 238.992 ms

As requested:

derrick@Dex ~ $ ping 41.185.74.1
PING 41.185.74.1 (41.185.74.1) 56(84) bytes of data.
64 bytes from 41.185.74.1: icmp_seq=1 ttl=254 time=76.6 ms
64 bytes from 41.185.74.1: icmp_seq=2 ttl=254 time=90.3 ms
64 bytes from 41.185.74.1: icmp_seq=3 ttl=254 time=76.3 ms
64 bytes from 41.185.74.1: icmp_seq=4 ttl=254 time=257 ms
64 bytes from 41.185.74.1: icmp_seq=5 ttl=254 time=83.8 ms
64 bytes from 41.185.74.1: icmp_seq=6 ttl=254 time=75.3 ms
64 bytes from 41.185.74.1: icmp_seq=7 ttl=254 time=106 ms
64 bytes from 41.185.74.1: icmp_seq=8 ttl=254 time=275 ms
64 bytes from 41.185.74.1: icmp_seq=9 ttl=254 time=153 ms
64 bytes from 41.185.74.1: icmp_seq=10 ttl=254 time=116 ms
64 bytes from 41.185.74.1: icmp_seq=11 ttl=254 time=82.1 ms
64 bytes from 41.185.74.1: icmp_seq=12 ttl=254 time=268 ms
64 bytes from 41.185.74.1: icmp_seq=13 ttl=254 time=75.5 ms
64 bytes from 41.185.74.1: icmp_seq=14 ttl=254 time=75.3 ms
64 bytes from 41.185.74.1: icmp_seq=15 ttl=254 time=75.2 ms
64 bytes from 41.185.74.1: icmp_seq=16 ttl=254 time=147 ms
64 bytes from 41.185.74.1: icmp_seq=17 ttl=254 time=114 ms
64 bytes from 41.185.74.1: icmp_seq=18 ttl=254 time=80.3 ms
64 bytes from 41.185.74.1: icmp_seq=19 ttl=254 time=74.3 ms
64 bytes from 41.185.74.1: icmp_seq=20 ttl=254 time=128 ms
64 bytes from 41.185.74.1: icmp_seq=21 ttl=254 time=94.1 ms
64 bytes from 41.185.74.1: icmp_seq=22 ttl=254 time=74.3 ms

[D3x]

[D3x]

Now, where are those guys who wanted me to post results?

[Blackhand]

Driving home from work =)

Anyway, as suspected, your latency is fluctuating wildly very early in your hops so its not the fault of your ISP and a strong indicator of congestion.
Most common cause is downloads/torrents running on one of your PCs, but equally common is spyware/viruses munching up your bandwidth. DON'T rule this out till you have bandwidth monitors installed on every PC/device and can confirm that they are using no bandwidth when idle.
After that, it could be a faulty router or congestion at your exchange. The faulty router would most likely cause packet loss as well which you aren't getting and congestion at the exchange more often than not just results in high latency, not really the kind of fluctuation your seeing (though it could still be possible).

Basically, step 1 is get bandwidth monitors and be absolutely sure on your side is good before blowing money on a new router or battling with Telkom to fix up a possibly congested exchange.

[D3x]

Well, I am running Linux Mint & my router is like 2 days old. I unwrapped it the other day, its new.

Telkom told me to restart both my PC (the only one in the house) & router simultaneously.

[D3x]

I am in JHB.

To CT



Jo JHB

[ozoned]

Looks like Webafrica has higher latency at the moment. (Sry, forgot to ping an int site)

Afrihost: IS uncapped acc.
TO: www.afrihost.co.za
PING www.afrihost.co.za (196.38.88.28) 56(84) bytes of data.
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=1 ttl=53 time=30.6 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=2 ttl=53 time=28.6 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=3 ttl=53 time=27.1 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=4 ttl=53 time=30.6 ms

To: ftp.is.co.za
PING ftp.is.co.za (196.4.160.12) 56(84) bytes of data.
64 bytes from ftp.is.co.za (196.4.160.12): icmp_seq=1 ttl=57 time=30.7 ms
64 bytes from ftp.is.co.za (196.4.160.12): icmp_seq=2 ttl=57 time=29.6 ms
64 bytes from ftp.is.co.za (196.4.160.12): icmp_seq=3 ttl=57 time=30.6 ms
64 bytes from ftp.is.co.za (196.4.160.12): icmp_seq=4 ttl=57 time=30.2 ms

To: www.gmail.com
PING googlemail.l.google.com (74.125.77.19) 56(84) bytes of data.
64 bytes from ew-in-f19.1e100.net (74.125.77.19): icmp_seq=1 ttl=48 time=213 ms
64 bytes from ew-in-f19.1e100.net (74.125.77.19): icmp_seq=2 ttl=48 time=217 ms
64 bytes from ew-in-f19.1e100.net (74.125.77.19): icmp_seq=3 ttl=48 time=213 ms
64 bytes from ew-in-f19.1e100.net (74.125.77.19): icmp_seq=4 ttl=48 time=225 ms

ISP Webafrica standard shaped 1GB/mth acc
TO: www.afrihost.co.za
PING www.afrihost.co.za (196.38.88.28) 56(84) bytes of data.
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=1 ttl=50 time=83.2 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=2 ttl=50 time=82.1 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=3 ttl=50 time=81.7 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=4 ttl=50 time=81.3 ms

To: ftp.is.co.za
PING ftp.is.co.za (196.4.160.12) 56(84) bytes of data.
64 bytes from ftp.is.co.za (196.4.160.12): icmp_seq=1 ttl=54 time=73.5 ms
64 bytes from ftp.is.co.za (196.4.160.12): icmp_seq=2 ttl=54 time=77.0 ms
64 bytes from ftp.is.co.za (196.4.160.12): icmp_seq=3 ttl=54 time=74.6 ms
64 bytes from ftp.is.co.za (196.4.160.12): icmp_seq=4 ttl=54 time=72.8 ms

[Blackhand]

@ozoned, while that is slightly raised, its "acceptable". The HUGE difference is you can see the latency is consistent, not spiking into the 100s/200s.

@D3x, the best advice I can give you if your absolutely sure you have 0 bandwidth usage on your end, is to phone Telkom and start off the painful process of getting them to check out your line and exchange.
Also, could you perhaps post your SNR margin and line attenuation found in your router statistics?

[D3x]

@D3x, the best advice I can give you if your absolutely sure you have 0 bandwidth usage on your end, is to phone Telkom and start off the painful process of getting them to check out your line and exchange.
Also, could you perhaps post your SNR margin and line attenuation found in your router statistics?

ADSL Link_____________Downstream______________Upstream
Connection Speed________384 kbps________________128 kbps
Line Attenuation__________34.5 db_________________20.0 db
Noise Margin_____________39.0 db_________________22 db

[Blackhand]

You line attenuation and noise margin are good, so its not the connection between your router and the exchange that's the problem. Starting to look a lot like congestion at the exchange.

[D3x]

Thanks Blackhand. WA gave me DNS settings to put into my local connection. I will try it out today & see what happens.

The funny thing is, WA say their servers are in CT ( In know they have in JHB though too ). Now, when I ping CT from JHB I get a 20ms less than pinging JHB from JHB? lol

[rodga]

ill post my results when i get home this eve, im also with WA

can someone tell me how to do a traceroute?? maybe a link to explain?

[Blackhand]

Start -> Run -> cmd

tracert www.mybroadband.co.za

[rodga]

fanx

[rodga]

just did this from my work pc

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

1 2 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 23 ms 23 ms 22 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.43.8.198]
4 157 ms 66 ms 88 ms 196.43.25.138
5 * 24 ms 22 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181]
6 31 ms 26 ms 60 ms 196.30.1.21
7 303 ms * 98 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
8 22 ms 25 ms 28 ms 196.30.213.108
9 366 ms 502 ms 196 ms firewall1.jnb2.host-h.net [196.7.216.173]
10 71 ms 359 ms 959 ms mybroadband.co.za [41.203.21.137]

Trace complete.

http://www.speedtest.net/result/937529061.png

what does it mean? lol looks bad