September 2026 - ripe-atlas - mailman.ripe.net

OpenWRT probes?
by Phillip Remaker 20 Oct '26

20 Oct '26

I recently got a note to upgrade all of my software probes to 5130 from 5080. I found that the OpenWRT package version is still at 5080. I know it is community supported, but are there plans to update? Should I retire OpenWRT probes or are they still useful?

3 3

Notifications about older software probe versions
by Robert Kisteleki 05 Oct '26

05 Oct '26

Dear all, especially software probe hosts, Many of you contribute to RIPE Atlas by running one or more software probes. Thank you for doing so! In the case of software probes you, the host, are in control of the installation and upgrade process. We noticed that there are many probes that have been installed, but not upgraded over time. We'd like to inform you that early next week we'll activate a feature in the system where we'll periodically remind software probe hosts with non-newest versions to upgrade their probes. We expect that at some point later we'll also start enforcing the use of newer versions. Please note that since we provide multiple binary releases, it's also possible to set up automatic package updates for the popular platforms (Debian, RHEL, Raspberry). We'd recommend using this feature (in general, not necessarily just for the probe package). You can find full upgrade instructions for the supported platforms at https://github.com/RIPE-NCC/ripe-atlas-software-probe#upgrading Regards, Robert Kisteleki, for the RIPE Atlas team

7 11

Anchor wont boot after unusual activity in root's .bash_history
by Andrew Gallo 30 Sep '26

30 Sep '26

We host an anchor that went offline on Sept 1, 2026. During troubleshooting, I noticed the following in root's .bash_history: > ping pl-szz-as28785.anchors.atlas.ripe.net > tail -f /var/log/ansible.log > yum -y update > reboot > cat /etc/redhat-release > dd if=/dev/zero of=$(mount|grep boot|awk '{print $1}') > rm -rf /etc/ /home/ /srv/ /export/ > systemctl poweroff Indeed, the boot partition is corrupted, grub can't identify any filesystem on it, nor can any other file system tools. From the messages, I can see that a named user from RIPE (meaning, it didn't appear to be an automated login) was logged in at this time. I opened a ticket in the portal on September 11 and have not received an update, nor can I open a second ticket on the same node. Before I begin to reinstall or recover this node, I'd like to know what's going on. Has anyone else seen anything like this? -- ________________________________ Andrew Gallo The George Washington University

2 2

RIPE Atlas UI updates for 2026-09-21
by Stephen Suess 21 Sep '26

21 Sep '26

Hello Atlas Friends, We just pushed a rather significant update to the Atlas UI with a bunch of new features, changes and fixes. Here are some of the highlights: New QuickStart guide: We have completely reworked the QuickStart guide (at the top of the Dashboard) to be more dynamic, interactive and (we hope) useful, especially for new users of Atlas. New Users 50K credits claim: Also for new users, we have an enabled a one-time claim of 50K credits (available in the Dashboard) to help them get started creating measurements of their own and learning more about the RIPE Atlas ecosystem. Khipu New Features: In Khipu, we have enabled a timelapse feature (for periodic measurements with less than 100 probes) as well as a new Shared Hops toggle that sets how aggressively routes merge — Paths merges them only once they've joined for good on the way to the target (cleaner), Topology merges every occurrence of the same hop into a single node (more accurate). Khipu will now also show an alert on paths that are stuck in a routing loop. Anchor Detail live map: Live Mesh Pings draws every other anchor in the mesh as a dot on the world map, coloured by the round-trip time of its most recent ping toward this anchor and pulsing as each new result streams in. In addition there are several enhancements and fixes for LatencyMON, Coverage map, DomainMON and others. You can view the full list in the release notes: https://atlas.ripe.net/docs/releases/website_index/2026-09-21 As always, we welcome your feedback and would love to know what you think. Kind regards, Stephen Atlas UI

1 0

RIPE Atlas probe connectivity drop around 11:20 UTC — looking for community insights
by Dixan Santiesteban 21 Sep '26

21 Sep '26

Hello everyone, I have recently been exploring RIPE Atlas’s public data, focusing on probe connectivity. Yesterday, I noticed a sharp drop in the number of connected probes, particularly around 11:20 UTC. As I am new to working with this data, I would appreciate your help understanding this observation. Did these disconnections actually occur simultaneously, or could the pattern reflect how the data is collected, reported, or processed in my dashboard? To make the results easier to explore, I have put together a standalone version of the dashboard, available here: https://ripleatlas.netlify.app/ It includes an interactive timeline that lets you explore the data and examine the changes I observed. My goal is to validate my interpretation and improve the dashboard’s logic so it can better distinguish actual connectivity events from potential data artifacts. Any insights, suggestions, or feedback on the methodology or dashboard would be greatly appreciated. Thank you for your time and help! Best regards, Dixán

3 2

Weird issue with Probe 54041
by J S 20 Sep '26

20 Sep '26

Hey team, my Probe 54041 stops working every couple of days. It always show connected but it does not send any measurements data. Any idea what could be wrong? After cold reboot it works for some time and then again. Cables and power source replaced couple of times. It is directly connected to Vodafone provided router, but it probably does not matter.It is in remote location so I can't get there frequently. Cheers Jiri

2 2

Re: RIPE Atlas probe connectivity drop around 11:20 UTC — looking for community insights
by Dixan Santiesteban 20 Sep '26

20 Sep '26

*Ray Bellis,* Now I can see the details of the disconnection a bit more clearly; thanks for your reply: https://ripleatlas.netlify.app/?q=ab928 thanks... El vie, 18 sept 2026 a la(s) 11:21 a.m., Dixan Santiesteban ( dixan2024(a)gmail.com) escribió: > I appreciate your comment; any suggestions are welcome... > > > El vie, 18 sept 2026 a la(s) 11:02 a.m., Ernst J. Oud (ernstoud(a)gmail.com) > escribió: > >> Dixán, >> >> What an excellent tool! Thanks for creating this! >> >> Regards, >> >> Ernst J. Oud >> >> On 18 Sep 2026, at 16:25, Dixan Santiesteban <dixan2024(a)gmail.com> wrote: >> >> >> >> Hello everyone, >> >> I have recently been exploring RIPE Atlas’s public data, focusing on >> probe connectivity. Yesterday, I noticed a sharp drop in the number of >> connected probes, particularly around 11:20 UTC. >> >> As I am new to working with this data, I would appreciate your help >> understanding this observation. Did these disconnections actually occur >> simultaneously, or could the pattern reflect how the data is collected, >> reported, or processed in my dashboard? >> >> To make the results easier to explore, I have put together a standalone >> version of the dashboard, available here: >> https://ripleatlas.netlify.app/ >> >> It includes an interactive timeline that lets you explore the data and >> examine the changes I observed. My goal is to validate my interpretation >> and improve the dashboard’s logic so it can better distinguish actual >> connectivity events from potential data artifacts. >> >> Any insights, suggestions, or feedback on the methodology or dashboard >> would be greatly appreciated. >> >> Thank you for your time and help! >> >> Best regards, >> Dixán >> ----- >> To unsubscribe from this mailing list or change your subscription >> options, please visit: >> https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ >> As we have migrated to Mailman 3, you will need to create an account with >> the email matching your subscription before you can change your settings. >> More details at: >> https://www.ripe.net/membership/mail/mailman-3-migration/ >> >>

1 0

Request for RIPE Atlas credits for RPKI measurements
by Alexander Männel 18 Sep '26

18 Sep '26

Dear RIPE Atlas community, my name is Alexander Männel and I'm a PhD student at the Chair of Distributed and Networked Systems at TU Dresden. I currently use RIPE Atlas measurements to track how dataplane paths change once the ROV status of an announcement changes. Given the coverage that I aim to achieve and the number of events like this that happen, these measurements require a large amount of credits. To be able to continue these measurements for at least four weeks I'm therefore seeking 200 million credits. I'm grateful for any donation that helps to achieve this number! My RIPE Atlas e-mail: alexander.maennel(a)tu-dresden.de Some preliminary findings were already presented at IETF126: https://datatracker.ietf.org/meeting/126/materials/slides-126-sidrops-measu… Thank you for considering my request! Sincerely, Alexander Männel -- Alexander Männel TU Dresden, Chair of Distributed and Networked Systems https://tu-dresden.de/cs/netd

6 5

Re: Request for RIPE Atlas credits for RPKI measurements
by Carsten Schiefner 18 Sep '26

18 Sep '26

Moin, Alex - 20 M sent. Happy researching - und herzliche Grüße nach dem schönen Elbflorenz -C. On 18.09.2026 18:02, Alexander Männel wrote: > Dear RIPE Atlas community, > my name is Alexander Männel and I'm a PhD student at the Chair of Distributed and Networked Systems at TU Dresden. > I currently use RIPE Atlas measurements to track how dataplane paths change once the ROV status of an announcement changes. Given the coverage that I aim to achieve and the number of events like this that happen, these measurements require a large amount of credits. To be able to continue these measurements for at least four weeks I'm therefore seeking 200 million credits. I'm grateful for any donation that helps to achieve this number! > My RIPE Atlas e-mail: alexander.maennel(a)tu-dresden.de > Some preliminary findings were already presented at IETF126: https://datatracker.ietf.org/meeting/126/materials/slides-126-sidrops-measu… > Thank you for considering my request! > Sincerely, > Alexander Männel

1 0

Request for RIPE Atlas credits for public DNS research
by Dipsy Desai 17 Sep '26

17 Sep '26

Dear RIPE Atlas community, My name is Dipsy Desai and I am a fourth year Ph.D. student at University of Southern California. I am conducting a research study examining the routing, performance, and data-residency properties of public recursive DNS services across India. The study will compare Bharat Public DNS (1.10.10.10) with global public resolvers using RIPE Atlas DNS measurements and traceroutes. We will begin with a small pilot (which we anticipate would consume about 60,000 credits) and then expand to a multi-week study across geographically and topologically diverse Indian probes. The measurements will examine latency, availability, routing variation, and client-to-resolver path locality. For the complete study and independent validation measurements, I am seeking up to 4,500,000 RIPE Atlas credits. Any partial donation would also be greatly appreciated. Only established public DNS services and research-controlled infrastructure will be targeted. We intend to make the measurements, analysis code, and results publicly available where possible. My RIPE Atlas account for credit transfers is: deepakde(a)usc.edu Thank you for any support you may be able to offer to this research. Best regards, Dipsy

6 9