- ripe-atlas - mailman.ripe.net

traceroute with specific udp target port
by julien.piccaluga 25 Jun '25

25 Jun '25

Hello, I’m developing a Proof of Location project and have a use case requiring a traceroute on a specific UDP port. It appears that traceroute only supports selecting a target port for TCP. Are there any undocumented or lesser-known methods to achieve this with UDP? Regards Julien Piccaluga Mobile: +41 (0) 78 832 36 20 Envoyé avec un e-mail sécurisé [Proton Mail](https://proton.me/mail/home).

1 0

Probe location API
by Ray Bellis 25 Jun '25

25 Jun '25

My RIPE visualiser for the DNS root system has previously been using this endpoint, that now returns an error: https://atlas.ripe.net/api/v2/cartography/locations Is there another I can use in its place with the same output? thanks, Ray

2 4

RIPE Atlas measurements broken since yesterday
by Lucas Rolff 24 Jun '25

24 Jun '25

Hello, It seems like creating new measurements through RIPE Atlas has been broken since yesterday afternoon, while the given measurement is created, it will simply return "Error fetching data", regardless of how long waits. e.g. a traceroute towards 8.8.8.8: https://atlas.ripe.net/measurements/111806687/overview Is RIPE aware of this issue? And any possible ETA when it will work again? - Lucas Rolff

2 2

Request for RIPE Atlas Credits for Geo-Staking Research
by julien.piccaluga 17 Jun '25

17 Jun '25

Hello, I’m currently working on a project related to proof of location for blockchain Proof-of-Stake node decentralization. To support my testing, I would like to run a series of measurements using the RIPE Atlas platform. If anyone has spare credits and would be willing to share, I’d greatly appreciate your support. Thank you in advance for your generosity. Best regards, Julien Piccaluga Mobile: +41 (0) 78 832 36 20 Envoyé avec un e-mail sécurisé [Proton Mail](https://proton.me/mail/home).

2 1

Request for RIPE Atlas Credits for Oceanic Connectivity Project
by Andrew 08 Jun '25

08 Jun '25

Him I’m Andrew and I'm currently working on a project aiming to test and analyze connectivity across the Atlantic and Pacific Oceans. The goal is to measure latency, reliability, and routing performance to better understand intercontinental connectivity and network behavior. To achieve a comprehensive perspective, we're planning extensive measurements using RIPE Atlas probes. However, we're limited by available credits. If anyone could provide RIPE Atlas credits to support this effort, it would be greatly appreciated. My RIPE NCC account email is: andrew(a)izongrp.com Thank you Andrew

4 5

eperd segaults on software probe?
by Alexander Bochmann 07 Jun '25

07 Jun '25

Hi, on this one software probe I run, I've noticed a bunch of segfaults in eperd between May 19 and May 21: > May 19 11:23:51 kernel: eperd[1705]: segfault at 0 ip 00007a7e28e95ace sp 00007ffdaa698030 error 4 in libc.so.6[7a7e28e45000+155000] likely on CPU 1 (core 1, socket 0) > May 19 13:23:50 kernel: eperd[2119167]: segfault at 0 ip 0000793ee0becace sp 00007ffc83ca3bd0 error 4 in libc.so.6[793ee0b9c000+155000] likely on CPU 1 (core 1, socket 0) > May 19 13:53:52 kernel: eperd[2168145]: segfault at 0 ip 000070f2b71ecace sp 00007fff868d06d0 error 4 in libc.so.6[70f2b719c000+155000] likely on CPU 1 (core 1, socket 0) > [..] > May 21 07:53:55 kernel: eperd[3181618]: segfault at 0 ip 00007dfe4bc95ace sp 00007fffeaf5b420 error 4 in libc.so.6[7dfe4bc45000+155000] likely on CPU 1 (core 1, socket 0) > May 21 08:54:03 kernel: eperd[3218383]: segfault at 0 ip 00007dba7970cace sp 00007fff1d145490 error 4 in libc.so.6[7dba796bc000+155000] likely on CPU 1 (core 1, socket 0) > May 21 09:24:04 kernel: eperd[3243867]: segfault at 0 ip 000076d0a8becace sp 00007fff2ffb2b20 error 4 in libc.so.6[76d0a8b9c000+155000] likely on CPU 1 (core 1, socket 0) Software probe version is 5110 on Debian 12. I haven't found anything similar before or after. Coredumps are not enabled on that system, and I don't notice anything unusual in the service logs (except that eperd has been restarted), so that's pretty much the information I have... Has anyone else seen something like that? Alex.

1 0

Best way to download bulk data older than a month?
by Vasileios Giotsas 02 Jun '25

02 Jun '25

I'm trying to download the RIPE Atlas traceroutes for a day that is older than one month. Given that the FTP repository publishes only results from the last month, I need to use the API. So, what I'm doing is to list of measurement IDs for a given data and then for each ID I do a GET for the results of that ID. The code is here: https://github.com/vgiotsas/RIPEAtlas_Queries/blob/main/download_atlas_trac… However, often some downloads time out and when I'm trying to resume it using the Range header it seems that the API doesn't support it and the download starts over until it fails again halfway through the download. Is there a better way to do such bulk downloads? Or at least to resume failed downloads? Thanks!

4 6

Anchor time sources
by Tim Chown 27 May '25

27 May '25

Hi, I assume the anchor nodes take their time via NTP and a general NTP pool? Have there been studies of time drift on anchors? Is there a way to configure a specific set of NTP sources? Thanks, Tim

3 2

Atlas reported uptime vs OS reported uptime
by Alexander Männel 26 May '25

26 May '25

Hi atlas folks, is there a way to get the operating system uptime of a probe? The reason I'm wondering is that I want to differentiate a shut down probe (i.e. power outage, operator reasons) from a disconnected probe (i.e. Internet connectivity lost). Depending on the goal of a measurement these two cases should be considered differently. The one way I think this is currently possible is to look for results that the probe has uploaded from its local buffer after it has regained network connectivity. In case of a disconnected probe, there will be measurement results during the outage but not if the probe was fully turned off. This approach is however a bit hacky and requires you to query the event log and align that with the measurement results. Depending on how often your measurement runs, you might have to query data from the built-ins as well. Of course you can always try to look at probes from the same region/AS and see if they faced outages, but this requires a lot of additional data to be queried and will not be 100% accurate. I understand that this probably is only relevant for a subset of all probes, but also collecting the uptime as tracked by the OS would be a simple fix to easily differenciate between different disconnect reasons. Regards, Alexander Männel -- Alexander Männel TU Dresden, Chair of Distributed and Networked Systems https://tu-dresden.de/cs/netd

1 0

Ripe Probes clock update
by Giovane C. M. Moura 13 May '25

13 May '25

Hi Atlas folks, I was wondering if there is an update on how Atlas probes sync their clocks from the article from 10 years ago[0]. * Anchors: `pool.ntp.org` * v1: fallback mechanism using HTTP * v2 : ntpclient (but which ntp servers?) * v3: opentpd (but which ntp servers)? What about newer probes version? v4? v5? vms? Thanks, /giovane [0] https://labs.ripe.net/author/philip_homburg/ntp-measurements-with-ripe-atla…

2 1