- 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 12 May '25

12 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

Atlas UI update - New Internet Maps
by Stephen Suess 01 May '25

01 May '25

Hello Atlas Community, We have just released an update to the UI that completely reworks the Internet Maps section: Root Name Server Instances & RTT to well-known destinations Performance: many times faster than previous maps Sharable URLs with all params Clickable legend tags to filter probe markers Probes on maps are searchable by ID, ASN, Country, IP, Prefix Time travel up to 30 days in the past You can find these maps here: https://atlas.ripe.net/maps/ Over the next couple of months we plan to bring many of the performance improvements of these maps to other areas of Atlas as well as refining and adding to the Internet Maps collection. And as always, we hope you find these changes useful and we welcome your feedback. Kind regards, Stephen Atlas UI

2 2

RIPE Atlas API rate limits
by Huseyn Gambarov 30 Apr '25

30 Apr '25

Hello. While looking for the rate limits defined for the RIPE Atlas API, I found the mail sent by Robert Kisteleki two years ago saying: > The measurement API in particular will impose a limit of 150 queries/second (if done over multiple connections) Can you tell me please, if the requests sent to the Streaming API are also considered in this limit? Thank you. Original mail: https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/thread/7K4JC7ZZN… With regards, Huseyn Gambarov Research Assistant PhD Student in Computer Science Case Western Reserve University

1 0

bulk-email.ripe.net
by Marco Moock 29 Apr '25

29 Apr '25

Hello! Some mails regarding RIPE atlas are being sent via bulk-email.ripe.net. Is there a reason RIPE uses that 3rd party (IPv4-only) service instead of its own infrastructure? -- Gruß Marco

8 12

Newbish DNS question
by Hank Nussbacher 29 Apr '25

29 Apr '25

Perhaps a newbie question: I am doing a DNS measurement and almost all probes return NXDOMAIN (expected), yet one probe returns NOERROR. How can I determine which DNS server it is using to provide a NOERROR? See attached json. Thanks, Hank

4 3

Atlas credits fallen way below zero
by Seth David Schoen 23 Apr '25

23 Apr '25

Hi, I created some rather large measurements a few months ago. I got a notice at some point that I was going to run out of credits and that the measurements would be stopped -- something which has happened to me before. Somehow, it looks like the measurements didn't stop (or maybe did stop and were then resumed), and my account balance has gone very significantly negative before I got around to checking what was going on. I keep getting e-mail notifications warning me that my balance is nearly exhausted, but these notifications (correctly?) state that my balance is already negative, and will run out a negative amount of time into the future. Can I assume this is a backend bug, where some part of the logic for credit exhaustion wrongly assumes that one's balance is currently positive, and then never triggers after it somehow becomes negative? My dashboard page somewhat comically states Daily credit spending currently (approximately) / your limit: 7160665 / 1000000 Daily measurement result flow (approximately) / your limit: 721024 / 100000 I didn't mean to "overdraw" the system or use resources without contributing resources back; I just didn't realize the cost of some particular measurements, and had previously seen that measurements that one's account couldn't afford would in fact be terminated. Can I "declare bankruptcy" and get my balance reset to zero? And can someone take a look at the credit logic to understand how this credit overdraft phenomenon can come about? Thanks!

2 1

Atlas Account Disabled
by cassianoaquino＠me.com 22 Apr '25

22 Apr '25

Hi, I was trying to login to my atlas ripe account and forgot I had multiple authenticators configured and kept trying with the wrong one which gave me an error about the account being disabled to contact "your administrator". Now when I try to login it says "Invalid email address or password". Is there someone who can help me or point me on how to contact "your administrator"? The atlas login email is the same I use here on the mailing list. Thanks in advance!

1 0

how to delete a never used software probe
by Hans Mayer 17 Apr '25

17 Apr '25

Dear All, by a mistake I submitted the wrong SSH key during the installation of a software probe. Therefore I have now in my list of probes a second probe ID which is hidden and was never connected. Querying the Internet tells me Click on your probe and Click the "Write off your probe" function on the probe's detailed information page But when I do so I see an almost empty screen with the probe ID and "This probe was Never Connected" and nothing else. Any help is welcome. Kind regards Hans --

2 2

Decreasing number of probes
by Felix Hoffmann 09 Apr '25

09 Apr '25

Hey, I am currently running multiple scheduled measurements (ids: 85023653, 85023729, 85023782, 85023852). In the wizard, I selected the probes by area with the following settings: WW, 1000 probes. At the beginning of the measurements, mostly all probes reported, but meanwhile the number of probes reporting has decreased constantly. Is there an option to rotate the probes regularly to ensure a certain amount of active probes? Best regards, Felix Hoffmann

5 5

Atlas software probe on FreeBSD
by Marco Moock 09 Apr '25

09 Apr '25

Hello! Are there any people who have the RIPE Atlas software probe daemon running on FreeBSD? I have a virtual machine that could host a probe, although I haven't found any info if the daemon runs there. -- kind regards Marco Send unsolicited bulk mail to 1744132937muell(a)stinkedores.dorfdsl.de

2 1

Monthly probe reports for March 2025 missing?
by ripe＠nurfuerspam.de 07 Apr '25

07 Apr '25

Hi, I don't recall having seen the monthly probe report for March 2025, and also cannot find anything when explicitly looking for them. Did anyone else get the probe report for March 2025? In the past, they usually came in the very early hours of the first day of the month. Thanks! Kind regards, R.

2 2

RIPE Atlas Anchor Certificate Change
by Robert Kisteleki 07 Apr '25

07 Apr '25

Dear colleagues, We will be carrying out planned maintenance on RIPE Atlas anchors to replace the existing Lets Encrypt certificates with self-signed ones. There is no action needed by anchor hosts. The only visible change for users - should they want to visit an anchor URL using their browser - will be the standard notification asking them whether they trust the certificate before proceeding. This change is not expected to have a significant impact on functionality as the HTTPS service on RIPE Atlas anchors is not intended to be accessed by regular users in browsers but from measurements and scripts. Kind regards, Robert Kisteleki

1 0

Software Probe version 5110 released
by Trix Taiclet 02 Apr '25

02 Apr '25

Dear colleagues, We have released a new version of the RIPE Atlas Software Probe, version 5110. This 5110 release contains the following changes: * Added support for Raspberry Pi OS 12 (added Debian 12 arm64 package) * Rewrote GitHub README and BUILD instructions * Display Probe registration instructions during installation for RHEL and Debian * Generate Probe keys after installation without requiring service startup * Using the signing key introduced in 5100 to sign RHEL packages. The current RHEL key is deprecated as of this release. * Fixed compilation error by adding a missing include to telnetd.c (authored by César de Tassis Filho <ctassisf(a)gmail.com>) * Hardened the security of the RIPE Atlas service unit (reported by Marek Küthe <m.k(a)mk16.de>) * Added missing requirement for procps-ng on RHEL9 to RHEL probe package specfile (authored by Robert Scheck <robert-scheck(a)users.noreply.github.com>) * Document runtime options for custom TCP ports (authored by AtlasMUC <AtlasMUC(a)mail.de>) * Fixed typo in GitHub org url for RHEL ripe-atlas-anchor specfile (authored by Pouria Mousavizadeh Tehrani <info(a)spmzt.net>) * Fixed typo in GitHub org url for RHEL ripe-atlas-probe specfile (authored by eeple <m.renusson(a)gmail.com>) This release does not contain any functional changes to the measurement code. You can find more information and instructions on the GitHub repository: https://github.com/RIPE-NCC/ripe-atlas-software-probe/ You might have seen this release before our announcement; we faced an issue with the arm64 repo package, which caused us to delay that specific package and our announcement. Please let us know if you find any issues with this release. Regards, Trix Taiclet & Marios Mavropoulos RIPE NCC

1 0

How to set a probe non-public?
by Robby van de Meulenhof 01 Apr '25

01 Apr '25

Hello, At the moment i have 3 probes. 1 of the 3 probes i would like set non-public. With the new detail page i can't change the Shared Publicy (no checkbox like the old design) I switch to /Legacy Probe Detail/ i can *uncheck Shared Publicy* when i save it a get an error "You cannot make a public probe non-public." I can'tt find how i set a probe to non-public. How i do that? Regards, Robby

2 3

API-Key grants: There were problems with your request
by Bjoern Franke 01 Apr '25

01 Apr '25

Hi, I created a new API key and tried to set some measurements permissions. Yesterday evening and also now I'm only getting "There were problems with your request" and no grants are set. Regards Bjoern

1 0

Missing data in connection and uptime history for probe
by Anton Bobov 21 Mar '25

21 Mar '25

Hello! I am experiencing an issue with incorrect uptime and connection history for my probe (ID: 1006959 https://atlas.ripe.net/probes/1006959/network) I am currently running a software probe on Rocky Linux 8.10, with the probe version 5100. There was a power outage between 2025-03-14 04:25 and 2025-03-14 05:25 (UTC), which seems to have affected the data. I downloaded the connection history for the specified period, and it shows the following entries: seq timestamp (UTC) event stored_timestamp (UTC) ---------------------------------------------------------------------- 1 2025-02-08 23:13:51 disconnect 2025-02-08 23:13:51 2 2025-02-08 23:17:18 connect 2025-02-08 23:17:18 3 2025-03-14 04:25:35 disconnect 2025-03-14 04:25:36 4 2025-03-14 05:25:06 connect 2025-03-14 05:25:06 5 2025-03-14 06:49:19 disconnect 2025-03-14 06:49:19 6 2025-03-14 06:52:46 connect 2025-03-14 06:52:47 7 2025-03-15 22:36:49 disconnect 2025-03-15 22:36:50 8 2025-03-15 22:39:17 connect 2025-03-15 22:39:17 However, entries [2] to [7] are missing from the connection history, and only [1] (last disconnect) and [8] (last connect) are displayed. Additionally, this period is also missing from the uptime history. Could this be a bug, or is there another explanation for this issue? -- Cheers, Anton

2 4