2. Christian Teuschel | APNIC 46 | September 2018 !2
What is RIPEstat?
• Open data platform for RIPE NCC data
- RIPE Database, RIS and RIPE Atlas
• Information service for Internet-related data
• Insight through statistics!
3. Christian Teuschel | APNIC 46 | September 2018 !3
RIPEstat Data Sources Available
• More than 25 different datasets:
- RIPE Database (INR, IRR) and other RIRs
- BGP routing data (RIS)
- RIPE Atlas, M-Lab, Speedchecker, etc.
- Geolocation
- Blacklist
- More details at https://stat.ripe.net/data-sources
• New datasets are constantly added!
…
4. Christian Teuschel | APNIC 46 | September 2018 !4
RIPEstat Concept
• Initial concept (2010) was a one-stop-shop for
Internet-related data
5. Christian Teuschel | APNIC 46 | September 2018 !5
RIPEstat APIs
• https://stat.ripe.net
• RIPEstat widget API
• RIPEstat data API
- https://stat.ripe.net/data/routing-status/data.json?
resource=…
6. Christian Teuschel | APNIC 46 | September 2018 !6
RIPEstat Data API
• JSON-RPC API
- E.g. https://stat.ripe.net/data/prefix-overview/data.json?
max_related=50&resource=193.0.20.0%2F23
• More than 50 data calls
• Documentation:
- https://stat.ripe.net/docs/data_api
7. Christian Teuschel | APNIC 46 | September 2018 !7
RIPEstat Widget API
• HTML5/CSS/JS applications
• Standard Javascript
- JQuery
- Require.js
• More than 50 widgets
• Documentation
- https://stat.ripe.net/docs/widget_api
8. Christian Teuschel | APNIC 46 | September 2018 !8
RIPEstat Widget API
• Building blocks of RIPEstat web interface
https://stat.ripe.net
9. Christian Teuschel | APNIC 46 | September 2018 !9
RIPEstat Widget API
• Widgets are embeddable on webpages
• ~10k external webpages visible on a weekly
basis
10. Christian Teuschel | APNIC 46 | September 2018 !9
RIPEstat Widget API
• Widgets are embeddable on webpages
• ~10k external webpages visible on a weekly
basis
11. Christian Teuschel | APNIC 46 | September 2018 !9
RIPEstat Widget API
• Widgets are embeddable on webpages
• ~10k external webpages visible on a weekly
basis
HTML page
12. Christian Teuschel | APNIC 46 | September 2018 !10
Usage of RIPEstat
• RIPEstat is popular!
- Daily requests range from 50 to 60 million
- More than 1.5 million unique clients/IPs (daily)
13. Christian Teuschel | APNIC 46 | September 2018 !10
Usage of RIPEstat
• RIPEstat is popular!
- Daily requests range from 50 to 60 million
- More than 1.5 million unique clients/IPs (daily)
Most requested:
1. Routing data
2. Registry data
14. Christian Teuschel | APNIC 46 | September 2018 !11
Operation of RIPEstat
• Operational requirements
- Monitoring
15. Christian Teuschel | APNIC 46 | September 2018 !12
Operation of RIPEstat
• Operational requirements
- Front-end capacity
16. Christian Teuschel | APNIC 46 | September 2018 !13
Operation of RIPEstat
• Operational requirements
- Back-end capacity
17. Christian Teuschel | APNIC 46 | September 2018 !14
The way ahead with RIPEstat!
• Improve system stability
- Extend system capacity
• Update UI
- Mobile friendliness
• Reach out and cooperate with other RIRs
- Global operation for a global information system
18. Christian Teuschel | APNIC 46 | September 2018 !15
RIR Cooperation
• RIPEstat has a very diverse user base:
19. Christian Teuschel | APNIC 46 | September 2018 !16
RIR Cooperation
• Despite this diverse user base, users from
other RIR regions are underrepresented
• Possible reasons:
- Lack of knowledge about the service
- Language barrier
- Not addressing local topic
• We believe we can improve these points
through cooperation with other RIRs
20. Christian Teuschel | APNIC 46 | September 2018 !17
Cooperation Proposal with LACNIC
• Phase 1
- Customisation of the UI to LACNIC’s design
- Localisation of textual content
• Phase 2
- Cooperation on system operation and dataset provisioning
- Example for dataset provisioning: collaboration on BGP
route collectors between APNIC, LACNIC and RIPE NCC
(already ongoing)
- Phase 1 and 2 are independent for data set provisioning
21. Christian Teuschel | APNIC 46 | September 2018 !18
Phase 1 Details
• Customisation of the UI to LACNIC’s design
- The goal is to provide UI that reflects the affiliation to
LACNIC. Users that go to stats.lacnic.net will see RIPEstat
loaded with a LACNIC customised template e.g. LACNIC
logo, header and footer. In the simplest case this requires a
DNS entry for stat.lacnic.net pointing to RIPEstat and
adaptions in the UI logic.
• Localisation of textual content
- The text that appears in RIPEstat widgets would be
translated to Spanish and Portuguese. This would require
language support in RIPEstat and the translation efforts.
22. Christian Teuschel | APNIC 46 | September 2018 !19
Benefits
• Improved usability for users in LACNIC region
- Catering for regional information requirements
- Removing language barrier
- Access to regional datasets
- Ability to show and share local events
- Establishing feedback channel for regional matter to
RIPEstat
23. Christian Teuschel | APNIC 46 | September 2018 !20
Remarks
• LACNIC is a good candidate for this project
because:
- With English, Spanish and Portuguese the number of
languages is small enough for this project
- Agustin Formoso (R&D engineer at RIPE NCC) used to
work for LACNIC and his knowledge is of tremendous help
to this project
- Daniel Karrenberg already started to create ties between
the two RIRs
24. Christian Teuschel | APNIC 46 | September 2018 !20
Remarks
• LACNIC is a good candidate for this project
because:
- With English, Spanish and Portuguese the number of
languages is small enough for this project
- Agustin Formoso (R&D engineer at RIPE NCC) used to
work for LACNIC and his knowledge is of tremendous help
to this project
- Daniel Karrenberg already started to create ties between
the two RIRs
Will APNIC join
our efforts?