Dear Gert,
On 29 Jan 2026, at 13:35, Gert Doering <gert@space.net> wrote:
... So the NCC already does it, but maybe not for route(6) and ROAs?
The NCC DB team sends automated emails 2 days after an assigned AUT-NUM object is deleted (we wait some time in case an object is deleted by accident). We do not look for references in ROAs. We look in the following object types for references to AS numbers no longer registered in the RIPE database (e.g. due to a return or inter-RIR transfer): as-set aut-num filter-set inet-rtr peering-set route(6) route-set and in the following attributes : aggr-bndry aggr-mtd components default export export-comps export-via filter filter-set if-addr import import-via inject interface local-as members mp-default mp-export mp-filter mp-import mp-members mp-peer mp-peering origin peer peering And ask maintainers of referencing objects to update and remove any references to those deleted ASN(s). I welcome any feedback on how this process can be improved. Regards Ed Shryane RIPE NCC