 | Let's try a monospace font for those test results...
Target Name: IP: Date/Time: 2/2/2012 4:10:32 PM to 2/2/2012 4:12:44 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP] 2 260 1 0.4 14 84 22 rd1no-ge5-0-0-2.cg.shawcable.net [64.59.140.227] 3 260 19 7.3 13 72 21 rc2so-tge0-3-5-0.cg.shawcable.net [66.163.71.162] 4 260 24 9.2 28 108 34 rc2wh-pos0-0-2-0.vc.shawcable.net [66.163.77.197] 5 253 202 79.8 27 103 34 gige-pix-s4-973.cipherkey.com [206.223.127.18] 6 260 24 9.2 35 404 85 xx208110096004.cipherkey.com [208.110.96.4]
|
 stolen join:2004-04-12 Calgary, AB kudos:1 | To my eyes, I see packetloss starting *within* shaw's network. A minimal amount at hop #2, and increasing from there. There's a lot at hop #5, but since the overall packetloss at hop #6 is back to about the same as hop #4, I don't think that #5 is the issue.
For what it's worth, I'm not seeing the packetloss from here, but I'm taking a different route out of shaw land (and not during a busy time).
My traceroute [v0.80]
beast (0.0.0.0) Wed Feb 8 08:29:10 2012
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.0.1 0.0% 70 0.2 0.2 0.1 0.2 0.0
2. ???
3. rd1so-ge5-0-0-4.cg.shawcable.net 0.0% 69 11.0 9.8 8.0 21.8 2.0
4. rc2no-tge0-9-2-0.cg.shawcable.ne 0.0% 69 20.9 15.2 10.5 20.9 2.7
5. 66.163.71.137 0.0% 69 17.6 15.4 9.2 36.9 4.4
6. rc2wh-tge0-9-2-0.vc.shawcable.ne 0.0% 69 26.8 28.7 23.1 91.4 9.6
7. rx0wh-bell-nexxia-ewo18733.vc.sh 0.0% 69 22.9 24.9 21.8 60.9 5.6
8. core4-vancouver_ge8-0-0.net.bell 0.0% 69 89.0 50.6 22.3 219.9 48.8
core3-vancouver_ge8-0-0.net.bell.ca
9. core2-vancouver_pos0-2-0.net.bel 0.0% 69 24.2 34.3 22.2 150.5 26.6
core1-vancouver_pos0-2-0.net.bell.ca
10. bx2-vancouver_POS1-0.net.bell.ca 0.0% 69 22.8 23.9 22.0 29.1 1.4
bx2-vancouver_POS2-0.net.bell.ca
11. 67.69.228.190 0.0% 69 25.3 24.0 22.2 29.9 1.4
12. xx208110096004.cipherkey.com 0.0% 69 83.5 80.4 36.8 296.3 46.4
|