- ripe-atlas - mailman.ripe.net

Credit sponsorship for research project
by Lennart Kloock 15 Dec '25

15 Dec '25

Hello everyone! I'm currently working on a university research project to detect BGP hijackings. For that it would be very helpful to use the Atlas platform to collect data from different points of view as it provides exactly the tools that I need. I would really appreciate if someone could support me by providing some credits to my account registered with s74lkloo(a)uni-bonn.de. Thank you very much, Lennart Kloock

3 4

Call for software project proposals (TU Delft)
by Giovane C. M. Moura 12 Dec '25

12 Dec '25

Folks, ## TL;DR: ``` if project_idea_exists and time_remaining <= 0: upload_to_students("https://sp.pages.ewi.tudelft.nl/site/") see_previous_year_project("https://ntpinfo.sidnlabs.nl") print("it uses RIPE Atlas") print("Deadline: Sunday March 15th 2026.") else: coffee.refill() ``` ## Longer version If you have a nice project idea but no time to develop, you could consider to "outsource" it to a group of 5 bachelor students to do that for you. Previous year example: we wanted a Internet.nl-like site for NTP, but we lacked CPU cycles do develop it. So we submitted a project proposal to TU Delft software project course[0], and students developed it[1], as an open-source project. We host a copy at SIDN Labs: https://ntpinfo.sidnlabs.nl. It uses **ripe atlas** to do real-time atlas measurements. The students presented it at both RIPE91[2] and ICANN84 meetings[3]. We would like to invite folks from the RIPE community to submit projects too. ## Who can submit it? * Anyone, can be from companies or academia * It does not have to be open-source, but students like open-source better -- it helps them to find jobs later ## What's your role going to be? * You'll be the _client_, you have to say what you need. * The students have a _coach_ and a supervisor to help make the technical choices ## What can you expect? * A group of 5 motivated second year Bachelor students. * The project will run from mid April to the end of June (roughly 10 weeks). * Each student will spend up to 320 hours working on the project (most of which will be development). * As a client company you retain the IP for the product that is developed by the students during the project. * The students retain the IP of the report they have to create about their project. If you have any questions, please let me know or the contact info at [0]. Thanks, /giovane [0] https://sp.pages.ewi.tudelft.nl/site [1] https://github.com/NTPinfo/NTPinfo [2] https://ripe91.ripe.net/programme/meeting-plan/sessions/17/ [3] https://icann84.sched.com/event/29QJv/ccnso-tech-day-1-of-4

3 3

Atlas UI update 2025-12-11, new LIR overview visualisation
by Stephen Suess 11 Dec '25

11 Dec '25

Hello Atlas Community, We have just released an update to the Atlas frontend, with a couple of new features and some fixes: LIR Overview - This new visualisation came out of work on our recently released Member Overview use case. The visualisation presents an interactive bubble diagram that shows Atlas probes and anchors within these LIRs' prefixes, as well as measurements targeting these prefixes. You can check it out here: https://atlas.ripe.net/statistics/lir-overview Health check banners - The Atlas team has done significant work recently on the backend to be able to better monitor the overall health of the system, and the UI will now be able to provide up to date specific warnings in a banner when loading the site, with links out to status page entries where appropriate. To see the full list of what is new, changed, or fixed, please visit the release notes here: https://atlas.ripe.net/docs/releases/website_index/2025-12-11 As always, 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

Atlas UI performance and bugfix release 2025-12-01
by Stephen Suess 01 Dec '25

01 Dec '25

Hello Atlas friends, We have just released a new version of the UI, which fixes some bugs and performance issues. You can read the release notes here: https://atlas.ripe.net/docs/releases/website_index/2025-12-01 Please let us know if you have any feedback. Kind regards, Stephen Atlas UI

1 0

Re: v3 probe stuck with BADMD-APP
by Marek Zarychta 25 Nov '25

25 Nov '25

Hello, I have had recently the same problem like Radu described. The probe wasn't connecting with this message since 2025-11-07 09:45:52, so I have taken this probe to different ASN, but it didn't help. Today, after configuring the DNS servers in the original ASN to respond to queries coming from the probe’s temporary network, the probe was finally able to reconnect. It looks like the issue with DNS setting was a problem here. The probe was initially set to use static IP and IPv6 addresses. After changing a few weeks ago to dynamic ones it's still stuck with old DNS server settings. It's really hard to fix the USB issue with the probe using static addresses. The only working way was taking it to the network with working DHCP and/or IPv6 auto-configuration including RDNSS, plugging it without USB, waiting several minutes, plugging USB stick, waiting till it reboots, disconnecting from the network, and connecting back to the network for which static addresses were configured. Of course, if there were DHCP or RDNSS working in the original network, the troubleshooting would be far easier. Anyway, I have two requests for the RIPE Atlas operations team: - please ensure that DNS settings automatically switch to dynamic when changing a probe’s addressing mode from static to dynamic, - please allow users to change a probe’s addressing mode from static to dynamic even when the probe is currently offline. Cheers -- Marek Zarychta

2 1

Atlas UI update 2025-11-24
by Stephen Suess 24 Nov '25

24 Nov '25

Hello Atlas community, We have just released an update to the Atlas frontend, with new features, changes and fixes. Here are some of them: NEW: Member resources dashboard card and use case - We have a new feature for members, both as a dashboard card and a use case (https://atlas.ripe.net/use-cases/member-resources) Members will be able to see Atlas probes and anchors within their LIRs' prefixes, see measurements that are targeting those prefixes, and link to these objects. NEW: Probe detail results: traceroute comparison component - We have been working on a component for comparing traceroutes over time, and the first place we are rolling it out for testing is on the results tab of the probe detail page (for example: https://atlas.ripe.net/probes/1/results) When you click on a point and show traceroutes, this component will pull 12 hours of traceroutes on either side of that point and show a timeline of significant changes for comparison. NEW: Probe detail results: download data (csv/json) - On the same probe results tab, you now have a menu in the graph allowing you to download the data in csv or json format. NEW: Probe detail overview: show recently stopped measurements - You will now see a button in the probe detail overview not only for measurements currently running on the probe, but also for recently stopped measurements. In addition to the new items above, there are numerous changes and fixes present. For the full list, please see the release notes here: https://atlas.ripe.net/docs/releases/website_index/2025-11-24 We would love to know what you think. Please let us know if you have any questions, comments, or encounter any issues with this update or elsewhere in Atlas. Kind regards, Stephen Atlas UI

1 0

v2 probe repair?
by Phillip Remaker 24 Nov '25

24 Nov '25

Hello! I have an 11+ year old v2 probe Seems to be in a reboot loop. Starts up, all LEDs go blank, and it repeats. Any diagnostics I can do? Any repairs? https://atlas.ripe.net/probes/4111/#tab-network

4 7

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

Fwd: Updated RIPE Atlas Terms & Conditions
by Karolina Bochenek 19 Oct '25

19 Oct '25

Dear Sulev-Madis, all, We amended the terms and conditions in line with applicable legal GDPR requirements and intellectual property law. Under GDPR, personal data cannot be processed without a legal basis, which in the case of RIPE Atlas, would be the individual’s consent. Also, a trade name may not be used without permission from its legitimate owner. To clarify, if consent or permission is granted, RIPE Atlas probe hosts may use personal data or trade names. Regions and cities that do not reveal the identification of individuals are also not personal data and can be used. Best regards, Karolina Bochenek RIPE NCC

8 15

tracemon from old measurement
by Randy Bush 09 Oct '25

09 Oct '25

for a preso, i want a tracemon from an old measurement, 70370611. i am logged in. i go to https://atlas.ripe.net/measurements/70370611/overview i see no tracemon or even khipu option. what am i not understanding this time? randy

4 7

Erroneous data in measurement 7000
by Filip Dobrev 07 Oct '25

07 Oct '25

Dear RIPE Team, I am a Master's student at TU Delft, currently working on a tool that uses RIPE data to reliably detect network outages. While analyzing the measurements, I noticed what appears to be incorrect data being reported. In particular, when counting the number of disconnected probes per country, I observed that many countries show a major outage on 23 April 2025, where nearly all probes were marked as disconnected for about an hour and a half before recovering. For example, in Spain (ES): 2024-09-10 12:58:10 UTC – 16:37:15 UTC (Duration: 3:39:05, Peak offline probes: 154) Happened across many(40+) countries 2024-09-17 10:37:04 UTC – 12:50:56 UTC (Duration: 2:13:52, Peak offline probes: 129) Happened across many(40+) countries 2025-04-23 09:39:27 UTC – 11:11:59 UTC (Duration: 1:32:32, Peak offline probes: 210) Happened across many(90+) countries The timing and duration of the April 23 outage are consistent across many countries. I’ve compiled more examples and raw data in this editable online notepad https://shrib.com/#Asa3ZLP3Xe. It seems that a large portion of probes were marked as disconnected, even though the raw measurement data indicates they were still actively sending and receiving information. It is important to note that such errors can be observed at other times for short periods of less than a minute - 20-05-2025, again across many countries. I would greatly appreciate your clarification on a few points: 1. What could explain this discrepancy? Is it a measurement issue or something related to RIPE’s internal systems? 1. Are all measurements potentially affected by this? For example, measurement 10310, during an outage in NMK on May 18, some probes showed no responses for a 30-minute window(possibly still timing out). Similarly, during the outage in Portugal on April 28, several probes had no data for multiple hours. 1. How trustworthy are the results from the measurements? 1. How long does it typically take for RIPE to detect and reflect a disconnected probe (or other events) in the API? 1. Different requests to root measurements take the same time, even though one is requesting 30 minutes and another is requesting 4 minutes of data. Is the overhead on Ripe's side the reason for this? Looking forward to your response! Best regards, Filip Dobrev

4 3

Fwd: Updated RIPE Atlas Terms & Conditions
by Ernst J. Oud 03 Oct '25

03 Oct '25

3 3

Atlas UI updates 2025-09-26
by Stephen Suess 26 Sep '25

26 Sep '25

Hello Atlas friends, We have just released an update to the UI that includes (among other items): - NEW: Measurement form: auto-top-up settings - NEW: Measurement details manage tab: auto-top-up settings and manual top-up (when possible) - CHANGES: Khipu (beta): Horizontal layout mode, much improved RTT mode with anomaly notes, country filter dropdown, country view lookup/scoring, IP labels in IP view For the full list of what has changed, please see the release notes here: https://atlas.ripe.net/docs/releases/website_index/2025-09-26 Please let us know what you think! Kind regards, Stephen Atlas UI

1 0

FreeBSD/MacOS probe
by Jared Mauch 22 Sep '25

22 Sep '25

I’m looking for people to test out my attempted FreeBSD/MacOS changes to shift a few calls to POSIX compliant and other tweaks to make it build on other operating systems. You can try to build from this git repo: https://github.com/jaredmauch/ripe-atlas-software-probe I would request comments go here: https://github.com/RIPE-NCC/ripe-atlas-software-probe/pull/135 Or possibly in this issue which originated from someone else, but the recent note from Randy had me look at the codebase. https://github.com/RIPE-NCC/ripe-atlas-software-probe/issues/123 Hopefully this is useful and might be able to be merged back in, but I know this may cause some troubles due to the busy box parent as well. - Jared

7 29

Debian trixie support for s/w probes?
by Andrew Elwell 16 Sep '25

16 Sep '25

Hi folks, Is there a plan to support debian stable 'soon' for the software probes? I know I could build from the git repo, but I'm lazy and would rather apt-get install it, but https://ftp.ripe.net/ripe/atlas/software-probe/debian/dists/ only has bullseye & bookworm. Hat tip to all involved tho, #1009903 seems to be chugging along happily (well, except that the hypervisor's due for an update & reboot shortly) Andrew

3 2

Atlas UI, Khipu and docs updates
by Stephen Suess 15 Sep '25

15 Sep '25

Hi All, Since the last update on 2 September, we have updated the Atlas UI 3 times (including today). Among the highlights: - Khipu visualisation -- Country view -- DNS multi target view -- Smart popup placement -- Improved path filter -- Docs: https://atlas.ripe.net/docs/tools-and-code/khipu - DomainMON improved error messaging - LatencyMON url param fixes - Legal accordion new sections - Clarify member benefits in the Use Cases menu You can see all the recent changes here: https://atlas.ripe.net/docs/releases/website_index/ And as always we welcome any and all feedback and suggestions. Kind regards, Stephen RIPE Atlas UI

1 0