I do, useful to see who is causing route churning and such. sent from Android <div class="gmail_quote">On 19 Jun 2016 7:22 am, "Geoff Huston" <<a href="mailto:gih@apnic.net">gih@apnic.net</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> > On 19 Jun 2016, at 6:05 AM, Mikael Abrahamsson <<a href="mailto:swmike@swm.pp.se">swmike@swm.pp.se</a>> wrote: > > On Fri, 17 Jun 2016, <a href="mailto:cidr-report@potaroo.net">cidr-report@potaroo.net</a> wrote: > >> >> TOP 20 Unstable Prefixes >> Rank Prefix Upds % Origin AS -- AS Name >> 1 - <a href="http://202.65.32.0/21" rel="noreferrer" target="_blank">202.65.32.0/21</a> 28086 0.8% AS10131 -- CKTELECOM-CK-AP Telecom Cook Islands, CK >> 2 - <a href="http://110.170.17.0/24" rel="noreferrer" target="_blank">110.170.17.0/24</a> 21868 0.7% AS134438 -- AIRAAIFUL-AS-AP Aira & Aiful Public Company Limited, TH >> 3 - <a href="http://123.231.192.0/24" rel="noreferrer" target="_blank">123.231.192.0/24</a> 21562 0.7% AS133841 -- IDOLA-BROADBAND-AS-ID INDONESIA BROADBAND ACCESS - ANYWHERE, ID >> 4 - <a href="http://93.181.192.0/19" rel="noreferrer" target="_blank">93.181.192.0/19</a> 20895 0.6% AS13118 -- ASN-YARTELECOM Verhnevolzhsky branch, RU >> 5 - <a href="http://123.231.206.0/24" rel="noreferrer" target="_blank">123.231.206.0/24</a> 19170 0.6% AS133841 -- IDOLA-BROADBAND-AS-ID INDONESIA BROADBAND ACCESS - ANYWHERE, ID >> 6 - <a href="http://123.231.193.0/24" rel="noreferrer" target="_blank">123.231.193.0/24</a> 19082 0.6% AS133841 -- IDOLA-BROADBAND-AS-ID INDONESIA BROADBAND ACCESS - ANYWHERE, ID >> 7 - <a href="http://195.128.159.0/24" rel="noreferrer" target="_blank">195.128.159.0/24</a> 15455 0.5% AS56636 -- ASVEDARU , RU >> 8 - <a href="http://192.254.88.0/24" rel="noreferrer" target="_blank">192.254.88.0/24</a> 15452 0.5% AS21859 -- ZNET - Zenlayer Inc, US >> 9 - <a href="http://185.11.121.0/24" rel="noreferrer" target="_blank">185.11.121.0/24</a> 14957 0.5% AS202105 -- DSP-AS , SA > > Everyone of these prefixes have managed to average one update per 40 seconds during a week, or worse. How is that even possible? Yes, I know we don't generally have dampening anymore, but geez, that's a lot of updates. > In the case of Cook Islands Telecom the problem is not directly with them - its their one-up upstream Spark NZ (AS4648) who appears to be flicking this route across a number of transit upstreams (<a href="http://bgpupdates.potaroo.net/cgi-bin/per-prefix?prefix=202.65.32.0.21" rel="noreferrer" target="_blank">http://bgpupdates.potaroo.net/cgi-bin/per-prefix?prefix=202.65.32.0.21</a>) Geoff _______________________________________________ AusNOG mailing list <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a> </blockquote></div>