- ripe-atlas - mailman.ripe.net

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

11 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

2 1

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