This document describes Resource Public Key Infrastructure (RPKI) related best practices and lessons learned.  It provides general recommendations aimed at supporting the implementation and operation of RPKI in diverse environments. These insights are drawn from practical experience and collaborative discussions but are not intended to be prescriptive. 

Continue

Welcome to our third half-yearly update. While we publish release notes with each update and promote new features and bug fixes on social media, these reports take a broader look at recent changes. You can find our previous half-yearly reports here and here. In 2025, PeeringDB’s board approved a 50% increase in spending on development and operations compared to 2024. All committees now have access to these resources, allowing us to complete more development work each month and devote more time to operational improvements.

Continue

The NRO RPKI Program aims to provide a more consistent and uniformly secure, resilient and reliable RPKI service. For 2025, the RPKI Steering Group, which includes RPKI experts from the five RIRs, set out to work on two main areas:

• Enhancing the transparency, robustness and security of the RPKI system.
• Increasing the consistency of the RPKI system user experience across RIRs.

Continue

The feedback period for the draft ‘Governance Document for the Recognition, Maintenance, and Derecognition of Regional Internet Registries’ (draft ‘RIR Governance Document’) has officially concluded. 

The consultation was open from 14 April to 27 May 2025, and allowed participants to share their opinions on the proposed text and requirements, as well as provide additional constructive comments.

Each RIR hosted at least one interactive informational session for their community during this period, where additional feedback may have been collected. Sessions were also hosted for ICANN communities, and an ICANN Public Comment process was held in parallel during the same period. The list of the sessions held and links to their archives are available on the NRO website.

This process focuses on reviewing and updating the fundamental principles of Internet Coordination Policy-2 (ICP-2), a key document that defines the criteria for recognizing and evaluating RIRs. The Number Resource Organization Number Council (NRO NC), which fulfils the role of the Address Supporting Organization Address Council (ASO AC), will discuss the feedback received from the RIR communities as well as the ICANN Public Comment process and use it to inform the next draft.

The NRO NC will publish the next draft for review to the RIR and ICANN communities in the later months of 2025.We would like to thank everyone who participated and provided feedback during this critical process. Your contributions are essential to ensuring that these principles reflect the needs and expectations of our community.

Author: Hervé Clément

You must have a second factor to login to PeeringDB from 1 July 2025. If you automate updates using our API, you'll need to use an API Key. But anonymous usage will not be going away. You can query the website or API without authenticating. This change will impact users who make updates or need access to contact information published in PeeringDB. To prepare for this we have simplified our user interface. We now have a single control page for second factors. You can still choose from: TOTP U2F tokens, and Passkeys.

Fig: U2F Hardware Authentication Security Keys, Tony Webster, CC By 2.0

Users can have multiple second factors. For instance, TOTP in an app on a phone and a U2F token. And users can download and securely store backup codes in case other factors aren’t available. Some organizations might need to move users from role accounts to personal accounts. We don't limit the number of accounts affiliated with an organization. And we provide permissions to manage permissions for individual users.

Continue

Authored by: Sofia Silva Berenguer, RPKI Program Manager, NRO

Earlier this year we launched the NRO RPKI Program and we shared information about the program’s purpose and the outcomes that were guiding our efforts. One of our main goals is to raise awareness among the technical community that we are committed to providing a more consistent and uniformly secure, resilient, and reliable RPKI service.

An important outcome from this year’s work is the documentation of a problem statement for the current Trust Anchor configuration and the exploration of potential solutions. We hope to share a proposal for discussion with the technical community soon.

Continue