- ripe-atlas - mailman.ripe.net

v3 probe stuck with BADMD-APP
by Radu Anghel 11 Nov '25

11 Nov '25

hi, one of the v3 probes i spread around the universe that is 12+ years old just had another USB stick die after a power failure. i have tried reviving it by replacing the stick (tried at least 3 different ones), but for some reason it does not work as when i previously replaced it. i also tried different partitioning on the 16/32gb sticks: one single partition fat32/ntfs/ext4, no partitions at all. the probe does not format the new stick or do anything with it except reporting it to the controller, i see "registrations" in the event log with info about the USB that is plugged in. after that it just keeps repeating the BADMD-APP SOS DNS query. no blinky light on the stick to show activity. tried leaving it for more than 8h with the new stick, tried plugging in the stick 10+ minutes after probe booted, tried booting with the fresh stick plugged in. no changes in behaviour. also replaced the power source/cable, that did not help either. is there anything else i can try to revive it? thanks!

3 2

A system tag for DNS resolution of "other types"?
by Stephane Bortzmeyer 11 Nov '25

11 Nov '25

I see a probe (31874) which can resolve A and AAAA (and has system tags for that) but always SERVFAIL for TXT records. % blaeu-resolve --probes 31874 --type TXT ietf.org [ERROR: SERVFAIL] : 1 occurrences Test #136741617 done at 2025-11-08T16:31:22Z % blaeu-resolve --probes 31874 --type A ietf.org [104.16.44.99 104.16.45.99] : 1 occurrences Test #136741646 done at 2025-11-08T16:31:36Z (You can check with other domains such as ripe.net.) Suggestion: a system tag "Resolves TXT".

2 1

Yeh, my v5 probe birthday
by Colin Johnston 10 Nov '25

10 Nov '25

Sent from my iPhone

1 0

IXP Country jedi seems to be down
by Vasileios Giotsas 07 Nov '25

07 Nov '25

Hi all, It seems that the data endpoints for the IXP Country jedi website are down. The website itself (https://jedi.ripe.net<https://jedi.ripe.net/latest/AT/geopath/index.html>) is loading, but none of the graphs are loading, e.g. the https://jedi.ripe.net/latest/AT/geopath/geopath.v4.json is returning 404 (and all other json data paths) so the plots aren't loading. Just thought to bring it to your attention because these data are very useful. Best, Vasilis Giotsas

3 2

Obsolete builtin measurements
by Ernst J. Oud 07 Nov '25

07 Nov '25

2 2

BIG Atlas UI update for 2025-11-06
by Stephen Suess 06 Nov '25

06 Nov '25

Hello Atlas friends, We have just released a pretty big update to the Atlas frontend, with lots of new features. Here are some of them: Probe Connectivity use case - Visualise Internet connectivity by analyzing RIPE Atlas probe connection states over time. This tool helps identify potential outages and connectivity issues across different networks and regions. Here is an example link showing a power outage in Chile earlier in the year: https://atlas.ripe.net/use-cases/probe-connectivity/?method=country&start=1… Khipu: export image and data - There is now an export button in the toolbar allowing you to export Khipu visualisations as pngs, and menu items for exporting your filtered or full measurement data source in either json or csv formats Khipu: multi term path filter - You can now use multiple terms in the path filter to further refine your path selection Khipu: country filter improvements - You can now filter by continent, search for a country, or invert your country selection Clone a measurement (from detail and listing pages) - You can now clone existing measurements (that are stopped and not system tagged) by clicking on a clone icon in the measurements listing page or next to the heading on any valid measurement detail page. This will open a new measurement form with all settings filled in except for timing. Measurement Form: duplicate definition - Within the measurement form itself, you can now duplicate a measurement definition to help copy similar configurations. Recheck DNS option (in measurement form and measurement detail manage tab) - This setting (on by default for periodic measurements that don't resolve on probe and are targeting a domain) will recheck the domain resolution every 24 hours and update the measurement. For the full list of what is new, has changed or been fixed, please see the release notes here: https://atlas.ripe.net/docs/releases/website_index/2025-11-06 We welcome your feedback, please let us know if you have any questions, comments, or encounter any issues in the new update. Kind regards, Stephen Atlas UI

1 0

khipu view "enhancements"
by Hendrik Visage 31 Oct '25

31 Oct '25

Good day, reference https://atlas.ripe.net/khipu/134895113/ip I’d love to have the following to make it useful for my case: - Ignore “unsuccessful” not reaching the target In these case I do expect some connectivity issues, and those I’d like to look in, but I want to focus on the main issue in this case is RTT anomalies and routing issues so do want to ignire those. - focus on specific intermediate/IXP hops Ie. want to select some hops and have the radials around them only

2 3

soft probe sending out UDP frames
by Hans Mayer 30 Oct '25

30 Oct '25

Dear All, month ago I installed a soft probe. I have running ripe-atlas-common 5110, ripe-atlas-probe 5110, ripe-atlas-repo 1.5-3 on Debian 12 bookworm. These days I realised something where I need some explaination. When I look at the types of measurements then I would expect a certain amount of services that can go out. Like ping, traceroute, dns, tls, http and ntp. Now I saw that the probe sends out to about 89 different IP addresses ( IPv4 as well IPv6 ) UDP frames. I looked for a period of about a day. Each destination is probed with a specific port number. And this again and again all over the time. So each combination of destination IP and destination port is unique. The ports are high ports above 32k and as far as I can see there is never a reply. (Probably not necessary for UDP) There are a little bit more than 60 frames per hour. That's about 1 UDP frame per minute. Not to say, if I switch off the ripe-atlas.service this phenomena doesn't happen. Is there any explanation for this behaviour ? I can only imagine that these destinations are monitoring servers from ripe and my soft probe says: "hello, I am still alive ! ". ( I didn't dig into the UDP frame itself) Kind regards Hans -- The destination IP's are well distributed around the world.

2 2

Software Probe version 5120 released
by Trix Taiclet 29 Oct '25

29 Oct '25

Dear colleagues, We have released a new version of the RIPE Atlas Software Probe, version 5120. This 5120 release contains the following main changes: * Add support for Debian 13 (#129) * Add support for Enterprise Linux 10 (#129) * Measurement code * Add local timestamp to HTTP POST header * Add local clock value to SOS message * Set Atlas-specific ref-id in NTP packets (authored by Joachim Kross #132) * `NTP_4G` instead of `4294967296.0` (authored by Marco Davids #131) * Fix NTP offset calculations (reported by Marco Davids and Giovane Moura #130) * Other * Improve OpenWrt support with documentation fixes and and reduced dependencies (hostname) * Add missing dependencies to Debian package files (libcap2-bin, ca-certificates) * Improve repo package building (rules.mk/.spec file) for clarity and Git tag support * Fix typo in GitHub org url for RHEL ripe-atlas-repo specfile * Fix casing of OpenWrt (authored by Goetz Goerisch #128) * Internal CI changes * Signed commit (bdf1b93) using production GPG key The full release notes are available on the docs: https://atlas.ripe.net/docs/releases/firmware_index/5120 Please note that this release only applies to software probes, an update will be released for hardware probes once OpenWrt consolidation work is complete. You can find more information and instructions on the GitHub repository: https://github.com/RIPE-NCC/ripe-atlas-software-probe/ https://github.com/RIPE-NCC/ripe-atlas-software-probe/releases/tag/5120 Please let us know if you find any issues with this release. Regards, Trix Taiclet & Marios Mavropoulos RIPE NCC

1 0

Probe Reactivation?
by Cornelius Keck 29 Oct '25

29 Oct '25

My first-generation probe (1198) has been down for 2 or so years. Managed to get it going again inasmuch it pings the outside world. Current status at https://atlas.ripe.net/probes/1198/overview shows it to be abandoned, though it does SOS-ping. What could be done to change its state to active? Thx! -Cornelius

4 4