PathCache
Running traceroutes from arbitrary sources to arbitrary destinations is an expensive process. PathCache reuses existing measurements on RIPE Atlas to gather information about the Internet that users can subscribe to. The benefits are two-fold:
- The users do not have to spend their own measurement budget to run traceroutes.
- RIPE's nodes can be more efficiently utilized since redundant traceroutes will be avoided.
Interacting With PathCache
We have exposed a REST API for users to interact with PathCache. This is an easy to use (and work in progress) interface. As of now, our API:
Given an AS number (asn), returns the graph constituted by paths to the asn based on recent data plane measurements.
- Endpoint: /asn
-
GET: curl -i http:path-cache-server:port/13812
Given two AS numbers (asn1, asn2), returns the path from asn1 to asn2 based on recent data plane measurements.
- Endpoint: /asn1-asn2
-
GET: curl -i http:path-cache-server:port/13812-174
Provides an endpoint to get daily updates made to the Internet AS graph based on the measurements done in the last 24 hours.
- Endpoint: /daily-update
-
GET: curl -i http:path-cache-server:port/daily-update
All responses are in JSON.
Development
As you can see, PathCache is under active development. We hope to improve it incrementally based on how it gets used by us and the community.
Authors and Contributors
Support or Contact
If you are having troubles using PathCache, feel free to contact us. If you plan to write scripts that query our servers a lot, do let us know in advance so we can monitor how well we handled it (and improve).