Hi Hank, Following up with Cisco POC, I got this response. "We are in the process of retrieving this /20 back. An ARIN ticket was opened for this."
I checked the ARIN allocation file until 1st March so it's been more than 4 months since ARIN marked this prefix "reserved". ftp://ftp.arin.net/pub/stats/arin/delegated-arin-extended-20180301 On Sun, 15 Jul 2018 at 20:08 Aftab Siddiqui <[email protected]> wrote: > Hi Hank, > > On Sun, 15 Jul 2018 at 04:32 Hank Nussbacher via db-wg <[email protected]> > wrote: > >> On 13/07/2018 18:40, Sandra Murphy via db-wg wrote: >> >> While we are on the topic, anyone have an idea about Cisco and >> 66.187.208.0/20? > > > Same issue, just because there is a bad entry in the RADB many transits > are accepting it, well there is Hurricane Electric in the middle as well > who doesn't filter anything though. > > route: 66.187.208.0/20 > <https://apps.db.ripe.net/db-web-ui/#/lookup?source=radb-grs&key=66.187.208.0/20AS109&type=route> > descr: CISCO SYSTEMS, INC 170 WEST TASMAN DRIVE SAN JOSE, CA 95134 US > RP-ALLN > origin: AS109 > <https://apps.db.ripe.net/db-web-ui/#/lookup?source=radb-grs&key=AS109&type=aut-num> > mnt-by: MAINT-AS109 > <https://apps.db.ripe.net/db-web-ui/#/lookup?source=radb-grs&key=MAINT-AS109&type=mntner> > source: RADB-GRS >
