July 2025 - ripe-atlas - mailman.ripe.net

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

Request for RIPE Atlas Credits for Research on Domain Blocking in Latin America
by Kirill Betberry 28 Jul '25

28 Jul '25

Hello, Atlas community! My name is Kyrylo, and I’m currently exploring how different ISPs across Latin America implement domain-level blocking, particularly in the context of content filtering and censorship. To get a more comprehensive and unbiased view, I’d like to use RIPE Atlas measurements from a geographically diverse set of probes. I’m especially interested in comparing how domain reachability varies across providers and countries in the region. This is a personal project designed to learn more about global network behavior. I would appreciate it if anyone in the community is willing to donate some extra RIPE Atlas credits to support this effort. Any help would be greatly appreciated! My RIPE Atlas account is registered with this email: kyrylo(a)betberry.io Thank you in advance for your support and for making such a great tool available to the community. -- Thanks! Kyrylo

4 3

Problem deleting measurements
by Loqman Salamatian 25 Jul '25

25 Jul '25

Hi folks, I’ve recently run into an issue when trying to stop some ongoing measurements that I created. I’ve tried two approaches: 1. Using the Cousteau API wrapper: from ripe.atlas.cousteau import AtlasStopRequest stop_request = AtlasStopRequest(msm_id=m_id, key=API_KEY) success, response = stop_request.create() 2. Attempting a raw DELETE via the API I attempted to stop them using the DELETE method via the /measurements/{id}/ endpoint. These two approaches worked for some measurmeents but then I get the following error: {"error":{"detail":"That measurement cannot be stopped","status":400,"title":"Bad Request","code":104}} 3. Using raw PATCH via the API I then tried to use a PATCH request to update the stop_time to a timestamp in the past. Here I get no error but the measurements are not updated. All these measurements appear under my user account and are marked as “Ongoing.” I’m unsure why they can’t be stopped. Could you please advise on: 1. Why these measurements might be undeletable? 2. Whether there’s an alternative way to terminate them? Thanks in advance for your help! Best, Loqman

1 0

measurements cannot be created
by Marco Moock 25 Jul '25

25 Jul '25

Hello! I tried to create a measurement, I get the green banner Measurement(s) created! 119740137 When opening it, I get the error that the data cannot be fetched. Do other people encounter the same? -- kind regards Marco Send unsolicited bulk mail to 1753424511muell(a)stinkedores.dorfdsl.de

1 0

Atlas UI and Docs updates
by Stephen Suess 24 Jul '25

24 Jul '25

Hello Atlas friends, We just released an update to the UI that includes the following new features (in addition to other changes and fixes): - NEW: Probe detail: Resolve geo location dispute - NEW: Measurement Detail: Add link out to new troubleshooting doc when any msm has no replies - NEW: Prefs: set preferred address family (v4/v6) for use in forms and charts when possible 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-03-25 We have also just released a new docs system based on vitepress: https://atlas.ripe.net/docs/ As always, we hope you find these changes useful and we welcome your feedback. Kind regards, Stephen Atlas UI

7 17

atlas.ripe.net service migration
by Christopher Amin 24 Jul '25

24 Jul '25

Dear colleagues, The scheduled maintenance on atlas.ripe.net was successfully completed earlier today, with a short-lived minor impact on API requests. For details, please see the status page entry: https://status.ripe.net/incidents/jv6wtx5s71rg Regards, Chris Amin RIPE NCC

1 0

really strange hop situation on 1006475
by Marco Moock 23 Jul '25

23 Jul '25

Hello! Probe 1006475 has really interesting results: RESOLVED tr.dorfdsl.de TO 2a01:170:118f:30::100 STARTED QUERY AT 2025/07/23 14:52:56 UTC Fetching Measurement: 119451691 Traceroute from 2405:8d40:48d9:592f:10b8:22ff:fe88:a416 to 2a01:170:118f:30::100 (2a01:170:118f:30::100): 1 fd8d:b030:165f::1 8.901ms 0.79ms 0.762ms 2 tr.dorfdsl.de (2a01:170:118f:30::100) 268.925ms 262.384ms 262.513ms This cannot be true as my system is far away. I also receive that packet, so it is not a simulation etc. This is the situation from the other direction: m@tr:~$ sudo traceroute -I 2405:8d40:48d9:592f:10b8:22ff:fe88:a416 traceroute to 2405:8d40:48d9:592f:10b8:22ff:fe88:a416 (2405:8d40:48d9:592f:10b8:22ff:fe88:a416), 30 hops max, 80 byte packets 1 2a01:170:118f:30::1 (2a01:170:118f:30::1) 1.164 ms 2.235 ms 2.309 ms 2 2a01:170:0:10::1 (2a01:170:0:10::1) 10.751 ms 10.853 ms 10.816 ms 3 * * * 4 * * * 5 * * * 6 ffm-bb1-v6.ip.twelve99.net (2001:2034:1:6b::1) 10.444 ms 11.857 ms 11.418 ms 7 mei-b5-v6.ip.twelve99.net (2001:2034:0:15a::1) 26.477 ms 41.573 ms 41.224 ms 8 sng-b7-v6.ip.twelve99.net (2001:2034:0:14::1) 197.873 ms 197.940 ms 196.175 ms 9 * * * 10 ditona-ic-388046.ip.twelve99-cust.net (2001:2035:0:28f0::2) 194.862 ms 194.751 ms 194.879 ms 11 2405:8d40:2:103b::3 (2405:8d40:2:103b::3) 230.238 ms 230.303 ms 230.253 ms 12 2405:8d40:0:1002::2 (2405:8d40:0:1002::2) 222.359 ms 222.388 ms 222.404 ms 13 2405:8d40:3:1004::3 (2405:8d40:3:1004::3) 256.477 ms 248.020 ms 247.930 ms 14 2405:8d40:103:1013::3 (2405:8d40:103:1013::3) 242.521 ms 244.766 ms 243.801 ms 15 2405:8d40:a38:20b3::4d (2405:8d40:a38:20b3::4d) 243.622 ms 244.194 ms 244.200 ms 16 2405:8d40:48d9:592f:569:347b:29b8:4da3 (2405:8d40:48d9:592f:569:347b:29b8:4da3) 261.501 ms 271.957 ms 275.285 ms 17 2405:8d40:48d9:592f:10b8:22ff:fe88:a416 (2405:8d40:48d9:592f:10b8:22ff:fe88:a416) 255.513 ms 249.852 ms 248.217 ms m@tr:~$ Does anyone have a clue what is going on? Traffic manipulation at the remote ISP? -- Gruß Marco Send unsolicited bulk mail to 1753282214muell(a)stinkedores.dorfdsl.de

1 0

Offset of NTP measurement
by Marco Davids (SIDN) 23 Jul '25

23 Jul '25

I noticed a discrepancy between the output of my own tool and RIPE Atlas. My tool reports the offset as a negative value, while RIPE Atlas shows a positive one. For example: https://atlas.ripe.net/measurements/115803954/results Any thoughts? -- Marco

7 10

Possible Corner Case Bug in RIPE Atlas NTP Measurement
by Marco Davids 22 Jul '25

22 Jul '25

Dear RIPE Atlas team, I believe we may have discovered a corner case bug in the way RIPE Atlas handles NTP measurements. The issue surfaced during experiments with my NTP simulator — a small tool that mimics an NTP server and allows for controlled manipulation of its behavior. In one particular scenario, the simulator randomly varies the poll value in each response. While this doesn’t occur frequently in real-world implementations, it is technically valid behavior. It appears, however, that either the probes or the measurement system itself do not expect the poll value to change across responses. When initiating a measurement with the default setting of 3 packets, and each response has a different poll value, the result is that the measurement ends up reporting nothing. I first described this on the RIPE Atlas mailing list: https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/thread/33KNP7KPX… A detailed analysis can be found here: https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/message/OSRNUJ2Y… The NTP simulator is publicly reachable at: ntp1.testdns.nl I'd appreciate it if you could take a look. Thank you in advance for your time and consideration! Kind regards, -- Marco Davids SIDN Labs

1 0

Re: Atlas probes not reporting NTP results on ntp0.testdns.nl ?
by Marco Davids 22 Jul '25

22 Jul '25

Hi Joachim, Thanks again for your work and the promising findings! I’ve updated the settings of the NTP simulator (now running at ntp1.testdns.nl) to keep the poll value fixed, and I’ve created a new measurement with 50 probes, each sending 10 packets per interval: https://atlas.ripe.net/measurements/118724341 And indeed — things already look a lot better! So... did we just find a bug? Best, -- Marco -------- Original Message -------- *Subject: *[atlas] Re: Atlas probes not reporting NTP results on ntp0.testdns.nl ? *From: *Joachim Kroß *To: *"Marco Davids (SIDN)" , ripe-atlas(a)ripe.net *Date: *Thu, 17 Jul 2025 15:30:35 +0200 > When multiple packets are sent per sample (default is to send three), > those are currently sent back to back. I.e., unless there is packet > loss, the second and third request are sent as soon as the response to > the previous request has been received. As consequence, the values of > the majority of fields in the responses are typically the same, e.g., > ref-id, poll, precision, stratum, version, mode, even ref-ts. As such, > they are at the top level of the JSON object. And the "result" structure > only has the fields that vary between the packets, i.e., the timestamps > related to the actual packet transmissions (and derived values). > > With the explicitly misbehaving server, however, some of the fields that > would typically not change between back-to-back responses, or rather > rarely only, _do_ change from one response to the next. E.g., the poll > and precision fields. In those cases, there still is an entry at the top > level of the JSON object, I guess perhaps derived from the first packet. > But then, the result structure would additionally have entries for those > types of fields where the value differs from the one at the top level.

1 1