Tracert (2nd hop)

Thanks Sinbad, I figured you would point me to Google's DNS and have switched over to them just under an hour ago.

Once again like when I get port resets and port recreates done it was working beautifully for the first 10-15 minutes and has now slowed down again.

I swear I am losing my mind :sick:

If I am supposedly being prioritised on protocols like HTTP and HTTPS with my current ADSL package why do you think browsing web sites and working on my wordpress web sites so utterly frustratingly slow?

Here's some more traces:

traceroute to facebook.com (173.252.120.68), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.306 ms 1.824 ms 1.770 ms
2 * * *
3 cdsl2-rba-vl2766-ipc.ip.isnet.net (196.38.73.86) 86.063 ms 30.674 ms 26.405 ms
4 196.38.73.85 (196.38.73.85) 32.271 ms 47.493 ms 31.529 ms
5 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 37.178 ms 35.817 ms 25.546 ms
6 core2-pkl-t0-7-0-0.ip.isnet.net (168.209.1.163) 37.725 ms 41.286 ms 32.104 ms
7 core2b-dock-pos-0-3-4-0.ip.isnet.net (168.209.201.65) 193.632 ms 306.600 ms 204.563 ms
8 195.66.237.69 (195.66.237.69) 204.564 ms 203.387 ms 203.583 ms
9 ae1.bb02.lhr2.tfbnw.net (31.13.30.198) 204.595 ms 204.119 ms 204.413 ms
10 be30.bb02.iad3.tfbnw.net (31.13.26.186) 283.998 ms 284.557 ms 286.813 ms
11 be37.bb02.frc3.tfbnw.net (31.13.26.56) 370.590 ms
be5.bb02.frc3.tfbnw.net (74.119.78.86) 306.853 ms
ae3.bb05.frc3.tfbnw.net (31.13.24.204) 302.519 ms
12 ae4.dr01.frc3.tfbnw.net (31.13.30.37) 289.380 ms
ae1.dr02.frc1.tfbnw.net (31.13.28.139) 307.418 ms
ae4.dr03.frc3.tfbnw.net (31.13.26.43) 287.235 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 edge-star-mini-shv-12-frc3.facebook.com (173.252.120.68) 323.264 ms 388.566 ms 307.112 ms
 
Have you checked that you're not somehow maximising your upload on your line?
 
Some F-Wit at WebAfrica told me that timing out on the second hop is perfectly normal, no it's NOT !!!
What BS causes this ?? This explains why my premium gold capped "unthrottled" and "unshaped" line is so **** !!!

traceroute to cnn.com (157.166.226.25), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 3.032 ms 2.671 ms 2.424 ms
2 * * *
3 cdsl2-rba-vl2563-ipc.ip.isnet.net (196.38.73.214) 120.733 ms 27.357 ms 26.128 ms
4 cdsl2-rba-vl2563.ip.isnet.net (196.38.73.213) 40.570 ms 32.312 ms 25.660 ms
5 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 28.224 ms 27.432 ms 26.322 ms
6 core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 29.879 ms 37.535 ms 26.902 ms
7 core1b-dock-pos-0-3-4-0.ip.isnet.net (168.209.201.61) 205.023 ms 205.904 ms

Haha. What a fail. It's been normal for some time.
 
Thanks Ho3n3r ..... I am old school networking where timeouts were problems ..... things have changed and I admitted I was wrong
 
What happens if you switch to a wired connection?

It looks like you are uploading more data than downloading (with errors) and if you are saturating the uplink things are gonna get sluggish.

Looking at your line rate you also have ASSIA DSM enable on your line which adds to latency.
 
Last edited:
What happens if you switch to a wired connection?

It looks like you are uploading more data than downloading (with errors) and if you are saturating the uplink things are gonna get sluggish.

Looking at your line rate you also have ASSIA DSM enable on your line which adds to latency.

Thanks for the reply ponder, what on earth is ASSIA DSM and how do I disable it on the D-Link, have looked around in the settings but can't seem to locate that one.

My desk is too far from the router but I can try later today with a wire connection to rule that out for certain.

Is there any local wireless settings I should not have on that may be causing problems ?? (see attached screen shots)


Screen Shot 2016-05-23 at 12.06.47 PM.jpg
Screen Shot 2016-05-23 at 12.07.40 PM.jpg
Screen Shot 2016-05-23 at 12.08.07 PM.jpg
 
Thanks for the reply ponder, what on earth is ASSIA DSM and how do I disable it on the D-Link, have looked around in the settings but can't seem to locate that one.

My desk is too far from the router but I can try later today with a wire connection to rule that out for certain.

Is there any local wireless settings I should not have on that may be causing problems ?? (see attached screen shots)


View attachment 363724
View attachment 363726
View attachment 363728

You can't disable it, OpenServe/Telkom can, but they won't. Or maybe it's not even possible any more.
 
You can't disable it, OpenServe/Telkom can, but they won't. Or maybe it's not even possible any more.

Oh great ..... now what ? My line is once again so utterly slow today it is unbearable.

Is there anything else there on my local settings that could be disabled that could perhaps help. I cannot understand what is causing an upload of more data than what I download, I find that highly impossible.

I'm stumped
 
Thanks Sinbad, I figured you would point me to Google's DNS and have switched over to them just under an hour ago.

Once again like when I get port resets and port recreates done it was working beautifully for the first 10-15 minutes and has now slowed down again.

I swear I am losing my mind :sick:

If I am supposedly being prioritised on protocols like HTTP and HTTPS with my current ADSL package why do you think browsing web sites and working on my wordpress web sites so utterly frustratingly slow?

Here's some more traces:

Code:
traceroute to facebook.com (173.252.120.68), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  2.306 ms  1.824 ms  1.770 ms
 2  * * *
 3  cdsl2-rba-vl2766-ipc.ip.isnet.net (196.38.73.86)  86.063 ms  30.674 ms  26.405 ms
 4  196.38.73.85 (196.38.73.85)  32.271 ms  47.493 ms  31.529 ms
 5  cdsl2-rba-vl150.ip.isnet.net (196.38.73.9)  37.178 ms  35.817 ms  25.546 ms
 6  core2-pkl-t0-7-0-0.ip.isnet.net (168.209.1.163)  37.725 ms  41.286 ms  32.104 ms
 7  core2b-dock-pos-0-3-4-0.ip.isnet.net (168.209.201.65)  193.632 ms  306.600 ms  204.563 ms
 8  195.66.237.69 (195.66.237.69)  204.564 ms  203.387 ms  203.583 ms
 9  ae1.bb02.lhr2.tfbnw.net (31.13.30.198)  204.595 ms  204.119 ms  204.413 ms
10  be30.bb02.iad3.tfbnw.net (31.13.26.186)  283.998 ms  284.557 ms  286.813 ms
11  be37.bb02.frc3.tfbnw.net (31.13.26.56)  370.590 ms
    be5.bb02.frc3.tfbnw.net (74.119.78.86)  306.853 ms
    ae3.bb05.frc3.tfbnw.net (31.13.24.204)  302.519 ms
12  ae4.dr01.frc3.tfbnw.net (31.13.30.37)  289.380 ms
    ae1.dr02.frc1.tfbnw.net (31.13.28.139)  307.418 ms
    ae4.dr03.frc3.tfbnw.net (31.13.26.43)  287.235 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  edge-star-mini-shv-12-frc3.facebook.com (173.252.120.68)  323.264 ms  388.566 ms  307.112 ms

How about posting trace route results as I have done? It is easier to read then .... and why all the decimal places?
 
You can't disable it, OpenServe/Telkom can, but they won't. Or maybe it's not even possible any more.

You can but it's only temporary.

Call 10210, switch your router off and ask them to change you over to the 1Mb/s profile, once done turn router on and check to see that it's syncing at 1Mb/s, turn it off again and ask them to put you back onto your normal profile ie 2Mb/s and once done turn your router on again and check the sync. You should now see it syncing at 2Mb/s and not 2554/508 etc, you will also notice an improvement in your SNR & Attenuation.
 
You can but it's only temporary.

Call 10210, switch your router off and ask them to change you over to the 1Mb/s profile, once done turn router on and check to see that it's syncing at 1Mb/s, turn it off again and ask them to put you back onto your normal profile ie 2Mb/s and once done turn your router on again and check the sync. You should now see it syncing at 2Mb/s and not 2554/508 etc, you will also notice an improvement in your SNR & Attenuation.

I will certainly try that ponder, thanks a mil. Let me see.
 
Eliminate Wi-Fi with a direct cable connection to the router .....

Then see what the differences are.

How many other wi-fi routers are operating in your area? How many other networks can you see?

If you have a smart phone (or a tablet )wi fi enabled, try and download this simple app which will show you what is going on around you. It may shed some light on what could be done to ensure your router defaults to a more quiet "channel"

The Tool is available in the Google Play-store and it's called "Wifi Analyzer" by "farproc

A friend of mine uses a D-link ADSL router and this is what he found with the above tool, before and after changing the channel used by his router ...

Before adjustment of the channel used by the D link router
Channel-6.jpg
After adjustment
Channel-8.jpg

where to do this setting ...
Router Settings.jpg
 
Last edited:
Thanks daniellgr, have a bad habit of decimal places in sentences :wtf:

Here's a few traceroutes to common sites done right now. (The only one that completed end to end was to Facebook but that was not the case this morning. Regardless Facebook is still slow and the 3 other sites all listed below)

traceroute to star-mini.c10r.facebook.com (31.13.77.36), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 7.937 ms 2.102 ms 2.027 ms
2 * * *
3 cdsl1-rba-vl2360-ipc.ip.isnet.net (196.38.73.134) 33.045 ms 62.530 ms 179.149 ms
4 cdsl1-rba-vl2360.ip.isnet.net (196.38.73.133) 65.686 ms 94.257 ms 49.108 ms
5 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 27.397 ms 27.733 ms 55.416 ms
6 core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 45.242 ms 78.745 ms 76.070 ms
7 168.209.201.89 (168.209.201.89) 204.860 ms 208.134 ms 230.720 ms
8 ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76) 207.372 ms 227.392 ms 194.936 ms
9 ae10.mpr2.lhr2.uk.zip.zayo.com (64.125.31.194) 215.133 ms 200.876 ms 200.973 ms
10 ae27.cs1.lhr11.uk.eth.zayo.com (64.125.30.236) 360.841 ms 328.378 ms 327.442 ms
11 ae5.cs1.lga5.us.eth.zayo.com (64.125.29.126) 349.926 ms 502.354 ms 390.636 ms
12 ae3.cs1.ord2.us.eth.zayo.com (64.125.29.209) 424.129 ms 409.882 ms 408.724 ms
13 ae5.cs1.den5.us.eth.zayo.com (64.125.29.19) 409.481 ms 333.719 ms 420.400 ms
14 ae6.cs1.sjc2.us.eth.zayo.com (64.125.31.219) 485.002 ms 511.464 ms 352.260 ms
15 ae27.cr1.sjc2.us.zip.zayo.com (64.125.30.231) 471.820 ms 389.038 ms 351.091 ms
16 ae16.mpr3.sjc7.us.zip.zayo.com (64.125.31.13) 409.816 ms 416.803 ms 387.362 ms
17 128.177.170.162.ipyx-100687-900-zyo.zip.zayo.com (128.177.170.162) 400.656 ms * *
18 po101.psw01c.sjc2.tfbnw.net (74.119.77.163) 441.225 ms
po101.psw01a.sjc2.tfbnw.net (31.13.31.15) 328.719 ms
po101.psw01d.sjc2.tfbnw.net (74.119.77.175) 400.816 ms
19 msw1an.01.sjc2.tfbnw.net (204.15.21.30) 336.795 ms
msw1ag.01.sjc2.tfbnw.net (74.119.79.148) 394.023 ms
msw1ah.01.sjc2.tfbnw.net (74.119.79.147) 424.168 ms
20 edge-star-mini-shv-01-sjc2.facebook.com (31.13.77.36) 457.826 ms 408.781 ms 512.296 ms



traceroute to twitter.com (199.59.149.230), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.926 ms 2.637 ms 3.112 ms
2 * * *
3 cdsl2-rba-vl2766-ipc.ip.isnet.net (196.38.73.86) 251.656 ms 49.232 ms 129.249 ms
4 196.38.73.85 (196.38.73.85) 96.602 ms 126.541 ms 95.345 ms
5 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 85.236 ms 67.306 ms 29.440 ms
6 core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 27.384 ms 48.861 ms 28.411 ms
7 core1a-hkt-gi0-3-91.ip.isnet.net (168.209.0.78) 212.500 ms 372.853 ms 205.323 ms
8 core2b-hkt-gi0-1.ip.isnet.net (168.209.4.6) 310.130 ms 306.783 ms 203.497 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
^C



traceroute to www.photoshelter.com (69.22.188.80), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.578 ms 2.008 ms 3.024 ms
2 * * *
3 cdsl2-rba-vl2563-ipc.ip.isnet.net (196.38.73.214) 102.249 ms 26.997 ms 33.632 ms
4 cdsl2-rba-vl2563.ip.isnet.net (196.38.73.213) 27.508 ms 24.245 ms 27.757 ms
5 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 26.898 ms 26.539 ms 25.029 ms
6 core2b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.63) 38.336 ms 95.534 ms 47.386 ms
7 core2b-dock-pos-0-3-4-0.ip.isnet.net (168.209.201.65) 192.434 ms 196.547 ms 190.943 ms
8 xe-0-4-0-6.r02.londen03.uk.bb.gin.ntt.net (83.231.235.221) 196.636 ms 315.083 ms 249.638 ms
9 ae-1.r00.londen10.uk.bb.gin.ntt.net (129.250.3.31) 236.073 ms 233.380 ms 200.920 ms
10 ae15.lon11.ip4.gtt.net (141.136.96.181) 210.346 ms 228.776 ms 207.475 ms
11 xe-2-1-3.nyc62.ip4.gtt.net (89.149.131.106) 286.179 ms 263.854 ms 259.400 ms
12 as62804.ge-0-0-2.ar1.nyc3.us.as4436.gtt.net (69.31.94.66) 323.434 ms 345.797 ms 261.996 ms
13 63.141.214.43 (63.141.214.43) 272.541 ms 271.049 ms 267.849 ms
14 * * *
15 * * *



traceroute: Warning: www.wordpress.com has multiple addresses; using 192.0.78.13
traceroute to lb.wordpress.com (192.0.78.13), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.291 ms 3.139 ms 1.792 ms
2 * * *
3 cdsl1-rba-vl2253-ipc.ip.isnet.net (196.38.73.182) 111.865 ms 182.386 ms 96.637 ms
4 cdsl1-rba-vl2253.ip.isnet.net (196.38.73.181) 59.028 ms 84.172 ms 25.568 ms
5 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 28.256 ms 53.672 ms 41.195 ms
6 core2b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.63) 53.631 ms 84.886 ms 118.949 ms
7 core2b-dock-pos-0-3-4-0.ip.isnet.net (168.209.201.65) 315.991 ms 308.141 ms *
8 * core1b-dock-ten-0-3-0-0sub2.ip.isnet.net (168.209.246.1) 265.863 ms 273.139 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
^C
 
Thanks daniellgr, have a bad habit of decimal places in sentences :wtf:

Here's a few traceroutes to common sites done right now. (The only one that completed end to end was to Facebook but that was not the case this morning. Regardless Facebook is still slow and the 3 other sites all listed below)

traceroute to star-mini.c10r.facebook.com (31.13.77.36), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 7.937 ms 2.102 ms 2.027 ms
2 * * *
3 cdsl1-rba-vl2360-ipc.ip.isnet.net (196.38.73.134) 33.045 ms 62.530 ms 179.149 ms
4 cdsl1-rba-vl2360.ip.isnet.net (196.38.73.133) 65.686 ms 94.257 ms 49.108 ms
5 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 27.397 ms 27.733 ms 55.416 ms
6 core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 45.242 ms 78.745 ms 76.070 ms
7 168.209.201.89 (168.209.201.89) 204.860 ms 208.134 ms 230.720 ms
8 ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76) 207.372 ms 227.392 ms 194.936 ms
9 ae10.mpr2.lhr2.uk.zip.zayo.com (64.125.31.194) 215.133 ms 200.876 ms 200.973 ms
10 ae27.cs1.lhr11.uk.eth.zayo.com (64.125.30.236) 360.841 ms 328.378 ms 327.442 ms
11 ae5.cs1.lga5.us.eth.zayo.com (64.125.29.126) 349.926 ms 502.354 ms 390.636 ms
12 ae3.cs1.ord2.us.eth.zayo.com (64.125.29.209) 424.129 ms 409.882 ms 408.724 ms
13 ae5.cs1.den5.us.eth.zayo.com (64.125.29.19) 409.481 ms 333.719 ms 420.400 ms
14 ae6.cs1.sjc2.us.eth.zayo.com (64.125.31.219) 485.002 ms 511.464 ms 352.260 ms
15 ae27.cr1.sjc2.us.zip.zayo.com (64.125.30.231) 471.820 ms 389.038 ms 351.091 ms
16 ae16.mpr3.sjc7.us.zip.zayo.com (64.125.31.13) 409.816 ms 416.803 ms 387.362 ms
17 128.177.170.162.ipyx-100687-900-zyo.zip.zayo.com (128.177.170.162) 400.656 ms * *
18 po101.psw01c.sjc2.tfbnw.net (74.119.77.163) 441.225 ms
po101.psw01a.sjc2.tfbnw.net (31.13.31.15) 328.719 ms
po101.psw01d.sjc2.tfbnw.net (74.119.77.175) 400.816 ms
19 msw1an.01.sjc2.tfbnw.net (204.15.21.30) 336.795 ms
msw1ag.01.sjc2.tfbnw.net (74.119.79.148) 394.023 ms
msw1ah.01.sjc2.tfbnw.net (74.119.79.147) 424.168 ms
20 edge-star-mini-shv-01-sjc2.facebook.com (31.13.77.36) 457.826 ms 408.781 ms 512.296 ms



traceroute to twitter.com (199.59.149.230), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.926 ms 2.637 ms 3.112 ms
2 * * *
3 cdsl2-rba-vl2766-ipc.ip.isnet.net (196.38.73.86) 251.656 ms 49.232 ms 129.249 ms
4 196.38.73.85 (196.38.73.85) 96.602 ms 126.541 ms 95.345 ms
5 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 85.236 ms 67.306 ms 29.440 ms
6 core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 27.384 ms 48.861 ms 28.411 ms
7 core1a-hkt-gi0-3-91.ip.isnet.net (168.209.0.78) 212.500 ms 372.853 ms 205.323 ms
8 core2b-hkt-gi0-1.ip.isnet.net (168.209.4.6) 310.130 ms 306.783 ms 203.497 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
^C



traceroute to www.photoshelter.com (69.22.188.80), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.578 ms 2.008 ms 3.024 ms
2 * * *
3 cdsl2-rba-vl2563-ipc.ip.isnet.net (196.38.73.214) 102.249 ms 26.997 ms 33.632 ms
4 cdsl2-rba-vl2563.ip.isnet.net (196.38.73.213) 27.508 ms 24.245 ms 27.757 ms
5 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 26.898 ms 26.539 ms 25.029 ms
6 core2b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.63) 38.336 ms 95.534 ms 47.386 ms
7 core2b-dock-pos-0-3-4-0.ip.isnet.net (168.209.201.65) 192.434 ms 196.547 ms 190.943 ms
8 xe-0-4-0-6.r02.londen03.uk.bb.gin.ntt.net (83.231.235.221) 196.636 ms 315.083 ms 249.638 ms
9 ae-1.r00.londen10.uk.bb.gin.ntt.net (129.250.3.31) 236.073 ms 233.380 ms 200.920 ms
10 ae15.lon11.ip4.gtt.net (141.136.96.181) 210.346 ms 228.776 ms 207.475 ms
11 xe-2-1-3.nyc62.ip4.gtt.net (89.149.131.106) 286.179 ms 263.854 ms 259.400 ms
12 as62804.ge-0-0-2.ar1.nyc3.us.as4436.gtt.net (69.31.94.66) 323.434 ms 345.797 ms 261.996 ms
13 63.141.214.43 (63.141.214.43) 272.541 ms 271.049 ms 267.849 ms
14 * * *
15 * * *



traceroute: Warning: www.wordpress.com has multiple addresses; using 192.0.78.13
traceroute to lb.wordpress.com (192.0.78.13), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.291 ms 3.139 ms 1.792 ms
2 * * *
3 cdsl1-rba-vl2253-ipc.ip.isnet.net (196.38.73.182) 111.865 ms 182.386 ms 96.637 ms
4 cdsl1-rba-vl2253.ip.isnet.net (196.38.73.181) 59.028 ms 84.172 ms 25.568 ms
5 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 28.256 ms 53.672 ms 41.195 ms
6 core2b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.63) 53.631 ms 84.886 ms 118.949 ms
7 core2b-dock-pos-0-3-4-0.ip.isnet.net (168.209.201.65) 315.991 ms 308.141 ms *
8 * core1b-dock-ten-0-3-0-0sub2.ip.isnet.net (168.209.246.1) 265.863 ms 273.139 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
^C

I think you have exchange congestion. Either that, or you are sending loads of data and overwhelming your upstream channel
 
I think you have exchange congestion. Either that, or you are sending loads of data and overwhelming your upstream channel

Thanks sinbad, going to phone 10210 and try getting them disable and re-enable the ASSIA profile as ponder has suggested. I simply cannot find what is uploading data, dropbox, google drive and icloud drive all turned off, I only turn them on manually especially these days.
 
Top
Sign up to the MyBroadband newsletter
X