So, at these ridiculously spoiled times I have the unique opportunity to observe my fast connection with another fast connection, from my home! This is interesting, now I can hack myself for a change ;-) What's also cool, I can trace myself from both sides: from Cable to ADSL : # IP address Host name Round trip time 1 62.108.18.1 h0rtr3.a2000.nl 2 ms 2 62.108.0.33 h0rtr2-h0rtr3.a2000.nl 5 ms 3 62.108.0.1 h0rtr1-h0rtr2.a2000.nl 4 ms 4 62.108.0.18 amsixrtr1-h0rtr1.a2000.nl 9 ms 5 193.148.15.48 ams-ix.xs4all.net 5 ms 6 194.109.5.13 ge-0-3-0.xr1.pbw.xs4all.net 9 ms 7 194.109.5.138 mxstream3.pbw.xs4all.net 11 ms 8 213.84.27.81 jult.net 36 ms from ADSL to Cable : # IP address Host name Round trip time 1 195.190.241.33 Unavailable 14 ms 2 194.109.5.133 ge-1-2.0.52.xr1.pbw.xs4all.net 30 ms 3 194.109.5.14 ge-0-3-0.xr1.sara.xs4all.net 20 ms 4 193.148.15.53 ams-ix.a2000.nl 29 ms 5 62.108.0.17 h0rtr1-amsixrtr1.a2000.nl 29 ms 6 62.108.0.2 h0rtr2-h0rtr1.a2000.nl 38 ms 7 62.108.0.34 h0rtr3-h0rtr2.a2000.nl 23 ms 8 24.132.133.42 node1852a.a2000.nl 33 ms Much of the ADSL-delay is caused by the KPN mxstream and Alcatel protocol conversion stuff at the start of the line. (Hope it will change when they throw away the dashboard...) Also the buffer-use in the Alcatel could cause part of this 'delay' (14 ms isn't really a delay, in my opinion) Contrary to what the shorter ping-times on cable could suggest, the ADSL connection to the world somehow appears faster though. This example possibly proves why: Cable to iets.org, taking 22 steps: # IP address Host name Round trip time 1 62.108.18.1 h0rtr3.a2000.nl 10 ms 2 62.108.0.33 h0rtr2-h0rtr3.a2000.nl 2 ms 3 62.108.0.85 gig14-0.am00rt04.brain.upc.nl 8 ms 4 212.142.32.34 srp8-0.am00rt02.brain.upc.nl 9 ms 5 212.142.32.44 srp0-0.am00rt06.brain.upc.nl 8 ms 6 213.46.161.53 nl-ams-rd-01-pos-4-0.chellonetwork.com19 ms 7 213.46.160.13 nl-ams-rc-01-pos-0-1.chellonetwork.com13 ms 8 213.46.160.10 uk-lon-rc-02-pos-0-0.chellonetwork.com18 ms 9 213.46.160.45 uk-lon-rc-01-pos-1-0.chellonetwork.com16 ms 10 213.46.160.54 uk-lon-rd-01-pos-1-0.chellonetwork.com29 ms 11 213.46.174.6 uk-lon-ri-01-pos-5-0-0.chellonetwork.co11 ms 12 195.66.225.76 Unavailable 13 ms 13 216.200.127.69 iad1-lhr1-stm4-2.iad1.above.net 86 ms 14 208.185.0.138 core4-core1-oc48.iad1.above.net 89 ms 15 208.184.233.125 dca2-iad1-oc192.dca2.above.net 86 ms 16 208.184.233.133 sjc2-dca2-oc48.sjc2.above.net 198 ms 17 208.185.175.162 pao1-sjc2-oc48-2.pao1.above.net 173 ms 18 207.126.96.78 criticalpath-abovenet.criticalpath.net173 ms 19 209.228.0.73 fa1-0.edge1.pao.cp.net 176 ms 20 209.228.0.129 s2-0.core2.corp.cp.net 173 ms 21 209.228.0.18 fa0-0.core1.corp.cp.net 179 ms 22 204.107.140.52 iets.org 176 ms ADSL to iets.org, taking only 14(!) steps: # IP address Host name Round trip time 1 195.190.241.33 Unavailable 12 ms 2 194.109.5.133 ge-1-2.0.52.xr1.pbw.xs4all.net 31 ms 3 194.109.5.14 ge-0-3-0.xr1.sara.xs4all.net 35 ms 4 193.148.15.122 amsix-fe.ams.above.net 28 ms 5 208.184.231.37 core1-ams1-stm1-2.ams3.above.net 36 ms 6 208.184.231.25 lga1-ams3-stm4.lga1.above.net 107 ms 7 216.200.127.66 sea1-lga1-oc48.sea1.above.net 187 ms 8 208.184.102.177 sjc2-sea1-oc48-2.sjc2.above.net 190 ms 9 208.185.175.162 pao1-sjc2-oc48-2.pao1.above.net 192 ms 10 207.126.96.78 criticalpath-abovenet.criticalpath.net190 ms 11 209.228.0.73 fa1-0.edge1.pao.cp.net 192 ms 12 209.228.0.129 s2-0.core2.corp.cp.net 190 ms 13 209.228.0.18 fa0-0.core1.corp.cp.net 190 ms 14 204.107.140.52 iets.org 190 ms Be aware of THIS when you use cable... Ciao Julius Thyssen |