384k ADSL Ping

D

D3x

Expert Member
Joined
Oct 23, 2009
Messages
1,834
Reaction score
67
Location
Sunninghill
Guys please can the 384k users, please post the following results, I'll post mine first:

ISP: Webafrica (Titan 1 Deal)

Bundle: 15GB / month (ADSL line rental included)

Ping: 134 ms

How does this ping compare to other 384k users?
 
What host are you pinging?
Are you getting the latency figure from a speed test site? If so which one?

If you're getting 134 ms to overseas then you have a very good connection!
 
Excuse me Paul but I am a noob, that is my speedtest.net result <50.
 
134ms is bad, very bad for a local site ping.
You should be in the <60ms region.
A buddy of mine with a 384k line plays Quake Live with me and his in-game ping is 33ms.
 
Before someone from my ISP tries pulling the wool over my eyes later, can someone comment on these results as I have no clue what I am looking at:



www.mweb.co.za

derrick@Dex ~ $ traceroute www.mweb.co.za
traceroute to www.mweb.co.za (196.2.63.110), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.462 ms 1.886 ms 2.258 ms
2 dsl-185-74-1.dynamic.wa.co.za (41.185.74.1) 54.580 ms 64.385 ms 74.135 ms
3 vl105.cr.gw.cpt.za.wa.co.za (196.220.59.250) 105.124 ms 115.767 ms 125.838 ms
4 vl35.er.gw.cpt.za.wa.co.za (41.185.0.38) 138.164 ms 146.692 ms 156.699 ms
5 upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 165.466 ms upstream.vl102.gw.cpt.za.wa.co.za (196.220.59.230) 175.514 ms upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 184.937 ms
6 196.43.39.62 (196.43.39.62) 197.275 ms 75.769 ms 75.185 ms
7 tiscali-gw.telkom-ipnet.co.za (196.25.55.178) 86.087 ms 96.080 ms 105.824 ms
8 196.41.144.36 (196.41.144.36) 118.029 ms * *


www.mybb.co.za

derrick@Dex ~ $ traceroute www.mybb.co.za
traceroute to www.mybb.co.za (213.133.106.183), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.340 ms 1.920 ms 1.975 ms
2 dsl-185-74-1.dynamic.wa.co.za (41.185.74.1) 53.350 ms 64.145 ms 74.117 ms
3 vl105.cr.gw.cpt.za.wa.co.za (196.220.59.250) 106.157 ms 113.596 ms 123.637 ms
4 vl32.er.gw.cpt.za.wa.co.za (41.185.0.26) 135.677 ms 144.178 ms 154.228 ms
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
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
7 ge-6-2-903.car5.London1.Level3.net (212.113.10.69) 260.772 ms 270.012 ms 279.663 ms
8 ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 286.102 ms 298.175 ms 307.908 ms
9 ae-46-46.ebr2.Amsterdam1.Level3.net (4.69.143.73) 323.406 ms ae-47-47.ebr2.Amsterdam1.Level3.net (4.69.143.77) 328.843 ms ae-48-48.ebr2.Amsterdam1.Level3.net (4.69.143.81) 336.606 ms
10 ae-1-100.ebr1.Amsterdam1.Level3.net (4.69.141.169) 346.413 ms 355.146 ms 365.944 ms
11 ae-48-48.ebr2.Dusseldorf1.Level3.net (4.69.143.210) 383.893 ms ae-46-46.ebr2.Dusseldorf1.Level3.net (4.69.143.202) 392.399 ms ae-47-47.ebr2.Dusseldorf1.Level3.net (4.69.143.206) 398.995 ms
12 ae-1-100.ebr1.Dusseldorf1.Level3.net (4.69.141.149) 251.602 ms 249.075 ms 250.113 ms
13 ae-46-46.ebr2.Frankfurt1.Level3.net (4.69.143.170) 262.995 ms ae-48-48.ebr2.Frankfurt1.Level3.net (4.69.143.178) 277.522 ms ae-46-46.ebr2.Frankfurt1.Level3.net (4.69.143.170) 282.977 ms
14 ae-82-82.csw3.Frankfurt1.Level3.net (4.69.140.26) 298.536 ms ae-62-62.csw1.Frankfurt1.Level3.net (4.69.140.18) 318.170 ms ae-72-72.csw2.Frankfurt1.Level3.net (4.69.140.22) 320.140 ms
15 ae-3-89.edge3.Frankfurt1.Level3.net (4.68.23.139) 324.597 ms ae-1-69.edge3.Frankfurt1.Level3.net (4.68.23.11) 336.071 ms ae-2-79.edge3.Frankfurt1.Level3.net (4.68.23.75) 345.448 ms
16 HETZNER-ONL.edge3.Frankfurt1.Level3.net (212.162.40.206) 357.574 ms 367.414 ms 377.180 ms
17 hos-bb1.juniper2.fs.hetzner.de (213.239.240.243) 392.776 ms 402.484 ms hos-bb1.juniper1.fs.hetzner.de (213.239.240.242) 411.119 ms
18 hos-tr2.ms-ex3k1.rz11.hetzner.de (213.239.236.83) 268.038 ms hos-tr4.ms-ex3k1.rz11.hetzner.de (213.239.236.115) 261.255 ms hos-tr1.ms-ex3k1.rz11.hetzner.de (213.239.236.67) 264.422 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


www.ps3za.co.za

derrick@Dex ~ $ traceroute www.ps3za.co.za
traceroute to www.ps3za.co.za (196.220.52.36), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.853 ms 2.627 ms 2.884 ms
2 dsl-185-74-1.dynamic.wa.co.za (41.185.74.1) 56.836 ms 66.358 ms 76.429 ms
3 vl105.cr.gw.cpt.za.wa.co.za (196.220.59.250) 109.682 ms 119.138 ms 129.202 ms
4 vl35.er.gw.cpt.za.wa.co.za (41.185.0.38) 146.898 ms 149.928 ms vl34.er.gw.cpt.za.wa.co.za (41.185.0.34) 160.136 ms
5 upstream.vl102.gw.cpt.za.wa.co.za (196.220.59.230) 168.693 ms upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 178.720 ms 188.621 ms
6 196.43.9.138 (196.43.9.138) 362.189 ms 240.866 ms 238.635 ms
7 gi4-8.ccr01.lon05.atlas.cogentco.com (149.6.2.193) 249.516 ms 258.915 ms 269.121 ms
8 te3-7.mpd01.lon01.atlas.cogentco.com (130.117.49.93) 282.448 ms te1-4.mpd01.lon01.atlas.cogentco.com (130.117.49.105) 290.011 ms 298.758 ms
9 te1-8.ccr01.lon01.atlas.cogentco.com (130.117.3.226) 348.074 ms te3-2.ccr01.lon01.atlas.cogentco.com (130.117.1.73) 346.110 ms *
10 te0-0-0-1.ccr21.jfk02.atlas.cogentco.com (130.117.0.46) 406.708 ms 416.393 ms 426.388 ms
11 te0-2-0-7.ccr21.dca01.atlas.cogentco.com (154.54.41.1) 443.965 ms te0-1-0-7.ccr21.dca01.atlas.cogentco.com (154.54.26.6) 454.098 ms te0-3-0-3.ccr21.dca01.atlas.cogentco.com (154.54.26.185) 461.496 ms
12 * te8-1.ccr01.atl01.atlas.cogentco.com (154.54.2.45) 341.456 ms te9-2.ccr01.atl01.atlas.cogentco.com (154.54.24.154) 335.085 ms
13 vl3561.na21.b019158-0.atl01.atlas.cogentco.com (38.20.37.58) 351.437 ms vl3861.na21.b019158-0.atl01.atlas.cogentco.com (38.112.38.14) 357.290 ms 365.824 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


www.gmail.com

derrick@Dex ~ $ traceroute www.gmail.com
traceroute to www.gmail.com (209.85.229.83), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.267 ms 1.534 ms 1.872 ms
2 dsl-185-74-1.dynamic.wa.co.za (41.185.74.1) 56.228 ms 65.768 ms 76.900 ms
3 vl105.cr.gw.cpt.za.wa.co.za (196.220.59.250) 108.872 ms 117.688 ms 127.488 ms
4 vl32.er.gw.cpt.za.wa.co.za (41.185.0.26) 138.517 ms 148.270 ms 158.145 ms
5 upstream.vl102.gw.cpt.za.wa.co.za (196.220.59.230) 169.387 ms upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 176.766 ms 188.012 ms
6 hkg-ip-dir-hongkong-pos-4-0-3.telkom-ipnet.co.za (196.43.18.214) 365.691 ms 246.646 ms 243.594 ms
7 72.14.196.129 (72.14.196.129) 399.253 ms 407.975 ms 417.809 ms
8 209.85.241.56 (209.85.241.56) 429.840 ms 209.85.241.58 (209.85.241.58) 436.448 ms 446.110 ms
9 72.14.239.68 (72.14.239.68) 461.711 ms 472.346 ms 482.428 ms
10 209.85.249.36 (209.85.249.36) 487.817 ms 498.763 ms 506.457 ms
11 209.85.248.221 (209.85.248.221) 521.973 ms 209.85.240.229 (209.85.240.229) 528.717 ms 535.016 ms
12 72.14.233.117 (72.14.233.117) 396.130 ms 395.719 ms 412.660 ms
13 216.239.46.214 (216.239.46.214) 405.153 ms 216.239.46.216 (216.239.46.216) 418.009 ms 216.239.46.214 (216.239.46.214) 461.064 ms
14 209.85.250.55 (209.85.250.55) 435.600 ms 443.474 ms 216.239.43.193 (216.239.43.193) 504.992 ms
15 72.14.232.134 (72.14.232.134) 473.884 ms 481.498 ms 491.563 ms
16 209.85.251.231 (209.85.251.231) 499.143 ms 508.017 ms 518.725 ms
17 209.85.243.73 (209.85.243.73) 533.276 ms * 209.85.243.85 (209.85.243.85) 556.245 ms
18 ww-in-f83.1e100.net (209.85.229.83) 401.369 ms 397.659 ms 399.044 ms



www.msn.com

derrick@Dex ~ $ traceroute www.msn.com
traceroute to www.msn.com (65.55.17.25), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.284 ms 1.898 ms 2.551 ms
2 dsl-185-74-1.dynamic.wa.co.za (41.185.74.1) 54.673 ms 64.434 ms 74.456 ms
3 vl108.cr.gw.cpt.za.wa.co.za (196.220.59.238) 107.407 ms 117.122 ms 125.908 ms
4 vl32.er.gw.cpt.za.wa.co.za (41.185.0.26) 138.174 ms 146.712 ms 156.826 ms
5 upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 165.423 ms 175.341 ms 186.509 ms
6 ams-ip-dir-globalc-gig-1-0-0.telkom-ipnet.co.za (196.43.9.218) 367.363 ms 401.260 ms 388.062 ms
7 214-228-228-213.packetexchange.net (213.228.228.214) 337.243 ms 359.237 ms 362.199 ms
8 ge-3-0-0-0.nyc-64cb-1b.ntwk.msn.net (207.46.47.216) 371.249 ms 382.128 ms 391.854 ms
9 ge-6-2-0-0.blu-64c-1b.ntwk.msn.net (207.46.46.142) 416.441 ms 421.682 ms 430.556 ms
10 ge-1-1-0-0.blu-64c-1a.ntwk.msn.net (207.46.43.110) 440.422 ms 450.366 ms 460.107 ms
11 ge-0-1-0-0.bl2-64c-1a.ntwk.msn.net (207.46.46.245) 470.322 ms 479.735 ms 490.765 ms
12 ge-0-0-0-0.bl2-64c-1b.ntwk.msn.net (207.46.43.85) 342.206 ms 339.860 ms 345.804 ms
13 ge-5-0-0-0.co2-64c-1b.ntwk.msn.net (207.46.40.106) 408.511 ms 407.658 ms 398.859 ms
14 ge-2-0-0-0.co1-64c-1b.ntwk.msn.net (207.46.43.178) 398.463 ms 406.780 ms 415.574 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
 
Someone from my ISP has told me because the 3rd Hop is above 100ms, that its a Telkom issue. Telkom have asked me to do a speedtest for them. I'll do it when I get home.
 
I get an average of about 53 ms to local sites on my 384K MWeb uncapped account.
 
D3x said:
Nobody?
Click to expand...

Speak to your ISP. All your trafic is being routed through CPT which means the closer you are to where the websites you're pinging the worse (Assuming you're in JHB as your location suggests). You're basically going JHB -> CPT -> ${WEBSITE} and that JHB -> CPT leg can add quite a few ms.

You're hitting your providers network on hop 2, so anything after that is in your ISP's hands.
 
134ms is too high for any line to a local site, you should be at 20-50ms.

Do a continuous ping to www.afrihost.co.za and post the results here. Want to check if there are fluctuations in your latency.
 
WA say their server is in CT, thats why everything must go via CT first? LOL

I have just been given WA DNS settings to try when I get home. I will just have to try it out & see. If it don't work, I might try someones MWEB account details & if the ping is better I will probably switch over. Thats if it's not Telkoms fault.
 
Blackhand said:
134ms is too high for any line to a local site, you should be at 20-50ms.

Do a continuous ping to www.afrihost.co.za and post the results here. Want to check if there are fluctuations in your latency.
Click to expand...

Cool, I will do that as soon as I get home today Blackhand, will post the results.

/me goes to Google to research how to do a continuous ping.. :D
 
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
 
Thanks Jax, I will try that too. I have also invited the WA MyBB members to comment as what I am hearing in here is not exactly what they are telling me over the phone.

:)
 
Last edited:
Blackhand said:
134ms is too high for any line to a local site, you should be at 20-50ms.

Do a continuous ping to www.afrihost.co.za and post the results here. Want to check if there are fluctuations in your latency.
Click to expand...

derrick@Dex ~ $ ping 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=116 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=2 ttl=50 time=102 ms
64 bytes from 196.38.88.28: icmp_seq=3 ttl=50 time=130 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=4 ttl=50 time=130 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=5 ttl=50 time=343 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=6 ttl=50 time=140 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=7 ttl=50 time=168 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=8 ttl=50 time=98.3 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=9 ttl=50 time=97.1 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=10 ttl=50 time=120 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=11 ttl=50 time=112 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=12 ttl=50 time=157 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=13 ttl=50 time=180 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=14 ttl=50 time=116 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=15 ttl=50 time=251 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=16 ttl=50 time=136 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=17 ttl=50 time=96.9 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=18 ttl=50 time=102 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=19 ttl=50 time=119 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=20 ttl=50 time=137 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=21 ttl=50 time=99.9 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=22 ttl=50 time=104 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=23 ttl=50 time=129 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=24 ttl=50 time=99.8 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=25 ttl=50 time=99.4 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=26 ttl=50 time=97.9 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=27 ttl=50 time=150 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=28 ttl=50 time=113 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=29 ttl=50 time=207 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=30 ttl=50 time=141 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=31 ttl=50 time=200 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=33 ttl=50 time=111 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=34 ttl=50 time=101 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=35 ttl=50 time=119 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=36 ttl=50 time=101 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=37 ttl=50 time=211 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=38 ttl=50 time=107 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=39 ttl=50 time=102 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=40 ttl=50 time=100 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=41 ttl=50 time=210 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=42 ttl=50 time=165 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=43 ttl=50 time=191 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=44 ttl=50 time=103 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=45 ttl=50 time=137 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=50 ttl=50 time=150 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=52 ttl=50 time=181 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=53 ttl=50 time=491 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=54 ttl=50 time=366 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=55 ttl=50 time=102 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=56 ttl=50 time=307 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=57 ttl=50 time=156 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=58 ttl=50 time=252 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=59 ttl=50 time=456 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=60 ttl=50 time=386 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=61 ttl=50 time=107 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=62 ttl=50 time=119 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=63 ttl=50 time=134 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=64 ttl=50 time=498 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=65 ttl=50 time=433 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=66 ttl=50 time=353 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=67 ttl=50 time=536 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=68 ttl=50 time=539 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=70 ttl=50 time=115 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=71 ttl=50 time=310 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=72 ttl=50 time=101 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=73 ttl=50 time=103 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=74 ttl=50 time=101 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=75 ttl=50 time=344 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=76 ttl=50 time=185 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=77 ttl=50 time=102 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=78 ttl=50 time=102 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=79 ttl=50 time=115 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=80 ttl=50 time=286 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=81 ttl=50 time=105 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=82 ttl=50 time=120 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=83 ttl=50 time=116 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=84 ttl=50 time=111 ms
64 bytes from www.afrihost.com (196.38.88.28): icmp_seq=85 ttl=50 time=107 ms


Bad news?
 
Mr.Jax said:
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
Click to expand...

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
 
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.
 
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.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X