- ripe-atlas - mailman.ripe.net

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

Notification on removal of system-ipv4-works && system-ipv6-works tags while connected
by Lukas Tribus 15 Sep '25

15 Sep '25

Hello, currently notifications are configurable for the event when a probe is disconnected; however when a probes remains connected but stops working (loosing or no having either system-ipv4-works and system-ipv6-works tags), we are blind. I have written a monitor script to query the API for this, to get this notification but I'm wondering if it would be possible to implement this at RIPE. The system-<AF>-works tags are already there. Software bugs and I guess HW issues can trigger hung probes that remain connected. It's hard to find out, unless one is specifically looking for it or specifically expecting the result of a single probe in a measurement. Lukas

15 29