- ripe-atlas - mailman.ripe.net

DNS Root Server Result Stream Visualisation not working
by Wessels, Duane 11 Feb '26

11 Feb '26

I wonder if the Atlas team knows that the RIPE Atlas DNS Root Server Result Stream Visualisation is no longer working? A web browser console shows this error: Loading failed for the <script> with source “https://atlas-stream.ripe.net/socket.io.js”. dns-instances.html:47:62 Uncaught ReferenceError: io is not defined getSocket https://sg-pub.ripe.net/demo-area/atlas-stream/dns-instances.html:52 <anonymous> https://sg-pub.ripe.net/demo-area/atlas-stream/dns-instances.html:144 DW

2 2

Re: Probe 1008669 is disconnected ()
by Marek Küthe 06 Feb '26

06 Feb '26

Hello, I haven't changed anything on the small device where I installed the Atlas Probe. Why is it offline? I have attached the log. Best regards, Marek Küthe On Thu, 05 Feb 2026 19:10:00 -0000 "RIPE Atlas" <no-reply(a)ripe.net> wrote: > Dear Marek Küthe, > > Your probe 1008669 has been disconnected from the RIPE Atlas infrastructure since 2026-02-05 18:35:55 UTC. > > You may be able to learn more about the possible cause on your probe's information page: > > https://atlas.ripe.net/probes/1008669/ > > Probes are tagged with suspected problems every four hours, so if there is nothing mentioned and your probe has just gone offline, please check back in a few hours, as more information may be available. > > If you need further assistance or have any questions, please contact us at atlas(a)ripe.net. > > Kind regards, > > RIPE Atlas Team > > ********** > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes. If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/1008669/, and click the "edit" button under "Notifications". > > -- Marek Küthe m.k(a)mk16.de er/ihm he/him

2 3

FreeBSD/MacOS probe
by Jared Mauch 12 Jan '26

12 Jan '26

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

9 33

Atlas UI updates 2026-01-05
by Stephen Suess 05 Jan '26

05 Jan '26

Happy New Year, We have just released an update to the Atlas frontend with several new features to help you customise and explore your measurement data. Dashboard customisation: You can now show or hide cards on your dashboard using the new preferences button at the top of the page. This lets you tailor your dashboard to show only the items you use most. Khipu-style popups: We've brought the interactive popups from our Khipu visualisation to more places across Atlas. These popups are significantly faster than our previous popups and provide detailed, draggable information panels in the measurement details overview (all types), the results tab (traceroute and DNS), and QuickLook. DNS resolver details: When viewing DNS measurement results, you can now click on the info button in the new details column to see the complete DNS response (for all resolvers) in a dig-style format, including all flags and sections. Historical data archives for Khipu: Khipu can now pull archived IP2ASN, IXP, IP2Country, and ASN2Country data when viewing older measurements (back to Sept 2025). This means you get more accurate lookups based on the data as it was at the time of your measurement, rather than current data. You can configure how many archive snapshots to keep locally in your preferences. You can see the full list of what has changed in the release notes: https://atlas.ripe.net/docs/releases/website_index/2026-01-05 As always, we welcome your feedback and would love to know what you think. Kind regards, Stephen Atlas UI

1 0

New Path Analysis tool and Atlas UI update
by Stephen Suess 18 Dec '25

18 Dec '25

Hi Atlas friends, We have just released an update to the Atlas frontend with a few fixes and tweaks and most importantly a new standalone path analysis tool. This tool leverages our recent work on the traceroute comparison component that we are embedding in various places within Atlas (such as the probe detail results page). You can read about this new tool on labs.ripe.net: https://labs.ripe.net/author/stephen_suess_1/introducing-path-analysis-a-ne… Or you can jump straight to the docs to learn how to configure it with all the params: https://atlas.ripe.net/docs/tools-and-code/path-analysis You can also see the full list of what has changed in the release notes: https://atlas.ripe.net/docs/releases/website_index/2025-12-18 As always, we welcome your feedback and would love to know what you think. Kind regards, Stephen Atlas UI

1 0

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