In message <20141106150814.GX31092@Space.Net>, Gert Doering <gert@space.net> wrote:
In this particular case, I wonder why nobody is yelling at the upstream who is happily forward packets for that AS... due dilligence at accepting customer prefixes would have easily caught the announcements.
I personally would be ``yelling at the upstream'' right now, but someone made a comment on the NANOG mailing list which sort-of hinted that this would be entirely futile in the case of AS200002. I don't know, but I suspect that he already knows something that I don't know, so I'm not wasting my time on sending comlaints to an entity that, it seems, may perhaps not give a damn.
(Yes, I understand that I'm now officially part of the problem, as I'm obviously not willing to do everything technically possible to stop particular sorts of badness)
To the extent that you might be able to avoid forwarding route announcements which originate from AS201640, allow me to express my personal opinion that doing so would be admirable. Regards, rfg