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

Archived Plans

You can find our plans from previous quarters along with requests from the community on this page. We are updating this page at the end of each quarter.


Q3 2022 Plans and Community Input

Plans
Item Activity Description
1 Migration to the cloud

Work started in Q2 2022 and continues in Q4 2022.

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.

2 Service quality monitoring

Work started in Q2 2022 and continues in Q4 2022.

We want to improve 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.

3 Data API revamp

Work started in Q2 2022 and continues in Q4 2022.

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.

4 Open-sourcing the RIPEstat widgets

Work started in Q2 2022 and continues in Q4 2022.

We will make the source code of RIPEstat widgets available for the community.

We plan to open-source the RIPEstat widgets as part of sustainable long-term maintenance of the old RIPEstat UI.

5 Improved UI testing

Work started in Q2 2022 and continues in Q4 2022.

We want to implement automatic UI testing to create a more reliable UI.

6 Improve the blocklist feature

Work started in Q2 2022 and continues in Q4 2022.

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.

7 ROAs in Routing Consistency

Work started in Q2 2022 and was completed in Q3 2022.

Based on a feature request, we wanted to show RPKI ROAs in the Routing Consistency UI (UI2020). The feature is now available in the RIPEstat UI and in the RIPEstat widget for Prefix and AS Routing Consistency.

Community Input
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 7).
RS-2022-#03 Request to visualise DNS name-to-IP changes similarly to BGPlay. We are currently assessing whether we would be able to accommodate this request in the future.

Q2 2022 Plans and Community Input

Plans
Item Activity Description
1 Migration to the cloud

Work started in Q2 2022 and continues in Q4 2022.

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. The first results are expected to be available in Q3.

2 Service quality monitoring

Work started in Q2 2022 and continues in Q4 2022.

We want to improve 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.

3 Data API revamp

Work started in Q2 2022 and continues in Q4 2022.

We are revamping the Data API to make the growing number of data calls more consistent and easier to use.

4 Feature Parity on the old and new UI

Work started in Q3 2021 and was completed in Q2 2022.

The remaining features that were only available in the old UI were implemented in the new UI.

5 Open-sourcing the RIPEstat widgets

Work started in Q2 2022 and continues in Q4 2022.

We will make the source code of RIPEstat widgets available for the community as part of sustainable long-term maintenance.

We plan to open-source the RIPEstat widgets as part of sustainable long-term maintenance of the old RIPEstat UI.

6 Improved UI testing

Work started in Q2 2022 and continues in Q4 2022.

We want to implement automatic UI testing to create a more reliable UI.

7 Improve the blocklist feature

Work started in Q2 2022 and continues in Q4 2022.

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.

8 ROAs in Routing Consistency

Work started in Q2 2022 and was completed in Q3 2022.

Based on a feature request, we wanted to show RPKI ROAs in the Routing Consistency UI (UI2020). The feature is now available in the RIPEstat UI and the RIPEstat widget for Prefix and AS Routing Consistency.

Community Input
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 7).
RS-2022-#02 Request to show all the RPKI ROAs in the prefix routing consistency widget. The work was completed in Q3 2022 (item 8).
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.