apologies to whoever Noticed on The Internet that a prefix i was announcing was bouncing between two HE peers for about half an hour
good news no NANOG posts about this ASN (yet)

now to configure ipv6 route-maps for ipv6 peers, now that enough is up that i can finish from home instead of a chairless DC floor

do ipv6 bogon filter templates exist? do bogons even apply for v6?

@gewt The two biggest I can think of are ULA space and the well-known NAT64 prefix of 64:ff9b::/96, as those should very much both be ASN-internal, but can be passed around via BGP in valid configurations (I do this in my lab, as I needed site-specific NAT64 prefixes for NAT46 'virtual IPs' to use as a source address, as v4 isn't routed between sites)

Oh, and 2001:db8::/32 just to make sure nobody can use the documentation prefix as anything other than documentation.

Aside from that, AFAIK most of what's left is either "nobody's using it in a way that not filtering it would impact" or "that really shouldn't be traversing BGP in the first place" stuff like multicast.

@becomethewaifu oh that's trivial to make a route-map to filter
@gewt checkin' flap stats on a sunday night? couldn't be me, i've never done that /s
@rey i had a prefix bouncing between two peers because i forgot to down the one on the old router lol