You are here: Home > Get Support > Documentation > Quarterly Planning > RIPEstat

RIPEstat Quarterly Planning

This page details the work we'll do on RIPEstat in the coming quarter, how you can give your input on that work and our reaction to that input.

We have three objectives in publishing our quarterly planning:

We want to be transparent about the work we are doing
We want your input on that work and our planning, and we want to document that input, and let you know if and when we can add your suggestions to our planning
We want an open dialogue with members and community on developments around RIPEstat

We launched this initiative in Q2 2022, 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.

If you have any suggestions on how we can improve RIPEstat, you can share them through the RIPEstat Feature Tracker.

We will update this page as our activities progress and continue to share updates on RIPE Labs, on the RIPE NCC Membership Discussion and MAT Working Group (WG) mailing lists, and at RIPE Meetings and other events.

Q4 2022 Plans

Last Updated: 26 September 2022

Item	Activity	Description	Status
1	Migration to the cloud	We are moving parts of RIPEstat to the cloud to make our infrastructure more efficient and resilient and reduce latency for our global user base. We have started with small, low-impact backends and plan to move to more complex parts of the service later. Currently, we are testing single-table backends in containers.	In progress Work continues from Q2 2022.
2	Service quality monitoring	We want to improve the service quality monitoring to provide a more reliable service. We started with specification testing for the Data API and will continue over the course of 2022.	In progress Work continues from Q2 2022.
3	Data API revamp	We are revamping the Data API to make the growing number of data calls more consistent and easier to use. A higher focus on the service quality monitoring (item 2) delayed this work item, but we expect the first public outcome in Q4 2022.	In progress Work continues from Q2 2022.
4	Open-sourcing the RIPEstat widgets	We will make the source code of RIPEstat widgets available for the community as part of sustainable long-term maintenance. We are currently reviewing the code base and expect this to continue in Q4 2022.	In progress Work continues from Q2 2022.
5	Improved UI testing	We want to implement automatic UI testing to create a more reliable UI. We expect to have all basic features covered by Q4 2022.	In progress Work continues from Q2 2022.
6	Improve the blocklist feature	Triggered by input from the Anti-Abuse WG, we are improving the blocklist feature on RIPEstat. A renaming of the service offering already happened in 2021. In Q3 2022, we started reviewing general terms and conditions for adding new blocklists that are more flexible. In Q4 2022, we expect to replace the old blocklist feature with the new one.	In progress Work continues from Q2 2022.
7	Review MLAB data	Former data calls providing insights based on MLAB data have been disabled for some time. In Q4 2022, we want to review the possibility of reintegrating the data into RIPEstat’s data API and UI.	In progress

Community Input on Planning

We want the community to contribute to our plans and suggest additional work items. Please share your comments with us via the RIPEstat Feature Tracker or post them on the RIPE NCC Membership Discussion and MAT WG mailing lists. And we'll be monitoring all the other channels where people talk about these services.

When we receive feedback that can significantly impact our planning or that needs a further response, we will add it to the table below.

Reference	Input	RIPE NCC Reaction
RS-2022-#01	Request to improve the blocklist feature. For more information, check the Anti-abuse WG mailing list archives.	The work has already started and has been added to the planning (item 6). We first recorded this request in Q2 2022.
RS-2022-#03	Request to visualise DNS name-to-IP changes similarly to BGPlay.	We are currently assessing whether we will be able to accommodate this request in the future. We first recorded this request in Q2 2022.

Reference

Input

RIPE NCC Reaction

RS-2022-#01

Request to improve the blocklist feature.

For more information, check the Anti-abuse WG mailing list archives.

The work has already started and has been added to the planning (item 6).

We first recorded this request in Q2 2022.

RS-2022-#03

Request to visualise DNS name-to-IP changes similarly to BGPlay.

We are currently assessing whether we will be able to accommodate this request in the future.

We first recorded this request in Q2 2022.

Archived Quarterly Plans

You can find our plans from the previous quarters on this page. The Q4 2022 plans will be archived once we publish the Q1 2023 planning.