- ripe-atlas - mailman.ripe.net

Atlas ping measurement with include_probe_id
by Yi Zhou 07 Apr '26

07 Apr '26

Hi All, I’m having issues with how the payload of a ping measurement is constructed. In a recent experiment, I found that not all probes correctly embed the probe ID into the payload. For example, the following payload is a correct example. [4, 255, 0, 1, 0, 25, 253, 117, 26, 85, 207, 174, 0, 0, 0, 0, 192, 94, 125, 241, 173, 37, 232, 44, 82, 73, 80, 69, 32, 65, 116, 108, 97, 115, 32, 112, 114, 111, 98, 101, 32, 49, 48, 50, 50, 49, 0, 0, 0, 0, 0, 0] Includes “[82, 73, 80, 69, 32, 65, 116, 108, 97, 115, 32, 112, 114, 111, 98, 101, 32]” as the ASCII of “RIPE Atlas probe ”, and “[32, 49, 48, 50, 50, 49]” as probe ID “10221” However, in a randomized sample of 50 probes, 34 of them do not have the probe ID following “RIPE Atlas probe" [82, 0, 0, 1, 113, 214, 8, 0, 0, 0, 0, 0, 129, 197, 72, 49, 0, 0, 0, 0, 0, 0, 0, 0, 171, 144, 68, 164, 87, 28, 143, 103, 0, 0, 0, 0, 82, 73, 80, 69, 32, 65, 116, 108, 97, 115, 32, 112, 114, 111, 98, 101] While considering the chance that older firmware versions do not recognize the configuration option, I disabled the ‘include_probe_id’ option. None of the payloads in this experiment includes the “RIPE Atlas probe” part. Does anyone have experience with this issue? I do notice that there are about 8 bytes shared between packets from the same probe and the same measurement, but it seems more like a randomized identifier. Thanks, Yi

1 0

Request for RIPE Atlas credits - CS student at ETH Zürich
by Nikolas Kühnlein 30 Mar '26

30 Mar '26

Hi all, My name is Nikolas Kühnlein and I am a computer science student at ETH Zürich, currently taking a course on computer networks. As part of my studies I have been exploring traceroute analysis and IP geolocation using latency triangulation — specifically trying to verify the physical location of intermediate hops using RTT measurements from distributed vantage points, rather than relying on WHOIS or commercial geolocation databases. I recently discovered RIPE IPmap and was impressed by how accurately it placed a Google border router in Zürich (contradicting a WHOIS record pointing to Mountain View, CA). I would like to run my own ping measurements from European probes to a small set of hop IPs from my traceroutes, to understand the triangulation method hands-on. As a new user I have no credits, and I am looking for a small donation to get started — a few million credits would be more than enough for what I have in mind. My RIPE Atlas account is registered under: nikshop(a)takuu.de I am happy to share my findings with the community. Thank you in advance for any help. Best regards, Nikolas Kühnlein ETH Zürich

5 5

CfP: Workshop on Negative results in Network measurements (NetNet)
by Alexandrina Ioana Livadariu 26 Mar '26

26 Mar '26

Hello all, We are organizing a workshop on Negative results in Network measurements (NetNet) this year. The workshop is part of ACM SIGCOMM’26 and will take place in Denver, Colorado, USA. The workshop invites submissions that report and reflect negative results in network measurement studies. The main goal is to foster a constructive discussion on lessons learned from studies in which methods, datasets or experimental designs did not yield the expected results. Submissions should focus on fundamental issues related to measurement approaches, methodology, and underlying assumptions, rather than on non-fundamental issues such as implementation bugs or misconfigurations. Focusing on the critical parts of the experiment, the workshop aims to strengthen rigor, promote transparency and improve methodology practices in network measurement research. We are planning to open the workshop for short papers (two and six pages) focusing on one problem where the authors dealt with negative results. Submissions must be original, unpublished work, and not under consideration at another conference or journal. Important dates: Submission deadline: May 1, 2026 (AoE) Acceptance deadline: June 5, 2026 Camera ready: June 20, 2026 Workshop date: August 17, 2026 (co-located with ACM SIGCOMM’26) Submission: https://netneg26.hotcrp.com/ Full Call for Papers: https://conferences.sigcomm.org/sigcomm/2026/netneg/ We look forward to your submissions and participation! Best regards, Ioana Livadariu & Mattijs Jonker

1 0

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