SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #4207497
Ticket Status: Remote Problem

PoP: chzrh02 - Init7 AG (Zurich)

connectivity breakage between 2001:1620:f00:80::1 & 2001:41d0:2:2eb9::1
[ch] Shadow Hawkins on Friday, 15 April 2011 14:33:14
From today around 11am traceroute6 -n chewbacca.ioda.net traceroute to chewbacca.ioda.net (2001:41d0:2:2eb9::1), 30 hops max, 40 byte packets using UDP 1 2001:1620:f00:80::1 (2001:1620:f00:80::1) 13.025 ms 14.319 ms 15.880 ms 2 2001:1620:2005:4::1 (2001:1620:2005:4::1) 25.968 ms 25.281 ms 24.379 ms 3 2001:1620:2::49 (2001:1620:2::49) 21.768 ms 23.344 ms 24.370 ms 4 2001:1620:2::6 (2001:1620:2::6) 38.989 ms 39.258 ms 40.525 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * reverse side traceroute6 -n ns.ioda-net.ch traceroute to ns.ioda-net.ch (2001:1620:f00:80::2), 30 hops max, 40 byte packets using UDP 1 2001:41d0:2:2eff:ff:ff:ff:ff (2001:41d0:2:2eff:ff:ff:ff:ff) 0.497 ms * * 2 2001:41d0::922 (2001:41d0::922) 0.900 ms 0.532 ms 0.530 ms 3 2001:41d0::7d2 (2001:41d0::7d2) 6.004 ms * * 4 2001:41d0::692 (2001:41d0::692) 27.038 ms * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * Nor ping6 works, or other tcp/udp protocols From both location ping6 ipv6.google.com ping6 -c4 ipv6.google.com PING ipv6.google.com(2a00:1450:8002::6a) 56 data bytes 64 bytes from 2a00:1450:8002::6a: icmp_seq=1 ttl=56 time=9.56 ms 64 bytes from 2a00:1450:8002::6a: icmp_seq=2 ttl=56 time=9.53 ms 64 bytes from 2a00:1450:8002::6a: icmp_seq=3 ttl=56 time=9.61 ms 64 bytes from 2a00:1450:8002::6a: icmp_seq=4 ttl=56 time=9.52 ms --- ipv6.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 9.521/9.556/9.613/0.104 ms ping6 -c4 ipv6.google.com PING ipv6.google.com(2a00:1450:8002::63) 56 data bytes 64 bytes from 2a00:1450:8002::63: icmp_seq=1 ttl=51 time=37.3 ms 64 bytes from 2a00:1450:8002::63: icmp_seq=2 ttl=51 time=36.8 ms 64 bytes from 2a00:1450:8002::63: icmp_seq=3 ttl=51 time=36.0 ms 64 bytes from 2a00:1450:8002::63: icmp_seq=4 ttl=51 time=37.0 ms --- ipv6.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3003ms rtt min/avg/max/mdev = 36.075/36.830/37.314/0.518 ms ping6 -c4 www.sixxs.net chewbacca:# ping6 -c4 www.sixxs.net PING www.sixxs.net(2001:1af8:4050::2) 56 data bytes 64 bytes from 2001:1af8:4050::2: icmp_seq=1 ttl=59 time=6.21 ms 64 bytes from 2001:1af8:4050::2: icmp_seq=2 ttl=59 time=6.24 ms 64 bytes from 2001:1af8:4050::2: icmp_seq=3 ttl=59 time=6.19 ms 64 bytes from 2001:1af8:4050::2: icmp_seq=4 ttl=59 time=6.21 ms --- www.sixxs.net ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3003ms rtt min/avg/max/mdev = 6.199/6.218/6.246/0.017 ms yoda:~ # ping6 -c4 www.sixxs.net PING www.sixxs.net(2001:1af8:4050::2) 56 data bytes 64 bytes from 2001:1af8:4050::2: icmp_seq=1 ttl=55 time=30.1 ms 64 bytes from 2001:1af8:4050::2: icmp_seq=2 ttl=55 time=29.8 ms 64 bytes from 2001:1af8:4050::2: icmp_seq=3 ttl=55 time=30.1 ms 64 bytes from 2001:1af8:4050::2: icmp_seq=4 ttl=55 time=30.3 ms --- www.sixxs.net ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3002ms rtt min/avg/max/mdev = 29.862/30.135/30.311/0.206 ms yoda = ns.ioda-net.ch / vellerat.ioda.net (Vellerat SixxS end point) chewbacca = ns.ioda.net ( OVH Paris endpoint ) Seems a breakage somewhere between Init Seven & OVH peering ? Thanks for any help, I've becomed too dependant of ipv6 :-)
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Friday, 15 April 2011 20:14:12
Message is Locked
The state of this ticket has been changed to remoteproblem
connectivity breakage between 2001:1620:f00:80::1 & 2001:41d0:2:2eb9::1
[ch] Jeroen Massar SixXS Staff on Friday, 15 April 2011 20:15:12
Seems a breakage somewhere between Init Seven & OVH peering ?
OVH is missing some crucially important transit providers and as such their prefix is not globally visible. Nothing we can do about, thus unfortunately can't help here.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker