[outages] Anyone else seeing IPv6 issues going through Level3?

[Frank Bulk]

Service was restored to me at 7:15 pm.  I don't have an RFO -- I can only
guess there was some routing table issue for our netblock in Level3's
infrastructure.

Frank

-----Original Message-----
From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
Behalf Of Frank Bulk
Sent: Friday, March 16, 2012 6:50 PM
To: outages at outages.org
Subject: Re: [outages] Anyone else seeing IPv6 issues going through Level3?

Our upstream provider opened up a ticket with Level3 late this afternoon.
Hopefully it will be resolved, soon.  

Our upstream provider has three dual-stacked transit providers and they shut
down the Level3 IPv6 peering, but then we lost access to another third or so
of the sites.  For example, ipv6.t-mobile.com is only visible to us from
Level3, same with www.globalcrossing.com.  ipv6.cablelabs.com is with HE and
Level3 and we should be able to get HE via Sprint, but we lost visibility
anyways.

Frank

-----Original Message-----
From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
Behalf Of Frank Bulk
Sent: Friday, March 16, 2012 8:05 AM
To: 'Teun Vink'
Cc: outages at outages.org
Subject: Re: [outages] Anyone else seeing IPv6 issues going through Level3?

Thanks, Teun.  

Someone else pointed to me offlist that this could be just our prefix,
2607:fe28::/32.  I've already contacted our upstream provider who buys the
transit from Level3.  

Frank

-----Original Message-----
From: Teun Vink [mailto:teun at teun.tv] 
Sent: Friday, March 16, 2012 7:39 AM
To: Frank Bulk
Cc: outages at outages.org
Subject: Re: [outages] Anyone else seeing IPv6 issues going through Level3?

On Fri, 2012-03-16 at 07:12 -0500, Frank Bulk wrote:
> I monitor over 30 IPv6 hosts, and starting around 1:54 am (Central) I
> couldn't access about a third of them.  Here's the list of sites that I
> currently can't access:
> 

http://ring.nlnog.net promotime :)

Just ran a few tests from 88 host in 78 ASN's, 24 countries:

> ipv6_akamai_com_29  (2001:418:2401:9::8367:8929)

$ ring-ping 2001:418:2401:9::8367:8929
2001:418:2401:9::8367:8929 - 87 servers: 119ms average
2001:418:2401:9::8367:8929 - unreachable via: 1 server

> ipv6_akamai_com_40  (2001:418:2401:9::8367:8940_

$ ring-ping 2001:418:2401:9::8367:8940
2001:418:2401:9::8367:8940 - 87 servers: 120ms average
2001:418:2401:9::8367:8940 - unreachable via: 1 server

> ipv6_cnn_com 

bit at bit01:~$ ring-http ipv6.cnn.com
unreachable via: 88 hosts

> ipv6_google_com 

$ ring-http ipv6.google.com
unreachable via: 88 hosts

> ipv6_sprint_com 

$ ring-http ipv6.sprint.com
88 servers: OK


A ring-trace from all these hosts to 2001:418:2401:9::8367:8940
https://ring.nlnog.net/paste/p/pv2jaodnosy8mget


regards,
Teun




_______________________________________________
Outages mailing list
Outages at outages.org
https://puck.nether.net/mailman/listinfo/outages