- ripe-atlas - mailman.ripe.net

Request for access to RIPE Atlas HTTP measurements with full URL support
by Andrey Validenko 19 Mar '26

19 Mar '26

Hi RIPE Atlas team, I would like to request access to HTTP measurements with full URL/path support. I am currently developing a project focused on monitoring domain availability and detecting potential network interference (DNS, IP, HTTP-level) across different countries and ISPs using RIPE Atlas. At the moment, standard measurements allow testing domains at a basic level, but for my use case it is important to test specific URLs and paths (e.g. https://domain.com/path) as blocking or filtering often happens on particular endpoints rather than the root domain. Additionally, I am working on applying these measurements to anti-phishing and malware detection use cases. Many phishing campaigns rely on specific URL paths, and being able to measure HTTP responses (status codes, headers, response size) for those paths across different networks would significantly improve detection accuracy. Concretely, this capability would allow me to: - detect selective blocking or filtering of specific URLs rather than entire domains - identify abnormal HTTP responses (e.g. block pages, injected content) on targeted paths - compare behavior across ISPs and regions to detect network-level anomalies - improve heuristics for early identification of malicious or compromised infrastructure I understand that this feature may require special permissions due to resource usage, and I am committed to using it responsibly with a limited and controlled number of measurements. I would be happy to provide more details about my use case if needed. Thank you for considering my request. Best regards, Andrew Validenko Andrew_CrushPhish

1 0

Latest RIPE Atlas web update kills older browsers
by Ernst J. Oud 17 Mar '26

17 Mar '26

Hi, I just noticed that atlas.rip.net has apparently been updated. Slightly older browsers now only give a blank page, for instance Safari on iPadOS 18.1 and Opera 78 on Windows 10. Not a huge problem, currently updating my trusty iPad… always holding this off until Apple updates are reported as more stable. Regards, Ernst J. Oud

3 3

Atlas UI updates 2026-03-16
by Stephen Suess 16 Mar '26

16 Mar '26

Hello Atlas friends, We have just released an update to the Atlas frontend with the following notable changes Updated RIPE NCC Navigation: We've rolled out an updated navigation across RIPE NCC services, you can read about it here: https://labs.ripe.net/author/antonella-de-bellis/rethinking-ripe-ncc-naviga… Path Divergence Use Case: Path Divergence is the counterpart to Khipu. While Khipu visualises paths from many probes to a single target, Path Divergence visualises paths from a single probe to multiple targets across different measurements. You can read about the tool in the docs: https://atlas.ripe.net/docs/tools-and-code/path-divergence And you can try it out here: https://atlas.ripe.net/use-cases/path-divergence In addition, we have: - New region and multi-country probe selection when creating or editing measurements - Popup links out to path analysis and khipu from traceroute measurement details - In page path analysis time window controls - and a bunch of fixes and tweaks You can see the full list of what has changed in the release notes: https://atlas.ripe.net/docs/releases/website_index/2026-03-16 As always, we welcome your feedback and would love to know what you think. Kind regards, Stephen Atlas UI

1 0

Looking for credit sponsor for Master's Thesis measurements
by jkb 05 Mar '26

05 Mar '26

Hi! My name is Jakob Bork and i am currently writing my Master's Thesis on the general topic of MASQUE which includes DNS and Traceroute measurements towards service entrypoints. I already ran a couple of measurements with interesting results but need to keep them going and schedule some new for comparison. My current credit balance won't suffice sadly. Could someone sponsor me with 10-12 million credits? I will gladly name you as sponsor in the thesis and share results afterwards. ripe atlas mail: ja.b(a)fu-berlin.de Thank you! Jakob

5 5

Credit Sponsoring for DNS Research
by Richter, Robert 03 Mar '26

03 Mar '26

Hello everybody, Currently, we’re working on DNS data for Starlink. Sadly, I have already burned through all 20M of my RIPE Atlas credits, but I would like to continue my measurements. Further measurements would probably require around 35M credits. If somebody has some spare credits lying around, I’d be happy to put them to good use 😊 My RIPE Atlas Mail: robert.richter(a)rrcomtech.com Thanks in advance! Best regards, Robert

5 4

Probe v3 SW Corrupted
by ripe＠brite.cz 26 Feb '26

26 Feb '26

Hi team, I have issue with probe 34512, on atlas.ripe.net it keeps showing Flash Drive Filesystem Corrupted. I tried 4 different USB flash disks, all proven working elsewhere, even tried to swap this probe with another probe's power supply + network + USB drive, no matter what I do it keeps in the bad state. When no USB drive connected it correctly shows NO-USB SOS messages, when I plug any USB drive it will correctly detect and show its name and properties, such as Size=15155200 ro=0 SerialNumber=C860008862F0CF610A0D3704 Vendor=0930 ProdID=6544 Rev= 1.00 Manufacturer=Kingston Product=DataTraveler 2.0 or Size=242024448 ro=0 SerialNumber=07210B4816170B42 Vendor=13fe ProdID=6000 Rev= 1.10 Manufacturer= Product=Patriot Memory but still no go. The lights on the probe are [on] [off] [slow blinking] [fast blinking] [on (button one)]. If the internal firmware is corrupted, is there a way how to resurrect it? Cheers from Czechia Jiri

2 1

RootViz Dashboard
by Giovane C. M. Moura 26 Feb '26

26 Feb '26

Folks, [Sorry for cross posting] We’ve just published a new open dashboard called RootViz[0]. It shows real-time data from all RIPE Atlas probes, letting you see reachability and latency between probes and each Root Server over IPv4 and IPv6. It’s a useful complement to DNSMON[1]: DNSMON uses only Atlas anchors, whereas RootViz uses all probes (Atlas does the heavy lifting of measuring ever server every 4min, we just process it and visualise it). We published a short blog describing it too[2]. If you’re interested in how the root servers are performing globally, this should be a handy tool. Any ideas, feedback or suggestions are more than welcome. (We are looking into releasing it open-source, as it can be used to monitor any DNS service -- we do this for one of the .nl authoritatives) Thanks, /giovane -- SIDN Labs [0] https://rootviz.sidnlabs.nl [1] https://dnsmon.ripe.net/ [2] https://www.sidnlabs.nl/en/news-and-blogs/rootviz-new-root-dns-reachability…

1 0

missing probe
by Cristel Pelsser 19 Feb '26

19 Feb '26

Dear all, Do you know how I can reassign a software probe to myself? I do not see my software probe. I tried to re-add it but it won’t let me. The portal says the key already exists. The probe may be paired with my former email address. Best, Cristel

2 2

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

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

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

tracemon false join
by Randy Bush 13 Sep '25

13 Sep '25

looking at TraceMON (for 128292864), it appears as if the traces for a bunch of sources converge at a common node before failing. but they do not. they fail at different points as one can see if one looks at the result details or at khipu. what am i misunderstanding here? this is very misleading to a novice. i see one madly clicking at the apparent point of failure desperately wanting its ip address. of course, i would never make that mistake :) randy

1 0

traffic graph
by Hans Mayer 05 Sep '25

05 Sep '25

Dear All, Based on the conversation about traffic here some days ago I took a look into my statistics. I looked at the dashboard from RIPE Atlas and I looked at netflow from the router for my probe. Both from the last 24 hours. This is the dashboard and this comes from netflow it is summarised for IPv4 in and out and IPv6 in and out. Not to be confused netflow shows bits and the dashboard bytes. There is another difference, netflow has 10 minutes intervals and it seem the dashboard has 3 minutes. But independent of that, the graphs should have some similarities. I am not worried about that because the traffic is below any perception. But is there any explanation ? It becomes funny when I switch to "Last Week" All the traffic is below the 0 KB line. Maybe it should be 10 KB and the "1" is not visible for some reason. Kind regards Hans

2 1

Suggestion to change "next" field in the result of a probes REST API query
by Shane Kerr 05 Sep '25

05 Sep '25

Hello, The REST API query to get probes is documented here: https://atlas.ripe.net/docs/apis/rest-api-reference/probes If you do a lookup which would return too many results, it sets the "next" field in the return, like this: -------------------------------------------------------------------- { "count": 55125, "next": "https://atlas.ripe.net/api/v2/probes/?page=2", "previous": null, ... -------------------------------------------------------------------- The idea is the REST API client will then make a call to the "next" URL and get the next batch of data; this is basic paging. There is no kind of transaction or anything, so the status of the probes can change between each call. This is fine since the status of the probes changes independently and you cannot count on their status really. One problem is that using "page" for this means it is possible to get the same probe twice. For example, if you are looking for "Connected" probes, and returning the probes in order of probe ID, and a probe that you have already returned becomes "Connected", then the answers will all shift up by one, and you will see the last probe twice. This can be avoided by instead of using "page" for the "next" field using whatever the sorting is for the returned values in the query. I think by default this is probe ID, so the "next" field could be: -------------------------------------------------------------------- { "count": 55125, "next": "https://atlas.ripe.net/api/v2/probes/?id__gt=101", "previous": null, ... -------------------------------------------------------------------- I suspect this would be faster on the back-end too. I ended up doing this logic on the client side and it works fine, although that is for a specific sorting order. It would be more complicated to do this for all orderings on the server side. Cheers, -- Shane

2 1

Possibility to specify a POST payload?
by Lars Eggert 04 Sep '25

04 Sep '25

Hi, (Please let me know if there is a better way to make feature requests.) It would be great if it was possible to specify a payload for an HTTP POST when putting together an experiment. Thanks, Lars

5 8

Non-Profit Arts Organization Seeking Credit Donations
by ADCIBC Tech Support 03 Sep '25

03 Sep '25

Hello All, My name is Ari Broad and I am the IT Director for a non-profit arts organization called The American Dance Competition, Inc. (www.adcibc.com) We have expanded our organization internationally and I need to do performance checks on the website in various countries abroad to ensure the site is working for international users as we recently found out our site is blocked in Mainland China, so I am doing my due diligence with other countries where we are touring. I have created a python script that will do this checking process for us (versus doing it manually through online tools which is time-consuming) that utilizes RIPE-Atlas, but it will not work because I have 0 credits on my account. I see that you have to contribute to the probes in order to get credits, I would love to contribute for science, but I do not have a desktop I could host this on. I reached out to RIPE-Atlas help and they suggested I reach out to this mailing list to ask for credit donations. *Here is a list of the tests I am attempting to run:*In these countries: JP,ES,DE,SE,DK,CH,GB,IT,CA,FR,NL,PL Run measurements on 3 ASNs per country. That's *36 site performance measurements. * I am not sure what the credit currency exchange is like, but if we could get enough credits to run these tests that'd be great. *But truly any amount of credits will help!* *If you have any amount of credits you would like to donate to us for our international site performance checks please send them to the recipient: adcibc.tech(a)gmail.com <adcibc.tech(a)gmail.com> * Thank you in advance for any donations we may receive. Best, *Ari Broad, M.S.* *(she/her)* IT Director ADC|IBC www.adcibc.com

4 3

Re: Notification on removal of system-ipv4-works && system-ipv6-works tags while connected
by Antony Gollan 03 Sep '25

03 Sep '25

Hello all, We use Brevo to send these emails primarily because it ensures deliverability and allows people to easily unsubscribe. This is important because big email providers have recently increased their penalties for potential spam, so we track bounces and unsubscribes to make sure the RIPE NCC stays within acceptable limits. It is not possible for us to turn off the tracking pixel in Brevo on our end, but we use it only to view the status of delivery, opens and unsubscribes. We are aware this tracking is not 100% accurate, but it gives us a general view of whether emails are reaching their recipients, which helps us to stay below the spam threshold. If you’d rather get a plaintext version of these emails from Brevo, some email clients provide an option to switch to the plaintext view. This will also block the tracking pixel. Regards, Antony Gollan Communications Team Manager RIPE NCC

2 1

Massive uptick in number of flows to/from probe
by Jenisch Ewald 03 Sep '25

03 Sep '25

Hi, Maybe coincidence with the update of the UI rolled out today, but we've seen a massive uptick in the number of flows going out from our probe up to a range of 120k flows/sec starting around 15:00 local time (CEST) Anybody else experiencing the same thing? Any ideas as to what's going on here? Thanks in advance for any clue, -ewald eingeschränkt/restricted

5 6

Atlas UI update 2025-09-02
by Stephen Suess 02 Sep '25

02 Sep '25

Hello Atlas friends, We just released a rather significant update to the UI that includes the following new features (in addition to other changes and fixes): - NEW: Khipu visualisation (beta) - NEW: Use Cases: Path Analysis (Khipu - beta) and Reachability Testing (QuickLook - beta) - NEW: Probe detail pages results tab: Timed out measurements display - NEW: Measurements advanced search: number of probes - NEW: Measurement detail pages: show destination IPs if target is domain and resolved on probe For the full list of what has changed, you can check out the release notes here: https://atlas.ripe.net/docs/releases/website_index/2025-09-02 As always, we hope you find these changes useful and we welcome your feedback. Kind regards, Stephen Atlas UI

1 0

New RIPE Atlas Traceroute Visualisation Tool
by Stephen Suess 29 Aug '25

29 Aug '25

Hello Atlas friends, Recently we have been working on a new traceroute visualisation tool, and although we are still in early development, we wanted to release this version to the community to solicit feedback and opinions about it. This will help us focus on the items that are most important to the community as we work to finish it. You can test out this new visualisation on our beta-ui site <https://beta-ui.atlas.ripe.net/>, from any traceroute measurement detail page. Just look for the "TRACEVIS" link at the top of the page and click to access it. There is a labs article that describes the tool in some detail: https://labs.ripe.net/author/stephen_suess_1/new-prototype-ripe-atlas-trace… As always, we hope you find these features useful and we encourage your feedback. Kind regards, Stephen RIPE Atlas UI

3 6

Comparison of HW and SW Probes
by Richter, Robert 28 Aug '25

28 Aug '25

Hello everybody! Currently, I am investigating the possibilities of measurements using RIPE Atlas. Is there information about differences in the measurement results of HW and SW probes? My advisor said that I should rather not use SW probes, but I am not sure what the actual difference is, especially as SW probes often run on better hardware, compared to the HW probes. Could you point me to some resources on that topic? Best regards, Robert

8 7

Anchoring measurements from 7106 appear to be affected by a local proxy
by William Kanieski 28 Aug '25

28 Aug '25

Hi, all. I am a computer networks PhD student analyzing RIPE anchoring measurements for research purposes. While I was looking at traceroutes originating from specific anchors, I noticed that all traceroutes from Anchor #7106 only contained one hop, with no silent hops present. Upon further inspection, these singleton hops were actually the destination IP addresses themselves, and they had extremely short (<1ms) RTTs from 7106 even when they were supposed to be located on the other side of the globe. On the other hand, ping and traceroute measurements directed *toward* 7106 all seemed normal, with regular hop counts and RTTs that seemed to agree with reported geographical distance. I strongly suspect that 7106 is connected to a local proxy that is responding to outgoing ping and traceroute traffic on behalf of its intended destinations. As such, I wanted to bring some attention to this anchor so that other researchers might be aware of its status before trying to use it to conduct measurements. Regards, William Kanieski

3 3

Any problems with the registration servers?
by Tore Anderson 25 Aug '25

25 Aug '25

I have recently have had three probes «die» on me in ways the hardware actually seems fine, but the problem is with connectivity with the Atlas infrastructure. I am therefore starting to wonder if my probes were all OK after all, and that the problems are with the Atlas registration servers or infrastructure in general. Here's the timeline: First problem was with V1 probe #138 back in January. It reported through SOS messages that it could not connect on HTTPS, error code «firewall issues suspected» or something like that. However, observing the network traffic in/out of the probe revealed that the probe did successfully establish a TCP three-way handshake with reg01/reg02.atlas.ripe.net, only to immediately close the connection with a FIN packet, without actually sending any payload. There was no firewall blocking any traffic. RIPE NCC support essentially shrugged and said V1 probes aren't really supported nowadays, so I gave up and recycled the probe. Second problem was with another V1 probe (#433), in May. That one was left disconnected for an extended period of time, transitioning to "abandoned" status. As it did not reconnect after I fixed the network, I proceeded to write it off and re-connect it, then re-registered it with my personal account. It too connected fine with the network, and the event log showed a «Registration» event every time I power-cycled the probe, but it never went further and the status was stuck at «No Controller Connection». The written off status never cleared. RIPE NCC support could confirm that the written off status should have cleared after reconnection, but otherwise weren't able to help, so this probe went in the bin as well. Third problem is with a V3 probe (#10667), ongoing as I write this. It was working perfectly fine up until last week, when I moved it from a data centre to my home network. The probe had static IP configuration in the data centre, and with no way of configuring it to back to using DHCP, I thought I'd just re-install firmware by booting it up without the USB in and plugging it back in after a while. It connected fine and reported «NO-USB» SOS messages, and after plugging in the USB stick «Registration» events with the hardware details of the USB stick appeared (curiously enough, most of these events report an IP of 172.17.0.1). At that point the process gets stuck, the «Registration» events with the USB stick details keep repeating approx. every 65 minutes, and there's a warning banner at the top of the page «Flash Drive Filesystem Corrupted». So I have re-tried this with several different USB sticks, all from reputable brands, and all passing whole-device read/write tests to identify bad blocks when connected to my laptop. I have also tried replacing the power supply – nothing helps, it always ends up in the same «Registration» loop. During the process, a partition table with three 1 GiB large partitions is created on the USB stick, containing data/filesystems that my Linux laptop does not recognise as anything familiar. I could be persuaded that the two V1 probes did indeed have hardware problems. However the V3 probe clearly does not, at least not with its USB stick, and since its failure mode is rather similar to how #433 failed (process getting stuck after «Registration» events), I am starting to wonder if at least #433 was fine all along. Anyway, i am curious to hear if it is just me being very unlucky with my probes this year or if anyone else have had similar problems recently? Another issue, probably unrelated but I thought I'd mention it anyway, is that when I try to change the ownership of the V3 probe to my personal account, the web page just displays a red pop-up with the unhelpful message «An error occurred», and the ownership change does not happen. Tore

1 0