Archived Plans

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.

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.

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.

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.

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.

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.

The assessment of this feature request is pending.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

Work started in Q2 2022 and continues in Q4 2022.

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

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.

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.

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.

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.

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.

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.

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.

Work started in Q2 2022 and continues in Q4 2022.

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

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.

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.