I don't think this is normal, I think this is a fault and needs to be addressed. There should be significant reachability problems, because rerouting isn't neither immediate, nor lock-step with SW+HW nor synchronous between nodes.
What exactly needs to be done, I can't tell without looking at the specific case. I'm not sure I understand 'tail-end ' and 'origin announcer' as synonyms, tail to me means receiver, head advertiser. But origin announcer to me means advertiser. So I'm not sure in which position you are. But if you are the source of this prefix, then you can probably fix the situation, if you are not, then you probably cannot fix the situation. On Mon, 28 Nov 2022 at 07:56, Pirawat WATANAPONGSE via NANOG <nanog@nanog.org> wrote: > > Dear Guru(s), > > > My apologies upfront if this question has already been asked. > If that’s the case, please kindly point me to the solution|thread so that the > mailing list bandwidth is not wasted. > > Situation: > On one of our prefixes, we are detecting continuous “BGP AS-Path Changes” in > the order of 1,000 announcements per hour---practically one every 3-4 seconds. > Those paths oscillate between two of our immediate upstreams. > > Questions: > 1. Is this number of events “normal” for a prefix? > 2. Is there any way we, as the tail-end (Origin Announcer), can do to reduce > it? Or should I just “let it be”? > 3. [Extra] Is this kind of oscillation affecting user experience, say, > throughput and/or latency? > > Thank you in advance for all the pointers and help. > > > Best Regards, > > Pirawat. > -- ++ytti
