RIS bview files 1-3-2026 and 21-5-2026 downloaded after 26-5
Dear colleagues, We have identified a misconfiguration in the pipeline that publishes RIS bview files to data.ris.ripe.net, and are giving early notice. As part of an infrastructure change on 27 May 2026, the publishing pipeline re-copied historical bview files produced after February 2022. This had two effects: * File modification timestamps changed for historical bview files published after February 2022. * Some bview files produced between 1 March 2026 and 21 May 2026 may be incomplete. This affects copies of files downloaded after 26 May 2026. For the incomplete files, the likely impact is that data from some RIS peers may be missing from the affected bviews. The data has not been lost. We have multiple copies available and expect to fully recover the affected files after the weekend. In the meantime, data consumers who rely on file modification timestamps, or who downloaded bview files for 1 March 2026-21 May 2026 after 26 May should take this into account. We apologise for the inconvenience and will update you on the situation early next week. Kind regards, Ties de Kock
Hey all, is it just more or are the MRT files missing from https://data.ris.ripe.net/ for the past 48 hours across multiple collectors (haven't checked them all) ? E.g. https://data.ris.ripe.net/rrc00/2026.06/ and https://data.ris.ripe.net/rrc03/2026.06/, nothing since the 18th? Cheers, James.
Hi James, Thanks for the message, and apologies for the late reply. Your email ended up in my spam folder. We are also investigating why it did not reach the list archives. On Sat, 20 Jun 2026 at 14:32, James Bensley <james+ris@bensley.me> wrote:
Hey all,
is it just more or are the MRT files missing from https://data.ris.ripe.net/ for the past 48 hours across multiple collectors (haven't checked them all) ?
E.g. https://data.ris.ripe.net/rrc00/2026.06/ and https://data.ris.ripe.net/rrc03/2026.06/, nothing since the 18th?
The issue affected all BGP update files. We applied a mitigation on Saturday. RIS update file production, including the backfill of affected data, recovered on Saturday 20 June at around 15:35 UTC. The root cause was a process that had become stuck. We did not detect this due to a gap in our monitoring. This specific alert for update files being updated stopped working after a recent migration, and we have now fixed it. We are also taking a broader look at RIS monitoring. The monitoring for RIS is changing from a legacy monitoring setup (icinga) to victoriametrics. This includes adding metrics inside the RIS pipelines. We expect this to help us detect issues before they have downstream effects and respond more quickly in the future. An end to end check, checking if the latest files are up to date, is definitely one of the a scenario we will cover. Kind regards, Ties de Kock RIPE NCC
Cheers, James. ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ris-users.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
participants (2)
-
James Bensley -
Ties de Kock