Here's my latest trace, showing the packet loss situation today through 'lee-bb-a-so-120-0.inet.ntl.com':
Target Name: N/A
IP: 87.237.38.200
Date/Time: 21/04/2007 12:42:03 to 21/04/2007 13:50:05
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 1634 1 0.1 0 32 0 [192.168.0.1]
2 1634 4 0.2 6 66 7 [10.227.144.1]
3 1634 1 0.1 6 41 7 leic-t2cam1-a-ge82.inet.ntl.com [82.3.35.185]
4 1634 2 0.1 6 59 7 cpc3-ches1-3-1-cust225.lutn.cable.ntl.com [82.3.32.225]
5 1633 259 15.9 9 42 10 lee-bb-a-so-120-0.inet.ntl.com [213.105.172.17]
6 1634 4 0.2 14 55 16 bre-bb-b-so-200-0.inet.ntl.com [213.105.175.26]
7 1633 4 0.2 14 50 16 telc-ic-1-so-700-0.inet.ntl.com [62.253.185.74]
8 1633 3 0.2 16 191 18 tge5-4.fr1.lon.llnw.net [195.66.224.133]
9 1633 4 0.2 15 240 21 ccp.ve201.fr3.lon.llnw.net [87.248.208.150]
10 1633 5 0.3 15 41 16 [87.237.38.199]
11 1633 5 0.3 15 39 16 [87.237.38.200]
Oh look, it's running at about 16% packet loss again, now there's a surprise (not).
I am beginning to wonder if this node has been set to drop a percentage of its received traffic deliberately to ease network congestion; the numbers are just so damn similar ALL the time.
