Brekage due to Hurricane Electric/Internet2

[William F. Maton Sotomayor]

>>> <http://lists.debian.org/debian-www/2009/10/msg00020.html>
>>
>> +1 here.  Coming from CANARIE-assigned address space the site is
>> unreachable.
>
> What is your source address?  Can you reach 2001:8d8:2:1:6564:a62:0:2,
> for instance?

We have address space from CAANRIE's network, so naturally it is the 
reasearch network.  However, some blocks allocated under that space also 
have access to the global IPv6 network so those folks don't have a problem 
reaching things.  The ones that don't get in trouble:

stats 1219# traceroute 2001:8d8:2:1:6564:a62:0:2
traceroute to 2001:8d8:2:1:6564:a62:0:2 (2001:8d8:2:1:6564:a62:0:2), 30 
hops max, 40 byte packets
  1  olans.core.ottix.net (2001:410:90ff::1)  0.710 ms  0.788 ms  0.880 ms
  2  border2.core.ottix.net (2001:478:235::7)  0.488 ms  0.482 ms  0.468 ms
  3  canet5.gigafed.net (2001:478:149::13)  13.182 ms  13.664 ms  14.148 ms
  4  2001:410:101:30::2 (2001:410:101:30::2)  70.721 ms  70.832 ms  71.430 ms
  5  2001:320:1b00:1::1 (2001:320:1b00:1::1)  185.465 ms  185.575 ms  185.690 ms
  6  * * *
  7  * * *
  8  * * *
  9  * * *
10  * * *
11  * * *
12  linx.bb-c.the.lon.gb.oneandone.net (2001:7f8:4::2170:1)  685.270 ms  689.004 ms  695.486 ms
13  te-1-2.bb-c.nkf.ams.nl.oneandone.net (2001:8d8:0:2::6)  699.094 ms  708.692 ms  711.432 ms
14  te-4-1.bb-c.act.fra.de.oneandone.net (2001:8d8:0:2::a)  719.148 ms  722.634 ms  725.365 ms
15  te-3-3.bb-c.bs.kae.de.oneandone.net (2001:8d8:0:2::2a)  1026.029 ms 
te-1-3.bb-c.bs.kae.de.oneandone.net (2001:8d8:0:2::12)  1016.646 ms 
te-3-3.bb-c.bs.kae.de.oneandone.net (2001:8d8:0:2::2a)  730.999 ms
16  ae-1.gw-dists-b.bs.ka.oneandone.net (2001:8d8:0:4::11)  731.097 ms 
ae-2.gw-dists-b.bs.ka.oneandone.net (2001:8d8:0:5::11)  731.451 ms 
ae-1.gw-dists-b.bs.ka.oneandone.net (2001:8d8:0:4::11)  731.185 ms
17  wieck.debian.org (2001:8d8:2:1:6564:a62:0:2)  727.989 ms  721.742 ms 
718.61 9 ms

Interesting.  Today it's working.

>> I suspect that global transit routes are being advertised to some
>> research networks but the traffic is getting tanked.
>
> Yes, this could be a routing leak.  CANARIE should be able to resolve
> it.

They are talking to KREONet who apparently is announcing those routes. 
The above traceroute might be a fix in progress.

wfms