There are only two situations where you will have a route that "isn't
liked", 1) The sender does something wrong, 2) The receiver incorrectly
handles something that is actually right. Either way, there is a
fundamental flaw in someone's BGP implementation, and that needs to get
resolved immediately. Flapping between the offender and its peer is
probably an acceptable way to go about finding these, flapping over the
entire internet because vendor C chooses to ignore the protocol spec and
vendor F does not is probably not...