Do people even read these? Re: BGP Update Report
Geoff Huston gih at apnic.net
Sat Jun 18 23:22:08 CEST 2016
> On 19 Jun 2016, at 6:05 AM, Mikael Abrahamsson <swmike at swm.pp.se> wrote: > > On Fri, 17 Jun 2016, cidr-report at potaroo.net wrote: > >> >> TOP 20 Unstable Prefixes >> Rank Prefix Upds % Origin AS -- AS Name >> 1 - 202.65.32.0/21 28086 0.8% AS10131 -- CKTELECOM-CK-AP Telecom Cook Islands, CK >> 2 - 110.170.17.0/24 21868 0.7% AS134438 -- AIRAAIFUL-AS-AP Aira & Aiful Public Company Limited, TH >> 3 - 123.231.192.0/24 21562 0.7% AS133841 -- IDOLA-BROADBAND-AS-ID INDONESIA BROADBAND ACCESS - ANYWHERE, ID >> 4 - 93.181.192.0/19 20895 0.6% AS13118 -- ASN-YARTELECOM Verhnevolzhsky branch, RU >> 5 - 123.231.206.0/24 19170 0.6% AS133841 -- IDOLA-BROADBAND-AS-ID INDONESIA BROADBAND ACCESS - ANYWHERE, ID >> 6 - 123.231.193.0/24 19082 0.6% AS133841 -- IDOLA-BROADBAND-AS-ID INDONESIA BROADBAND ACCESS - ANYWHERE, ID >> 7 - 195.128.159.0/24 15455 0.5% AS56636 -- ASVEDARU , RU >> 8 - 192.254.88.0/24 15452 0.5% AS21859 -- ZNET - Zenlayer Inc, US >> 9 - 185.11.121.0/24 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 (http://bgpupdates.potaroo.net/cgi-bin/per-prefix?prefix=202.65.32.0.21) Geoff