Looks like I have the same problem. Was fine for years (0.1% just like ronald) but sometime in late 2011/early 2012 I started having this problem. Couldn't find a solution for it for months and then sometime in mid-2012 the problem seemed to just go away. Then about two days ago the ploss came back. When I first saw your post (my ploss had been fine for months at this point) I did a trace: Tracing Zone: SSCU Trench Wars IP Address: 66.36.241.110 Hop IP Address Host Name Loss(%) Min/Avg/Max Ping--- --------------- -------------------------------- ------- ---------------- 1 192.168.1.1 0.0 0 0 0 2 10.9.44.96 0.0 0 10 70 3 130.81.110.36 G3-3-897.BSTNMA-LCR-08.verizon-g 0.0 0 10 70 4 130.81.29.254 so-0-3-0-0.BOS-BB-RTR2.verizon-g 0.0 0 10 70 5 130.81.19.66 so-7-2-0-0.NY5030-BB-RTR2.verizo 0.0 10 20 90 6 152.63.2.81 0.xe-3-1-0.BR3.NYC4.ALTER.NET 0.0 10 20 50 7 4.68.111.137 te-7-3-0.edge2.NewYork2.level3.n 0.0 10 20 80 8 4.69.138.222 vlan51.ebr1.NewYork2.Level3.net 0.0 10 20 60 9 4.69.132.89 ae-3-3.ebr2.Washington1.Level3.n 0.0 20 20 40 10 4.69.134.150 ae-72-72.csw2.Washington1.Level3 0.0 20 30 50 11 4.69.149.68 ae-22-70.car2.Washington1.Level3 0.0 20 50 240 12 ... ... 0.0 1000000 0 0 13 ... ... 0.0 1000000 0 0 Cycles: 112 After the problem started again I did another trace: Tracing Zone: SSCU Trench Wars IP Address: 66.36.241.110 Hop IP Address Host Name Loss(%) Min/Avg/Max Ping--- --------------- -------------------------------- ------- ---------------- 1 192.168.1.1 0.0 0 0 0 2 10.9.44.96 0.0 0 10 40 3 130.81.109.62 G3-3-797.BSTNMA-LCR-07.verizon-g 0.0 0 10 30 4 130.81.29.252 so-0-3-0-0.BOS-BB-RTR1.verizon-g 0.0 0 10 50 5 152.63.18.222 0.ae3.BR1.NYC1.ALTER.NET 0.0 10 20 80 6 4.68.62.41 ae11.edge2.NewYork.Level3.net 0.0 10 30 110 7 4.69.138.222 vlan51.ebr1.NewYork2.Level3.net 0.0 10 20 70 8 4.69.132.89 ae-3-3.ebr2.Washington1.Level3.n 0.0 20 30 70 9 4.69.134.154 ae-82-82.csw3.Washington1.Level3 0.0 30 40 70 10 4.69.149.132 ae-32-80.car2.Washington1.Level3 0.0 20 70 440 11 ... ... 0.0 1000000 0 0 12 ... ... 0.0 1000000 0 0 Cycles: 133 I still have no idea what the problem is or how to fix it though.