Repairing the RPKIViews H1 2026 Archives

Key Takeaways

• RPKIViews repaired 110 rpkispools, processing 190,601 CCRs.
• Storage reduced from 190 TB to 62.86 GB compressed.
• CCR format compresses snapshot to ~20 MB versus 1 GB raw.
• ROA changes occur every ~2 minutes; ASPA changes every ~25 minutes.
• Repaired data now hosted on JP, EU, and US mirrors.

Pulse Analysis

The Resource Public Key Infrastructure (RPKI) underpins BGP route validation, yet its distributed database grows continuously as certificates, ROAs and ASPA objects are issued worldwide. Researchers need historic snapshots to audit certification authorities and to model routing‑security trends, but a naïve daily backup would consume roughly 1.44 TB per day, quickly becoming untenable. RPKIViews addresses this problem with the rpkispool format, which separates raw objects from deterministic metadata (CCR) and leverages deduplication, Merkle trees and Zstandard compression. The result is a compact, query‑ready archive that can be stored for long‑term analysis at a fraction of the raw size.

In early 2026 a compatibility issue surfaced: older rpki‑client releases wrote CCR byte strings in reverse order, breaking interoperability with other tools. Job Snijders added a repair routine to the rpkitouch utility and reprocessed the first‑half‑year archives on a 16‑core server. Over two days the team decompressed 110 rpkispools, re‑sorted 190,601 CCRs and recompressed the data, turning 4.37 TB of uncompressed material into 62.86 GB of compressed files—an order‑of‑magnitude reduction compared with the 190 TB a full‑snapshot approach would have required. The repaired pools now reflect accurate state transitions for more than 9.5 million CRLs and nearly 10 million manifest objects.

The cleaned archives are now mirrored in Japan, Europe and the United States, and can be decoded with rpki‑client 9.8+, RIPE NCC’s rpki‑commons library, or converted to JSON for custom analytics. By providing a reliable, space‑efficient historical record, RPKIViews enables security teams to pinpoint abnormal ROA churn—approximately every two minutes—and to study ASPA dynamics, which change roughly every 25 minutes. This level of granularity supports more accurate risk assessments, informs policy development, and encourages broader adoption of RPKI as a cornerstone of Internet routing security.