Skip to main content

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.

Q4 2023 Plans and Community Input

Plans
Item Activity Description
1 Service quality monitoring

We want to improve service quality monitoring to provide a more reliable service.
We developed a test framework that helps us structurally identify bugs, which we started to fix in Q4 2022 and continued to work on in Q4 2023.

We have now fixed all the bugs we tracked in 15 of the most popular data calls in 2022.

2 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.

An upgrade of outdated Javascript library dependency in the widget code is a prerequisite for open sourcing.

We finalised the upgrade of jQuery for the widget API and are currently busy rolling it out to production in the most careful way, avoiding any disruptions to external users of RIPEstat widgets.

We expect the work to be completed by Q4 2023.

3 Improved UI testing

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

As part of the update of the client-side software stack of the Widget API, we added two test features to prevent regression and support the UI development efforts. One is an end-to-end testing solution, and the other is helping to automatically spot visual differences in the rendering of the UI in a user’s browser. 

4 Review MLAB data

Some time ago, data calls based on MLAB data were disabled because of changes in the data provisioning. In Q4 2022, we reviewed reintegrating MLAB data into RIPEstat’s data API and UI.

The MLAB-based data calls are back on RIPEstat, and with them are the two RIPEstat widget visualisations: “Observed Network Activity” and “Observed Bandwidth Capacity”.

Reference Input RIPE NCC Reaction
RS-2022-#03 Request to visualise DNS name-to-IP changes similarly to BGPlay.

The assessment of this feature request is pending.

Q3 2023 Plans and Community Input

Plans
Item Activity Description
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.

After the first installation in Q4 2022, we will continue moving smaller backends to the cloud. Generally, we follow the strategy to first work on small, low-impact backends and later move to more complex parts of the service.

2 Service quality monitoring

We want to improve the service quality monitoring to provide a more reliable service.

We developed a test framework that helps us structurally identify bugs, which we started to fix in Q4 2022 and will continue to work on in Q3 2023.
 By the end of 2023 and tracked by an internal metric, we expect to reduce failed requests (up to 0.0125% of total requests or 10k) caused by code errors by 50%.

3 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.

An upgrade of outdated Javascript library dependency in the widget code is a prerequisite for open sourcing. Currently, we are in the process of upgrading the biggest one, which is JQuery. Because of other work - mainly bug fixes to the UI - this item is postponed to Q3.

4 Improved UI testing

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

Our initial estimate to have all basic features covered by Q4 2022 has been moved to Q3 2023 because of necessary bug fixing and improvements to the UI.

5 Review MLAB data

Some time ago, data calls based on MLAB data were disabled because of changes in the data provisioning. In Q4 2022, we reviewed reintegrating MLAB data into RIPEstat’s data API and UI.

Our initial plan for Q1 2023 has been moved to Q3 to deliver better maintainability in the backend logic.

Reference Input RIPE NCC Reaction
RS-2022-#03 Request to visualise DNS name-to-IP changes similarly to BGPlay.

The assessment of this feature request is pending.

Q2 2023 Plans and Community Input

Plans
Item Activity Description
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.

After the first installation has been done in Q4 2022, we will continue moving smaller backends to the cloud. Generally, we follow the strategy to first work on small, low-impact backends and later move to more complex parts of the service.

2 Service quality monitoring

We want to improve the service quality monitoring to provide a more reliable service.

We developed a test framework that helps us structurally identify bugs, which we started to fix in Q4 2022 and will continue to work on in Q2 2023.
 By the end of 2023 and tracked by an internal metric, we expect to reduce failed requests (up to 0.0125% of total requests or 10k) caused by code errors by 50%.

3 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.

An upgrade of outdated Javascript library dependency in the widget code is a prerequisite for open sourcing. Currently, we are in the process of upgrading the biggest one, which is JQuery. Because of other work - mainly bug fixes to the UI - this item is postponed to Q2.

4 Improved UI testing

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

Our initial estimate to have all basic features covered by Q4 2022 has been moved to Q2 2023 because of necessary bug fixing and improvements to the UI.

5 Review MLAB data

Some time ago, data calls based on MLAB data were disabled because of changes in the data provisioning. In Q4 2022, we reviewed reintegrating MLAB data into RIPEstat’s data API and UI.

Our initial plan for Q1 2023 has been moved to Q2 to deliver better maintainability in the backend logic.

6 Ability to adjust colours in BGPlay

Triggered by a public feature request, we want to provide an ability to adjust colours in BGPlay to make it more accessible to users with colour vision deficiency.

We expect this to be done in Q2 2023.

Community Input
Reference Input RIPE NCC Reaction
RS-2022-#03 Request to visualise DNS name-to-IP changes similarly to BGPlay.

The assessment of this feature request is pending.

RS-2023-#01 Request to alter the colours in BGPlay

Added to quarterly planning (item 6).

Q1 2023 Plans and Community Input

Plans
Item Activity Description
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 deployed a single-table backend to AWS and have started to collect experience with its maintenance. Generally, we follow the strategy to first work on small, low-impact backends and later move to more complex parts of the service.

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.

3 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.

An upgrade of outdated Javascript library dependency in the widget code is a prerequisite for open sourcing. Currently, we are in the process of upgrading the biggest one, which is JQuery. We expect this to be done by the end of Q1 2023.

4 Improved UI testing

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

The work started in Q2, and we expect to have all basic features covered at the end of Q4.

5 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.

6 Extending RIPEstat UI for Zonemaster

Work was completed in Q1 2023.

We plan to extend the RIPEstat UI for the Zonemaster backend to allow pre-delegation checks. This work will enable us to replace the Zonemaster UI for our on-premise installation and provide a more consistent user experience.

We expect this to be done in Q1 2023.

Community Input
Reference Input RIPE NCC Reaction
RS-2022-#03 Request to visualise DNS name-to-IP changes similarly to BGPlay.

The assessment of this feature request is pending.

Q4 2022 Plans and Community Input

Plans
Item Activity Description
1 Migration to the cloud

Work started in Q2 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.

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.

3 Data API revamp

Work is on hold.

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

We decided to pause the work on this item until service quality monitoring (item 2) has reached a final state.

4 Open-sourcing the RIPEstat widgets

Work started in Q2 2022.

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.

5 Improved UI testing

Work started in Q2 2022.

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

We expect to have all basic features covered by Q4 2022.

6 Improve the blocklist feature

Work was completed 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 finished replacing the old blocklist feature with a new one that does not include controversial blocklists. This has been done in all RIPEstat UIs.

We strive to add more blocklists, but we do this as part of maintenance and hence close this item on the planning.

7 Review MLAB data

Work started in Q2 2022.

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.

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 was completed (item 6).
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.

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.