<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hey all,<br>
<br>
We've just had two reports on <a class="moz-txt-link-abbreviated" href="mailto:webmaster@python.org">webmaster@python.org</a> about ipv6
connectivity issues. Normally they are caused by client / route
issues, however if I try via claranet I get failures too:<br>
<br>
<a class="moz-txt-link-freetext" href="http://noc.eu.clara.net/lg.php">http://noc.eu.clara.net/lg.php</a><br>
Router: US <br>
Command: ping ipv6 python.org<br>
<br>
Sending 5, 100-byte ICMP Echos to 2001:888:2000:D::A2, timeout is 2
seconds:<br>
.....<br>
Success rate is 0 percent (0/5)<span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0);
font-family: Times; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="font-family: arial,helvetica;
text-align: center;"></span></span><br>
<br>
Reports below:<br>
<br>
It seems that your IPv6 network is down:<br>
<br>
[luk@bender:~]$ traceroute6 python.org # from my workplace<br>
traceroute to python.org (2001:888:2000:d::a2), 30 hops max, 80 byte
packets<br>
1 spider1.mimuw.edu.pl (2001:6a0:5001:1::1) 0.273 ms 0.295 ms
0.293 ms<br>
2 kp-mm-r3.rtr.net.icm.edu.pl (2001:6a0:4001:1::1) 4.794 ms
4.826 ms 4.822 ms<br>
3 kp-mm-r3.rtr.net.icm.edu.pl (2001:6a0:1:4::1) 5.045 ms 5.069
ms 5.254 ms<br>
4 2001:6a0:0:19::1 (2001:6a0:0:19::1) 1.396 ms 1.394 ms 1.401
ms<br>
5 2001:b10:c000:204::1 (2001:b10:c000:204::1) 6.499 ms 6.501 ms
6.513 ms<br>
6 pionier-bckp.rt1.poz.pl.geant2.net (2001:798:23:10aa::5) 6.476
ms 5.960 ms 5.975 ms<br>
7 so-7-1-0.rt1.fra.de.geant2.net (2001:798:cc:1401:2301::1)
18.706 ms 18.842 ms 18.876 ms<br>
8 2001:450:2002:70::1 (2001:450:2002:70::1) 148.335 ms 144.553
ms 143.525 ms<br>
9 2001:450:2002:1e2::2 (2001:450:2002:1e2::2) 27.310 ms 27.305
ms 27.300 ms<br>
10 * * *<br>
11 * * *<br>
12 * * *<br>
13 kpn-ic-135436-adm-b5.c.telia.net (2001:2000:3080:6f::2) 48.579
ms 48.601 ms 48.554 ms<br>
14 * * *<br>
15 * * *<br>
16 * * *<br>
17 * * *<br>
18 * * *<br>
19 * * *<br>
20 * * *<br>
21 * * *<br>
22 * * *<br>
23 * * *<br>
24 * * *<br>
25 * * *<br>
26 * * *<br>
27 * * *<br>
28 * * *<br>
29 * * *<br>
30 * * *<br>
<br>
<br>
I'd like to just report that python.org (and subdomains) is not
avaiable (lost 100% packets, no ICMP responses) from some locations
over IPv6. The problem started yesterday in the evening CEST. I'm
observing the problem from the University of Warsaw network which is
one of the largest .edu networks in Poland. Traceroute6 reports:<br>
<br>
root@schowek:/home/accek/foo# traceroute6 pypi.python.org<br>
traceroute to pypi.python.org (2001:888:2000:d::a8) from
2001:6a0:5001:2:212:3fff:fe78:660, 30 hops max, 16 byte packets<br>
1 spider2.mimuw.edu.pl (2001:6a0:5001:2::1) 0.237 ms 0.202 ms
0.207 ms<br>
2 kp-mm-r3.rtr.net.icm.edu.pl (2001:6a0:4001:1::1) 4.229 ms
4.175 ms 4.115 ms<br>
3 kp-mm-r3.rtr.net.icm.edu.pl (2001:6a0:1:4::1) 4.085 ms 3.824
ms 4.079 ms<br>
4 2001:6a0:0:19::1 (2001:6a0:0:19::1) 6.328 ms 0.821 ms 0.736
ms<br>
5 2001:b10:c000:204::1 (2001:b10:c000:204::1) 6.136 ms 5.953 ms
5.894 ms<br>
6 * pionier-bckp.rt1.poz.pl.geant2.net (2001:798:23:10aa::5)
6.249 ms 5.952 ms<br>
7 so-7-1-0.rt1.fra.de.geant2.net (2001:798:cc:1401:2301::1)
18.643 ms 18.661 ms 18.659 ms<br>
8 2001:450:2002:70::1 (2001:450:2002:70::1) 112.468 ms 76.75 ms
18.881 ms<br>
9 2001:450:2002:1e2::2 (2001:450:2002:1e2::2) 44.23 ms 27.581
ms 27.315 ms<br>
10 * * *<br>
11 * * *<br>
12 * * *<br>
13 kpn-ic-135436-adm-b5.c.telia.net (2001:2000:3080:6f::2) 49.17
ms 49.016 ms 77.695 ms<br>
14 * * *<br>
15 * * *<br>
16 * * *<br>
17 * * *<br>
18 * * *<br>
19 * * *<br>
20 * * *<br>
<br>
It looks like a routing problem in the core IPv6. I don't know the
exact area affected, but entries like 'telia.net' or 'geant2.net'
suggest it's not a local issue. Access via some Teredo server in the
Netherlands seems ok.<br>
<br>
Maybe it's a good idea to drop AAAA DNS records for python.org
temporarily, especially that easy_install and such are broken on
affected networks with IPv6-enabled hosts (and automatic fallback to
IPv4 does not always work, at least in my case).<br>
<br>
All the best, <br>
<br>
Michael Foord<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.voidspace.org.uk/">http://www.voidspace.org.uk/</a>
May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing <a class="moz-txt-link-freetext" href="http://www.sqlite.org/different.html">http://www.sqlite.org/different.html</a>
</pre>
</body>
</html>