On 2013-09-26 11:55 , Fredy Kuenzler wrote: > Anyone else seeing this... do we have a new peering spat or is it just a > random routing issue?
Looks to be just that prefix, as for instance: traceroute to chzrh02.sixxs.net (213.144.148.74), 64 hops max, 52 byte packets [..] 3 217-168-54-245.static.cablecom.ch (217.168.54.245) 9.388 ms 10.610 ms 9.914 ms 4 * 84.116.200.233 (84.116.200.233) 11.472 ms 12.464 ms 5 ch-zrh01b-ra1-ae-1.aorta.net (84.116.134.142) 11.482 ms 11.522 ms 11.727 ms 6 213.46.171.14 (213.46.171.14) 21.762 ms 18.420 ms 24.830 ms 7 r1zlz1.core.init7.net (77.109.128.210) 14.849 ms 27.172 ms 61.669 ms 8 chzrh02.sixxs.net (213.144.148.74) 14.876 ms 15.100 ms 15.925 ms traceroute to 217.168.54.245 (217.168.54.245), 64 hops max 1 213.144.148.73 (213.144.148.73) 0.556ms 0.446ms 0.413ms 2 77.109.128.209 (77.109.128.209) 0.422ms 0.423ms 0.438ms 3 213.46.171.13 (213.46.171.13) 0.526ms 0.543ms 0.555ms 4 84.116.134.141 (84.116.134.141) 1.024ms 0.824ms 1.367ms 5 217.168.54.245 (217.168.54.245) 3.486ms 3.365ms 3.359ms Works fine at this moment. Greets, Jeroen _______________________________________________ swinog mailing list [email protected] http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
