On Oct 28, 2011, at 9:01 AM, Jon Lewis wrote:
On Fri, 28 Oct 2011, Ryan Rawdon wrote:
On Oct 28, 2011, at 3:43 AM, Ryan Rawdon wrote:
Starting at 2:50AM (Eastern), we are unable to reach 2001:4870::/32 from a number of locations (all locations that we tested from).
ashburn-rtr2#sh bgp ipv6 unicast 2001:4870::/32 % Network not in table ashburn-rtr2#
2001:4870::/32 re-appeared at 5:27AM and no other issues appeared to persist.
I'm a TWT customer, and still not seeing the /32, but am seeing lots of more specific /48's from it.
I don't think I actually checked which prefix we were seeing when connectivity was restored at the time I posted my follow-up. Right now we are seeing two prefixes from TWTC: 2001:4870::/31 2620:81:8000::/48 (and also 2001:4870:E00B::/48 from a path transiting 4323) I don't know for sure whether they were advertising the /31 or /32 before the event this morning but regardless 2001:4870::/32 wasn't reachable in the DFZ (as itself or as a superprefix). bgp.he.net still shows them advertising a /32, so I suspect they only changed to a /31 very recently - potentially during or after this outage.
I thought this was interesting though:
$ whois as4323@whois.arin.net [Querying whois.arin.net] [Redirected to rwhois.twtelecom.net:4321] [Querying rwhois.twtelecom.net] [rwhois.twtelecom.net] %rwhois V-1.5:003AB6:00 rwhois.twtelecom.net (rwhois_ngd v0.9.0 by James Sella) %error 230 No objects found
---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________