This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[db-wg] 2018-06 Proposal Implemented (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)

• Previous message (by thread): [db-wg] 2018-06 Proposal Implemented (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
• Next message (by thread): [db-wg] RIPE-NONAUTH to RIPE for IANA anycast prefixes?

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ronald F. Guilmette rfg at tristatelogic.com
Thu Jan 16 15:18:02 CET 2020

In message <7747EE59-A4AD-4191-93B7-0A3B0A1C6AAC at ripe.net>, 
Edward Shryane via db-wg <db-wg at ripe.net> wrote:

>The Non-authoritative Route Object cleanup job ran for the first time
>last night. We identified 978 route(6) objects with conflicting ROA(s)
>which are now marked for cleanup, and emailed 269 addresses.

Praise be unto you.

Cleanliness is next to Godliness.


Regards,
rfg

• Previous message (by thread): [db-wg] 2018-06 Proposal Implemented (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
• Next message (by thread): [db-wg] RIPE-NONAUTH to RIPE for IANA anycast prefixes?

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]