384k ADSL Ping

ozoned

Well-Known Member
Joined
Mar 30, 2010
Messages
267
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

Senior Member
Joined
Dec 22, 2004
Messages
582
@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?
 
Last edited:

D3x

Expert Member
Joined
Oct 23, 2009
Messages
1,834
@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
 
Last edited:

Blackhand

Senior Member
Joined
Dec 22, 2004
Messages
582
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

Expert Member
Joined
Oct 23, 2009
Messages
1,834
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

Honorary Master
Joined
May 9, 2007
Messages
10,192
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?
 

rodga

Honorary Master
Joined
May 9, 2007
Messages
10,192
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
 

ozoned

Well-Known Member
Joined
Mar 30, 2010
Messages
267
From my Afrihost acc: Trying to simulate what Blackhand is talking about:
Start with nothing chewing BW, then run
Code:
curl -o test.bin --limit-rate 30k http://london1.linode.com/100MB-london.bin

Then ping for a bit, finally kill the dl. Gets you:

PING www.mybroadband.co.za (41.203.21.137) 56(84) bytes of data.
under load...
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=1 ttl=51 time=932 ms
64 bytes from 41.203.21.137: icmp_seq=2 ttl=51 time=896 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=3 ttl=51 time=340 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=4 ttl=51 time=37.3 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=5 ttl=51 time=294 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=6 ttl=51 time=336 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=7 ttl=51 time=341 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=8 ttl=51 time=347 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=9 ttl=51 time=319 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=10 ttl=51 time=355 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=11 ttl=51 time=344 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=12 ttl=51 time=32.4 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=13 ttl=51 time=349 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=14 ttl=51 time=345 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=15 ttl=51 time=348 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=16 ttl=51 time=309 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=17 ttl=51 time=356 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=18 ttl=51 time=355 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=19 ttl=51 time=343 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=20 ttl=51 time=33.5 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=21 ttl=51 time=333 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=22 ttl=51 time=317 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=23 ttl=51 time=360 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=24 ttl=51 time=365 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=25 ttl=51 time=348 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=26 ttl=51 time=272 ms
normal starts here again...
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=27 ttl=51 time=31.3 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=28 ttl=51 time=30.2 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=29 ttl=51 time=32.1 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=30 ttl=51 time=31.2 ms
64 bytes from mybroadband.co.za (41.203.21.137): icmp_seq=31 ttl=51 time=30.1 ms
 

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,437
D3x,

It looks like the exchange is congested/broken.

You can try logging on using the guest telkom account (sorry I dont recall the username/pwd), do a tracert to telkom.co.za and have a look at the latencies on the second hop.

If its still bad, then its probably an exchange problem....oh...and good luck with sorting that out!
 

rodga

Honorary Master
Joined
May 9, 2007
Messages
10,192
heres my home web africa stuff

938247927.png


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 * * * Request timed out.
3 49 ms 44 ms 47 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 188 ms 308 ms 162 ms vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
5 50 ms 48 ms 45 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
6 48 ms 48 ms 47 ms wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]
7 48 ms 49 ms 52 ms 196.43.25.206
8 50 ms 48 ms 49 ms 196.7.8.206
9 70 ms 73 ms 71 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
10 67 ms 68 ms 67 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 * 69 ms 65 ms 196.30.213.108
12 69 ms 69 ms 68 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 70 ms 69 ms 68 ms www.mybroadband.co.za [41.203.21.137]

Trace complete.
 
Top