Maybe we can pinpoint the troubled node if we match the loss with your tracert logs and with our own.
ok, i'll bite.
Traceroute from Comhem-> rp.entropiauniverse.com
2 83.255.248.168 (83.255.248.168) 5.166 ms 6.102 ms 4.946 ms
3 vrr-pr-r-02-to-vrr-bb-r-01.comhem.se (83.255.252.214) 10.674 ms 11.897 ms 10.949 ms
4 64.209.107.209 (64.209.107.209) 8.898 ms 9.364 ms 7.914 ms
5 64.208.110.70 (64.208.110.70) 71.364 ms 72.592 ms 70.641 ms
6 ten-gige-1-1.mpr1.ams2.nl.above.net (64.125.26.73) 71.871 ms 68.617 ms 72.152 ms
7 * * *
Traceroute from mpr1.ams2.nl.above.net -> comhem
1 ge-1-2-0.mpr1.ams1.nl.above.net (64.125.26.74) 0 msec 0 msec 0 msec
2 *
ge6-0-0-104-1000M.ar1.AMS1.gblx.net (64.208.110.69) 52 msec 52 msec
3 64.209.107.210 [AS 3549] 72 msec 76 msec 72 msec
4 vrr-bb-r-02-to-vrr-pr-r-01.comhem.se (83.255.252.215) [AS 39651] 68 msec 68 msec *
5 *
83.255.248.169 [AS 39651] 64 msec *
ping from comhem to 64.209.107.209:
--- 64.209.107.209 ping statistics Tue Sep 2 21:04:02 2008 ---
1000 packets transmitted, 1000 received, 0.00% packet loss, time 9446ms
rtt min/avg/max/mdev = 7.341/9.900/64.297/4.649 ms
ping from comhem to 64.208.110.70:
--- 64.208.110.70 ping statistics Tue Sep 2 21:04:53 2008 ---
1000 packets transmitted, 939 received, 6.10% packet loss, time 12789ms
rtt min/avg/max/mdev = 76.327/83.133/130.499/6.359 ms
ping from comhem to 64.125.26.73:
--- 64.125.26.73 ping statistics Tue Sep 2 21:05:41 2008 ---
1000 packets transmitted, 391 received, 60.90% packet loss, time 12349ms
rtt min/avg/max/mdev = 76.840/105.671/300.997/52.043 ms
ping from mpr1.ams2.nl.above.net -> mpr1.ams1.nl.above.net
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
ping from mpr1.ams2.nl.above.net -> 64.208.110.69 (ar1.AMS1.gblx.net)
Success rate is 40 percent (2/5), round-trip min/avg/max = 60/60/60 ms
--------
traceroute from bbb to rp.entropiauniverse.com
2 ti3031a211-pc5.ti.telenor.net (146.172.72.125) 3.103 ms 5.106 ms 3.978 ms
3 ti3005d320-ge3-0-0.ti.telenor.net (146.172.109.17) 4.188 ms 5.396 ms 4.219 ms
4 * * *
5 ti3003c310-ae5-0.ti.telenor.net (146.172.100.33) 8.952 ms 8.651 ms 8.471 ms
6 ti6000b300-ae1-0.ti.telenor.net (146.172.105.22) 11.244 ms 9.872 ms 10.920 ms
7 212.162.17.133 (212.162.17.133) 28.248 ms 28.157 ms 28.017 ms
8 ae-31-55.ebr1.Dusseldorf1.Level3.net (4.68.119.158) 32.429 ms 29.501 ms 32.580 ms
9 ae-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 40.589 ms 42.387 ms 35.609 ms
10 ae-1-100.ebr1.Dusseldorf1.Level3.net (4.69.132.129) 32.179 ms 38.026 ms 36.178 ms
11 ae-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 43.246 ms 41.155 ms 37.147 ms
12 ae-22-54.car2.Frankfurt1.Level3.net (4.68.118.112) 38.078 ms ae-22-56.car2.Frankfurt1.Level3.net (4.68.118.176) 36.838 ms ae-22-52.car2.Frankfurt1.Level3.net (4.68.118.48) 36.013 ms
13 ge-1-8.mpr1.fra1.de.above.net (62.4.64.61) 38.210 ms 36.694 ms 38.080 ms
14 ten-gige-1-1.mpr1.ams2.nl.above.net (64.125.26.73) 86.358 ms 79.728 ms 81.707 ms
15 * * *
16 ten-gige-1-1.mpr1.ams2.nl.above.net (64.125.26.73) 86.314 ms 90.604 ms 88.477 ms
ping from bbb to 4.68.118.112
--- 4.68.118.112 ping statistics Tue Sep 2 21:48:58 2008 ---
1000 packets transmitted, 1000 received, 0.00% packet loss, time 11984ms
rtt min/avg/max/mdev = 35.092/37.321/78.036/2.313 ms
ping from bbb to 62.4.64.61:
--- 62.4.64.61 ping statistics Tue Sep 2 21:50:12 2008 ---
1000 packets transmitted, 1000 received, 0.00% packet loss, time 12060ms
rtt min/avg/max/mdev = 36.184/38.120/45.612/0.885 m
ping from bbb to mpr1.ams2.nl.above.net
--- 64.125.26.73 ping statistics Tue Sep 2 21:51:14 2008 ---
1000 packets transmitted, 989 received, 1.10% packet loss, time 12529ms
rtt min/avg/max/mdev = 73.976/97.031/280.563/40.135 ms