Hosting a RIPE Atlas probe on your network

Have you heard about Ripe Atlas project ?
RIPE Atlas
RIPE NCC is running an excellent project called RIPE Atlas from few years. This is one of the largest distributed network measurement projects where thousands of users host small devices called RIPE Atlas Probes on their networks, home connections, data centers etc. These probes do measurement under both public and private category and make that data available publicly for use by network engineers and helps in optimising routing.

These can help other users to run ping, trace route etc from other networks to detect latency, routing issues.

I have been hosting few of these and wanted to check with other users in India if they can host some devices.
It does not have any major requirements and just need USB power, uses 4-5kbps internet for tests and be available online 24/7.

I have 2 devices which I can share at this time.

To setup new device will need your email(invite and account for accessing online tools) and ISP details(ASN) to set it up.

Some more explaining how Ripe Atlas works and can help Network users/teams
RIPE Atlas - Wikipedia
RIPE ATLAS and Benefits of Hosting it in your Indian ISP Network | Mumbai IX Blogs
RIPE Atlas Probe Stats
RIPE Atlas Measurements
 
Click to expand...
Can someone guide me as to how to understand/interpret atlas measurements. I did a traceroute measurement for 2 days to steam CDN server for all probes in India.

atlas.ripe.net

RIPE Atlas - RIPE Network Coordination Centre

RIPE Atlas is the RIPE NCC's main Internet data measurement system.
atlas.ripe.net atlas.ripe.net

Thanks in advance!
 
@deezcnuts Access the 'Latest Results' menu and you can click on the info icon
Screenshot 2020-08-03 at 1.44.25 PM.webp
which is besides every traceroute measurement. For example.
Screenshot 2020-08-03 at 1.43.03 PM.webp


If you or anyone else is interested, there is a presentation on RIPE Atlas at INNOG3. You can check the schedule here and register here
 
@swapneelp Oh wow! That's quite a lot of information! Pretty amazing. Don't know why I missed the little 'i'. Was mostly looking into maps.

Looks like most of the pings to steamcdn-a.akamaihd.net are above 150ms. Probably an EU server. I'll try another measurement if I find the ip/domain for Indian/SEA servers.

Quite cool actually :D
Thanks!
 
Yup this is true, the domain will resolve to different IP based on the ISP and Location of IP Address. For example, on my ISP steamcdn-a.akamaihd.net resolves to 23.223.243.64 rather than 212.247.14.18 . In @deezcnuts measurement page RESOLVED ON PROBE is set to false (this is by default), so it traceroutes whatever IP Address is returned by RIPE Servers (which is 212.247.14.18) rather than probe itself (which varies on probe location).

@Smh set RESOLVED ON PROBE to True which gives the accurate traceroute depending on location of probe.

I think (though I'm not sure) its because of this EDNS Client Subnet - Wikipedia
 
That is quite interesting! Thank you all for your replies!

I'll try some more CDN measurements using resolve on probe selected.
Netflix, prime, steam etc. Let me know if you have other suggestions for measurements. :D
 
It's the local Unbound resolver on PFSENSE. My primary probe doesn't have the tag RIPE Atlas despite being connected to same router.

The ISP of the probe I mentioned before does hijack DNS though. So maybe that's the issue?
 
You must log in or register to reply here.
Back