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]/
RIS data collection outage report
- Previous message (by thread): RIS to be modified to support 4-byte ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erik Romijn
eromijn at ripe.net
Mon Jan 15 13:43:50 CET 2007
Subject: RIS data collection outage report Dear Colleagues, Between May 2005 and December 2006, Remote Route Collectors (RRCs) 06, 07, 10, and 14 stored few updates and only partial Routing Information Base (RIB) dumps. These RRCs are connected to NSPIXP2 (Otemachi, JP), Netnod (Stockholm, SE), MIX (Milan, IT), and PAIX (Palo Alto, US). During this period, most update dumps contained no more than a few updates, and many were completely empty, even when many more updates had been seen. Most RIB dumps have been partially stored. Some are empty and some are complete. As the data used by the RIS is read from these files, no RIS tools will have seen these missing routes and updates. The cause for this issue was an error in the permissions set for a tool used by the compression script. This caused the files to be compressed a few seconds after their creation, thus deleting the old file. In most cases, this caused all data written after a few seconds to be discarded. We corrected the error on 2 January 2007. Any data collected on 3 January 2007 or later is stored correctly. We are working to implement better monitoring to ensure that, should this problem reoccur, we will be notified. RRCs other than those connected to NSPIXP2, Netnod, MIX, and PAIX have not been affected in any way. Our apologies for any inconvenience caused. If you have any questions, please e-mail: ris at ripe.net Regards, Erik Romijn Information Services department RIPE NCC
- Previous message (by thread): RIS to be modified to support 4-byte ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]