Something smells verrry fishy here.
For the last three or four weeks, my ADSL speed (on a 1024k line) has been getting worse and worse - maxing out at around 300k down and 380k up.
Sentech speed test avg. 129k
Gamco speed test avg. 245k
dslreports speed test avg. 186k
and more similar
but, telskum's speed test avg. is 800k!!! wtf?
I'm not a big file downloader - I'm talking about normal day-to-day business activity - especially my server farm administration (in the US).
I've been on the phone to various techy-type persons at telskum - to no avail, as yet. The line has been tested: fine. The router has been tested: fine. The router settings have been tweaked and tested: fine. The network has been tested: fine.
Now, out of desperation, I go to one of my servers in the US (via PuTTy) and do a traceroute www.saix.co.za - in theory, the main telskum gateway to the world, and then also another one to my ADSL IP address - results?
traceroute to www.saix.net (196.25.1.200), 64 hops max, 40 byte packets
1 gw.dedicated.abac.net (216.55.133.1) 0.460 ms 0.420 ms 0.430 ms
2 gi4-15.cr1.sandiego.abac.net (66.226.66.9) 0.397 ms 0.410 ms 0.367 ms
3 gi2-0.er1.sandiego.abac.net (66.226.66.2) 0.354 ms 0.411 ms 0.339 ms
4 ge-5-1-142.hsa2.SanDiego1.Level3.net (64.158.218.1) 0.752 ms 0.690 ms 0.671 ms
5 so-6-1-0.mp1.SanDiego1.Level3.net (4.68.113.41) 1.107 ms 1.132 ms 1.104 ms
6 as-2-0.bbr1.LosAngeles1.Level3.net (64.159.1.30) 4.148 ms 4.186 ms 4.141 ms
7 ge-0-0-0-55.gar1.LosAngeles1.Level3.net (4.68.102.144) 4.222 4.349 4.208 ms
8 sprint-level3-oc192.LosAngeles1.Level3.net (64.152.193.74) 4.410 ms 4.337 ms 4.284 ms
9 sl-bb21-ana-13-0.sprintlink.net (144.232.20.66) 5.017 ms 4.951 ms 4.965 ms
10 sl-bb22-ana-15-0.sprintlink.net (144.232.1.174) 121.410 ms 42.151 ms 7.139 ms
11 sl-bb21-fw-6-0.sprintlink.net (144.232.20.130) 31.991 ms 31.978 ms 31.930 ms
12 sl-bb22-pen-13-0.sprintlink.net (144.232.9.30) 69.440 ms 69.354 ms 69.556 ms
13 sl-bb27-pen-9-0.sprintlink.net (144.232.16.54) 69.466 ms 70.325 ms 69.426 ms
14 sl-bb21-nyc-2-0.sprintlink.net (144.232.20.96) 70.709 ms 70.674 ms 70.892 ms
15 sl-bb23-nyc-3-0.sprintlink.net (144.232.7.109) 70.941 ms 71.563 ms 81.960 ms
16 sl-gw30-nyc-1-0.sprintlink.net (144.232.13.24) 70.734 ms 70.593 ms 70.708 ms
17 sl-telko-1-0.sprintlink.net (144.223.25.130) 70.897 ms 70.732 ms 70.788 ms
18 wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za (196.43.11.30) 300.574 ms 298.683 ms 298.617 ms
19 * * * Timed Out
20 * * * Timed Out
21 * * * Timed Out
22 * * * Timed Out
23 * * * Timed Out
Notice where the whole thing goes pear-shaped - at the *first* telskum hop.
then...
traceroute to 165.146.xxx.xxx (165.146.xxx.xxx), 64 hops max, 40 byte packets
1 xxx 0.411 ms
2 xxx 0.338 ms
3 xxx 0.404 ms
4 ge-5-1-142.hsa2.SanDiego1.Level3.net (64.158.218.1) 0.795 ms 0.860 ms 0.705 ms
5 so-6-1-0.mp1.SanDiego1.Level3.net (4.68.113.41) 1.117 ms 10.097 ms 1.143 ms
6 ae-0-0.bbr2.LosAngeles1.Level3.net (64.159.1.126) 4.114 ms 4.143 ms 4.113 ms
7 ge-0-0-0-55.gar1.LosAngeles1.Level3.net (4.68.102.144) 4.307 4.283 4.240 ms
8 sprint-level3-oc192.LosAngeles1.Level3.net (64.152.193.74) 5.492 ms 4.393 ms 4.329 ms
9 sl-bb21-ana-4-0.sprintlink.net (144.232.8.95) 5.061 ms 4.918 ms 4.977 ms
10 sl-bb22-ana-15-0.sprintlink.net (144.232.1.174) 5.230 ms 4.998 ms 5.232 ms
11 sl-bb21-fw-6-0.sprintlink.net (144.232.20.130) 31.792 ms 31.904 ms 31.870 ms
12 sl-bb22-pen-13-0.sprintlink.net (144.232.9.30) 69.353 ms 69.496 ms 69.785 ms
13 sl-bb27-pen-9-0.sprintlink.net (144.232.16.54) 69.419 ms 69.354 ms 69.366 ms
14 sl-bb21-nyc-2-0.sprintlink.net (144.232.20.96) 70.733 ms 70.852 ms 70.762 ms
15 sl-bb24-nyc-11-0.sprintlink.net (144.232.13.185) 71.082 ms 70.817 ms 71.017 ms
16 sl-gw30-nyc-0-0.sprintlink.net (144.232.13.20) 71.059 ms 71.155 ms 70.780 ms
17 sl-telko-1-0.sprintlink.net (144.223.25.130) 75.929 ms 70.909 ms 70.862 ms
18 ny-ip-dir-stacker-pos-5-1-0-2.telkom-ipnet.co.za (196.43.9.110) 71.303 ms 71.786 ms 71.100 ms
19 ny-ip-dir-globalc-ge-0-0-2-1.telkom-ipnet.co.za (196.43.9.189) 93.211 ms 95.244 ms *
20 hkg-ip-dir-hongkong-pos-7-4.telkom-ipnet.co.za (196.43.18.13) 381.920 ms 388.636 ms 381.238 ms
21 rrba-ip-lir-1-pos-4-0.telkom-ipnet.co.za (196.43.18.17) 544.950 ms 546.425 ms 548.434 ms
22 wbs-ip-er-1-ge-11-0-0.telkom-ipnet.co.za (196.43.11.150) 546.581 ms * 834.912 ms
23 wbs-ip-esr-2-gig-6-1-0-611.telkom-ipnet.co.za (196.43.23.9) 538.375 ms 540.116 ms 542.699 ms
24 * * * Timed Out
25 * * * Timed Out
26 * * * Timed Out
So, we're going to Hong Kong for a little data side trip. Why? Are the telskum routers correctly configured? Does anyone at telskum know? Does anyone at telskum care?
I'll report back if I find out.
For the last three or four weeks, my ADSL speed (on a 1024k line) has been getting worse and worse - maxing out at around 300k down and 380k up.
Sentech speed test avg. 129k
Gamco speed test avg. 245k
dslreports speed test avg. 186k
and more similar
but, telskum's speed test avg. is 800k!!! wtf?
I'm not a big file downloader - I'm talking about normal day-to-day business activity - especially my server farm administration (in the US).
I've been on the phone to various techy-type persons at telskum - to no avail, as yet. The line has been tested: fine. The router has been tested: fine. The router settings have been tweaked and tested: fine. The network has been tested: fine.
Now, out of desperation, I go to one of my servers in the US (via PuTTy) and do a traceroute www.saix.co.za - in theory, the main telskum gateway to the world, and then also another one to my ADSL IP address - results?
traceroute to www.saix.net (196.25.1.200), 64 hops max, 40 byte packets
1 gw.dedicated.abac.net (216.55.133.1) 0.460 ms 0.420 ms 0.430 ms
2 gi4-15.cr1.sandiego.abac.net (66.226.66.9) 0.397 ms 0.410 ms 0.367 ms
3 gi2-0.er1.sandiego.abac.net (66.226.66.2) 0.354 ms 0.411 ms 0.339 ms
4 ge-5-1-142.hsa2.SanDiego1.Level3.net (64.158.218.1) 0.752 ms 0.690 ms 0.671 ms
5 so-6-1-0.mp1.SanDiego1.Level3.net (4.68.113.41) 1.107 ms 1.132 ms 1.104 ms
6 as-2-0.bbr1.LosAngeles1.Level3.net (64.159.1.30) 4.148 ms 4.186 ms 4.141 ms
7 ge-0-0-0-55.gar1.LosAngeles1.Level3.net (4.68.102.144) 4.222 4.349 4.208 ms
8 sprint-level3-oc192.LosAngeles1.Level3.net (64.152.193.74) 4.410 ms 4.337 ms 4.284 ms
9 sl-bb21-ana-13-0.sprintlink.net (144.232.20.66) 5.017 ms 4.951 ms 4.965 ms
10 sl-bb22-ana-15-0.sprintlink.net (144.232.1.174) 121.410 ms 42.151 ms 7.139 ms
11 sl-bb21-fw-6-0.sprintlink.net (144.232.20.130) 31.991 ms 31.978 ms 31.930 ms
12 sl-bb22-pen-13-0.sprintlink.net (144.232.9.30) 69.440 ms 69.354 ms 69.556 ms
13 sl-bb27-pen-9-0.sprintlink.net (144.232.16.54) 69.466 ms 70.325 ms 69.426 ms
14 sl-bb21-nyc-2-0.sprintlink.net (144.232.20.96) 70.709 ms 70.674 ms 70.892 ms
15 sl-bb23-nyc-3-0.sprintlink.net (144.232.7.109) 70.941 ms 71.563 ms 81.960 ms
16 sl-gw30-nyc-1-0.sprintlink.net (144.232.13.24) 70.734 ms 70.593 ms 70.708 ms
17 sl-telko-1-0.sprintlink.net (144.223.25.130) 70.897 ms 70.732 ms 70.788 ms
18 wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za (196.43.11.30) 300.574 ms 298.683 ms 298.617 ms
19 * * * Timed Out
20 * * * Timed Out
21 * * * Timed Out
22 * * * Timed Out
23 * * * Timed Out
Notice where the whole thing goes pear-shaped - at the *first* telskum hop.
then...
traceroute to 165.146.xxx.xxx (165.146.xxx.xxx), 64 hops max, 40 byte packets
1 xxx 0.411 ms
2 xxx 0.338 ms
3 xxx 0.404 ms
4 ge-5-1-142.hsa2.SanDiego1.Level3.net (64.158.218.1) 0.795 ms 0.860 ms 0.705 ms
5 so-6-1-0.mp1.SanDiego1.Level3.net (4.68.113.41) 1.117 ms 10.097 ms 1.143 ms
6 ae-0-0.bbr2.LosAngeles1.Level3.net (64.159.1.126) 4.114 ms 4.143 ms 4.113 ms
7 ge-0-0-0-55.gar1.LosAngeles1.Level3.net (4.68.102.144) 4.307 4.283 4.240 ms
8 sprint-level3-oc192.LosAngeles1.Level3.net (64.152.193.74) 5.492 ms 4.393 ms 4.329 ms
9 sl-bb21-ana-4-0.sprintlink.net (144.232.8.95) 5.061 ms 4.918 ms 4.977 ms
10 sl-bb22-ana-15-0.sprintlink.net (144.232.1.174) 5.230 ms 4.998 ms 5.232 ms
11 sl-bb21-fw-6-0.sprintlink.net (144.232.20.130) 31.792 ms 31.904 ms 31.870 ms
12 sl-bb22-pen-13-0.sprintlink.net (144.232.9.30) 69.353 ms 69.496 ms 69.785 ms
13 sl-bb27-pen-9-0.sprintlink.net (144.232.16.54) 69.419 ms 69.354 ms 69.366 ms
14 sl-bb21-nyc-2-0.sprintlink.net (144.232.20.96) 70.733 ms 70.852 ms 70.762 ms
15 sl-bb24-nyc-11-0.sprintlink.net (144.232.13.185) 71.082 ms 70.817 ms 71.017 ms
16 sl-gw30-nyc-0-0.sprintlink.net (144.232.13.20) 71.059 ms 71.155 ms 70.780 ms
17 sl-telko-1-0.sprintlink.net (144.223.25.130) 75.929 ms 70.909 ms 70.862 ms
18 ny-ip-dir-stacker-pos-5-1-0-2.telkom-ipnet.co.za (196.43.9.110) 71.303 ms 71.786 ms 71.100 ms
19 ny-ip-dir-globalc-ge-0-0-2-1.telkom-ipnet.co.za (196.43.9.189) 93.211 ms 95.244 ms *
20 hkg-ip-dir-hongkong-pos-7-4.telkom-ipnet.co.za (196.43.18.13) 381.920 ms 388.636 ms 381.238 ms
21 rrba-ip-lir-1-pos-4-0.telkom-ipnet.co.za (196.43.18.17) 544.950 ms 546.425 ms 548.434 ms
22 wbs-ip-er-1-ge-11-0-0.telkom-ipnet.co.za (196.43.11.150) 546.581 ms * 834.912 ms
23 wbs-ip-esr-2-gig-6-1-0-611.telkom-ipnet.co.za (196.43.23.9) 538.375 ms 540.116 ms 542.699 ms
24 * * * Timed Out
25 * * * Timed Out
26 * * * Timed Out
So, we're going to Hong Kong for a little data side trip. Why? Are the telskum routers correctly configured? Does anyone at telskum know? Does anyone at telskum care?
I'll report back if I find out.