Ce qui est troublant dans cette affaire, c'est la différence entre les deux traceroutes.
Test effectués sur OSX 10.8.2 ETH à 21h Dimanche
IPv4 :
Traceroute a démarré…
traceroute: Warning: youtube.fr has multiple addresses; using 74.125.230.206
traceroute to youtube.fr (74.125.230.206), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 5.109 ms 0.219 ms 0.184 ms
2 XXX 6.962 ms 6.756 ms 6.936 ms
3 XXX 6.094 ms 6.875 ms 6.293 ms
4 th2-49m-1.intf.nra.proxad.net (78.254.251.78) 6.738 ms 6.822 ms 7.152 ms
5 * th2-6k-2-v914.intf.nra.proxad.net (78.254.251.61) 6.996 ms *
6 212.27.57.202 (212.27.57.202) 7.144 ms 10.815 ms 7.306 ms
7 te0-7-0-18.338.ccr21.par04.atlas.cogentco.com (149.6.165.145) 7.667 ms 7.544 ms 7.150 ms
8 te0-2-0-4.mpd22.par01.atlas.cogentco.com (130.117.1.141) 7.896 ms
te0-5-0-4.mpd21.par01.atlas.cogentco.com (130.117.48.253) 7.216 ms
te0-1-0-4.ccr21.par01.atlas.cogentco.com (130.117.2.21) 7.712 ms
9 te0-3-0-1.mpd22.lon13.atlas.cogentco.com (130.117.50.9) 15.901 ms
te0-3-0-1.mpd21.lon13.atlas.cogentco.com (130.117.0.181) 15.928 ms
te0-4-0-6.ccr21.lon13.atlas.cogentco.com (154.54.37.177) 15.060 ms
10 te0-0-0-0.ccr22.lon01.atlas.cogentco.com (130.117.0.94) 16.082 ms 16.464 ms
te0-3-0-1.ccr22.lon01.atlas.cogentco.com (130.117.0.237) 16.093 ms
11 te3-1.ccr01.lon18.atlas.cogentco.com (154.54.62.50) 121.186 ms 361.006 ms 202.244 ms
12 149.6.146.30 (149.6.146.30) 120.355 ms 115.183 ms 109.906 ms
13 209.85.255.78 (209.85.255.78) 15.546 ms 15.172 ms 15.036 ms
14 209.85.253.90 (209.85.253.90) 15.789 ms
209.85.253.94 (209.85.253.94) 16.213 ms
209.85.253.90 (209.85.253.90) 15.129 ms
15 72.14.232.210 (72.14.232.210) 15.174 ms 20.433 ms
209.85.242.79 (209.85.242.79) 16.009 ms
16 72.14.235.172 (72.14.235.172) 14.914 ms
72.14.235.168 (72.14.235.168) 15.585 ms
72.14.235.172 (72.14.235.172) 15.548 ms
17 209.85.242.49 (209.85.242.49) 16.152 ms 15.319 ms 15.946 ms
18 par08s09-in-f14.1e100.net (74.125.230.206) 15.513 ms 15.420 ms 15.445 ms
En IPv6
traceroute6 to youtube.fr (2a00:1450:400c:c06::be) from XXX, 64 hops max, 12 byte packets
1 XXX 0.632 ms 0.191 ms 1.424 ms
2 * * *
3 th2-crs16-1.intf.routers.proxad.net 7.777 ms 7.322 ms 7.095 ms
4 cbv-9k-1-be1000.intf.routers.proxad.net 7.598 ms 7.277 ms 7.303 ms
5 google-pni-3.intf.routers.proxad.net 109.168 ms
2001:4860:1:1:0:3022:: 100.941 ms
2001:4860:1:1::3022:0:5 102.801 ms
6 2001:4860::1:0:23 7.976 ms 8.705 ms 8.526 ms
7 2001:4860::8:0:3df4 7.782 ms 7.950 ms
2001:4860::8:0:3df5 7.822 ms
8 2001:4860::8:0:2ac3 27.320 ms
2001:4860::8:0:2ac4 13.165 ms
2001:4860::8:0:2ac3 13.517 ms
9 2001:4860::2:0:87d 12.257 ms
2001:4860::2:0:87b 12.839 ms 12.592 ms
10 * * *
11 wb-in-xbe.1e100.net 13.018 ms 12.743 ms 12.707 ms
On a bien deux saturations : L'une en IPv4 sur le Peering Cogent/Google à Londres (Paris --> Londres --> Paris, Pratique....) et l'autre sur le Peering privé PROXAD/Google....
WTF ?!