RIPE Database Quarterly Planning
We launched this initiative in Q4 2021, and we are open to improving what we publish here and how we do that. So let us know if there are ways we can better present our plans.
We will update this page as our activities progress and continue to share updates on RIPE Labs, on the RIPE Database Working Group (WG) mailing list and at RIPE Meetings and other events.
Q2 2026 Plans
Last Updated: 27 March 2026
Item 1: Migrate API Keys from LIR Portal to My Resources
We plan to move IP Analyser and Resources API access out of the LIR Portal and into My Resources under the Database website. This will group all resources together under one page, so they are more easily accessible for our users, and easier to maintain for the Database team.
Status: In progress
Item 2: Comply with ISO27001
Implementing the recommendation of the Information Security team for ISO 27001 to provide a structured, auditable framework to meet these evolving obligations and enhance overall information security resilience.
Status: In progress
Community Input on Planning
We want the community to contribute to our plans and suggest additional work items. The Database Working Group (WG) employs a process called Numbered Work Items (NWIs) that allows anyone to suggest work the RIPE NCC should carry out to improve the RIPE Database. A lot of work takes place each quarter to investigate the feasibility of NWIs and plan for their implementation.
Community Input DB-2025#01: NWI-20 - Adjusting contact method requirements and adding new methods
Description : The Database Working Group requested to align requirement levels for contact methods across person and role object types, and additionally to support new contact methods.
Status: Planned. The RIPE NCC has published a Solution Definition and Impact Analysis and expects to implement this feature in Q2.
Community Input DB-2026#01: NWI-21 - Improving identification of RIPE NCC Members and independent resource holders by publishing company registration Numbers
Description : The RIPE NCC Registry team proposed at RIPE 91 to publish the registration number for organisations in the RIPE database, so they can be uniquely identified more easily (excluding natural persons).
Status: Planned. The RIPE NCC has published a Solution Definition and expects to implement this feature in Q2.
Community Input DB-2026#02: UTF-8 in free-text Attributes
Description: The RIPE NCC Database team proposed to allow UTF-8 characters in free-text attributes (i.e. “descr:” and “remarks”).
Status: Planned. The RIPE NCC has published a Solution Definition and Impact Analysis and expects to implement this feature in Q2.
Archived Quarterly Plans
You can find our plans from the previous quarters on this page. The Q2 2026 plans will be archived once we publish the Q3 2026 planning.