- ripe-atlas - mailman.ripe.net

Kind request for credits
by Khodor SAFA 29 Jun '26

29 Jun '26

Hello everyone, I hope this message finds you well. I have been advised by the RIPE Atlas team to contact this mailing list for my request of credits. Any number you can provide could be useful for me, at least to begin getting familiarised with the platform. Thank you very much in advance!

3 4

Announce: upcoming changes in historical data access
by Robert Kisteleki 23 Jun '26

23 Jun '26

Dear RIPE Atlas users, We'd like to inform you about an upcoming change affecting downloads of large, historical results. As of today, one can ask the RIPE Atlas API to supply results of measurements without time boundaries, as in "give me all the data you have for this measurement". That's fine for results of one-off measurements because those are always relatively small. However for periodic measurements this is mostly harmful as it results in possibly huge amounts of data, as such it's often aborted, and incurs costs on both parties. We plan to enforce time limit parameters, where the query for results will have to specify a start and and end time and the interval spans at most a week. Scripts that intend to download results for a wide time interval will need to loop through the interval in chunks (perhaps per day, ideally aligned to UTC midnight to be the most efficient). UI functionality will not be affected. We intend to apply this change around the first week of August. Regards, Robert Kisteleki, for the RIPE Atlas team

1 0

Re: Atlas UI updates for 2026-06-09
by ripe＠brite.cz 16 Jun '26

16 Jun '26

Could you please make the "Passkey" type of login method as default (when configured), instead of "Authenticator application". Or at least have the "Select login method" as default or let the user choose the default once and make it remember. In fact, retyping number from Authenticator application that is the least comfortable way of login. Also would be great if the login is remembered across multiple days, so no login is needed every single time. Thanks Jiri ------------------------------------------------------------------------------------------------------------- út 9. 6. 2026 v 10:41 odesílatel Stephen Suess <ssuess(a)ripe.net> napsal: Hello Atlas community, We have just pushed some new updates to the UI. Among the highlights: - Well-known measurements: In addition to Google, Facebook and Wikipedia, we have added Akamai, Amazon, Azure, Cloudflare, Fastly, Github, Instagram, LinkedIn, Netflix, Reddit, X and Youtube. We have also added the ability to set your choices on the results tab of the probe detail pages, share links to these selections, and save your preferences so that you always see your preferred selections when visiting these pages. In addition, these measurements have been added to the Well-known RTT map at https://atlas.ripe.net/maps/well-known - Probe connectivity use case enhancements: You can now select "All Probes" (careful, it may take some time to load) as well as a checkbox to separate probes by controller to see connections by controller visualised in the main graph. You can see the full list of what has changed in the release notes: https://atlas.ripe.net/docs/releases/website_index/2026-06-09 As always, we welcome your feedback and would love to know what you think. Kind regards, Stephen Atlas UI ----- 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/

3 2

Probe connected, but data upload seems to fail with 429, and high bitrate bursts
by ripe＠nurfuerspam.de 10 Jun '26

10 Jun '26

Hi, I have a software probe that since a few days only is sending very short traffic bursts at very high bitrates (for a probe), amounting to a 5 minute bitrate average nearing 1 Mbit/s. I _think_ this _may_ have started on or around 2026-06-07, but I don't have detailed logs going back that far anymore (destroyed the container the probe was originally running in, see below, several times in the course of troubleshooting this without saving the logs :-() When looking into the current logs, I see (as per my understanding) that the POST upload of the measurement data apparently fails with a 429 error, or an occasional "httppost: error reading from server: Connection reset by peer". See below for two instances from the log. Originally, the probe was running in a container (like most of my other probes as well without issues), then version 5100 natively on Debian 12 x86_64 VPS, just upgraded to 5120 - same result. Probe ID 1009529. Any thoughts? Thanks! Cheers, R. Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: total size in dir: 6254 Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: httppost: before getaddrinfo Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: httppost: before connect Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: httppost: sending request Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/1' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/5' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/2' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/0' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/3' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/6' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/7' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/8' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/4' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/9' Jun 10 18:59:24 vps-cbf1 ripe-atlas[173212]: httppost: getting result Jun 10 18:59:25 vps-cbf1 ripe-atlas[173212]: httppost: POST command failed: '429 ' Jun 10 18:59:25 vps-cbf1 ripe-atlas[173212]: httppost: leaving with error Jun 10 18:59:25 vps-cbf1 ripe-atlas[173212]: ooqd: httppost failed with 1 Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: total size in dir: 6254 Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: httppost: before getaddrinfo Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: httppost: before connect Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: httppost: sending request Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/1' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/5' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/2' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/0' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/3' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/6' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/7' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/8' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/4' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: posting file '/var/spool/ripe-atlas/data/out/ooq/9' Jun 10 18:57:24 vps-cbf1 ripe-atlas[173212]: httppost: getting result Jun 10 18:57:25 vps-cbf1 ripe-atlas[173212]: httppost: error reading from server: Connection reset by peer Jun 10 18:57:25 vps-cbf1 ripe-atlas[173212]: httppost: leaving with error Jun 10 18:57:25 vps-cbf1 ripe-atlas[173212]: ooqd: httppost failed with 1

1 1

Atlas UI updates for 2026-06-09
by Stephen Suess 10 Jun '26

10 Jun '26

Hello Atlas community, We have just pushed some new updates to the UI. Among the highlights: - Well-known measurements: In addition to Google, Facebook and Wikipedia, we have added Akamai, Amazon, Azure, Cloudflare, Fastly, Github, Instagram, LinkedIn, Netflix, Reddit, X and Youtube. We have also added the ability to set your choices on the results tab of the probe detail pages, share links to these selections, and save your preferences so that you always see your preferred selections when visiting these pages. In addition, these measurements have been added to the Well-known RTT map at https://atlas.ripe.net/maps/well-known - Probe connectivity use case enhancements: You can now select "All Probes" (careful, it may take some time to load) as well as a checkbox to separate probes by controller to see connections by controller visualised in the main graph. You can see the full list of what has changed in the release notes: https://atlas.ripe.net/docs/releases/website_index/2026-06-09 As always, we welcome your feedback and would love to know what you think. Kind regards, Stephen Atlas UI

5 7

Reporting incorrect location of an anchor
by Serhii Timofieiev 08 Jun '26

08 Jun '26

Is it possible to report RIPE Atlas anchor having an incorrect location?

3 2

Issues with software probes connections
by Robert Kisteleki 08 Jun '26

08 Jun '26

Dear software probe hosts, Around Friday afternoon we started experiencing an issue where software probes that disconnected for any reason were not allowed to connect again. Over time this caused a gradual decrease in the number of connected probes, up to 20% of software proves or about 10% of the total probe population. We identified the root cause to be a delay of processing of internal control messages. We executed ad-hoc measures that allowed most probes to temporarily connect again, and we are currently working on a proper solution. I'll post an update once we this solution in place. Regards, Robert Kisteleki

1 0

Re: Your probe 1008669 has disconnected
by Marek Küthe 07 Jun '26

07 Jun '26

Hello, My probe has disconnected. Could someone take a look at this? The message in the log is as follows: ``` Jun 06 00:12:48 laplace ripe-atlas[113935]: condmv: not moving, destination '/var/spool/ripe-atlas/data/out/simpleping' exists Jun 06 00:12:48 laplace ripe-atlas[113934]: condmv: not moving, destination '/var/spool/ripe-atlas/data/out/v6addr.txt' exists Jun 06 00:12:48 laplace ripe-atlas[113915]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1780697679 Jun 06 00:12:47 laplace ripe-atlas[113915]: ssh -p 443 atlas(a)193.0.19.246 INIT Jun 06 00:12:47 laplace ripe-atlas[113915]: REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 Jun 06 00:12:47 laplace ripe-atlas[113915]: REG_WAIT_UNTIL expired go re-reg 1780697510 now 1780697567 Jun 06 00:12:47 laplace ripe-atlas[113915]: there is WAIT, REG_WAIT_UNTIL , now is 1780697567 Jun 06 00:12:47 laplace ripe-atlas[113915]: ATLAS registration starting Jun 06 00:12:47 laplace ripe-atlas[1356]: start reg Jun 06 00:12:47 laplace ripe-atlas[1356]: Ping works Jun 06 00:12:44 laplace ripe-atlas[1356]: /run/ripe-atlas/status/reginit.vol does not exist try new reg Jun 06 00:12:44 laplace ripe-atlas[1356]: RESULT 9006 done 1780697564 901b0e4bf9d8 no reginit.vol start registration ``` I've attached the last 200 lines of the log. Best regards, Marek Küthe On Fri, 05 Jun 2026 17:00:00 +0000 "RIPE Atlas" <atlas+e76c0ca5(a)ripe.net> wrote: > ###Probe 1008669 is disconnected () > > > Marek Küthe, > > > > Your probe 1008669 has been disconnected from the RIPE Atlas infrastructure since 2026-06-05 16:25:47 UTC. > > You may be able to learn more about the possible cause from the "Status" tab on your probe's information page: > > https://atlas.ripe.net/probes/1008669/#!tab-status > > Probes are tagged with suspected problems every four hours, so if there is nothing listed under the Status tab 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. > > > Best regards, > The RIPE Atlas Team > > **RIPE NCC** > > Stationsplein 11, 1012 AB, Amsterdam > > This email was sent to m.k(a)mk16.de > > You've received this email because you are registered as a RIPE Atlas probe host. -- Marek Küthe m.k(a)mk16.de er/ihm he/him

5 9

And another probe disconnected
by Ernst J. Oud 07 Jun '26

07 Jun '26

Number 4 of 11 is down… Ouch. Ernst

2 2

Disconnected probes
by Ernst J. Oud 06 Jun '26

06 Jun '26

The controller with a problem appears to be ctr-dub-sw01 And reg server reg03 and/or reg04. Met vriendelijke groet, Ernst J. Oud

1 0

Re: Your probe 1008669 has disconnected
by Ernst J. Oud 06 Jun '26

06 Jun '26

Yes, my three software probes that are down are on 5G connections that have a forced renew of their IP address every 24 hours. The controller in Dublin I believe has some fault. Hope RIPE corrects this asap. Met vriendelijke groet, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud > On 6 Jun 2026, at 17:11, via ripe-atlas <ripe-atlas(a)ripe.net> wrote: > > Hi again, > > My number keeps going up. Looks like whenever a probe gets disconnected for some other reason, it is not able to connect back to the system. > > And my earlier count was too low already. It seems e-mail notifications aren't sent reliably. At least I didn't get one for some probes that are definitely down longer than the timeout configured (mostly default of 30 minutes). > > Cheers, > > R. > >> On 6/6/26 17:06, Ernst J. Oud wrote: >> Hi, >> Same here. Three of my software probes have disconnected this morning. Nothing wrong with internet at those locations. One of these locations also has a hardware probe that runs fine. >> In the logs it says: >> —- >> /var/atlas-probe/status/reginit.vol does not exist try new reg >> Ping failed >> start reg >> ATLAS registration starting >> there is WAIT, REG_WAIT_UNTIL , now is 1780758142 >> REG_WAIT_UNTIL expired go re-reg 1780758077 now 1780758142 >> REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 >> ssh -p 443 atlas@2001:67c:2e8:11::c100:13f6 INIT >> 255 REGINIT exit with error >> condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists >> condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists >> —- >> Something definitely wrong with the controller infra! >> Regards, >> Ernst J. Oud >>>> On 6 Jun 2026, at 14:16, via ripe-atlas <ripe-atlas(a)ripe.net> wrote: >>> Hi, >>> Same thing is affecting five of my probes since yesterday, also with repeated messages of being asked to wait, or there having been an error: >>> 2026-06-06T12:13:24.673341015Z reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1780748131 >>> I understand that you "updated [y]our controllers so all probes disconnected for a short while" yesterday, but that is now more than a day ago? >>> Thanks! >>> Kind regards, >>> R. >>>> On 6/6/26 00:14, Marek Küthe via ripe-atlas wrote: >>>> Hello, >>>> My probe has disconnected. Could someone take a look at this? >>>> The message in the log is as follows: >>>> ``` >>>> Jun 06 00:12:48 laplace ripe-atlas[113935]: condmv: not moving, destination '/var/spool/ripe-atlas/data/out/

1 0

Controller error?
by Ernst J. Oud 06 Jun '26

06 Jun '26

And to add insult to injury… three probes down, only one gave me a status message to that effect. So never received a notification that the other two were down too. The change to the new status email template introduced some error perhaps? Regards, Ernst J. Oud

1 0

Global timeout event root DNS
by Jesse Prins 06 Jun '26

06 Jun '26

Hey all! For the final research project for my bachelor I am researching timeouts involving the Root DNS servers using RIPE atlas measurements. In my research I stumbled upon (in my opinion) a weird event that I can’t find any causes for. On the 23rd of December there was a spike (ranging from 10% - 60% depending on the server) in timeouts involving all root servers except F, G and H which don’t show any spike at all (see https://rootviz.sidnlabs.nl/public-dashboards/f81c02c68d7a4986ba1674fd7eb87…) My main question is if there were any problems with RIPE atlas itself around this time (causing an artifical spike)? and if not: Does anyone know what could have caused such a global spike in timeouts? Thanks in advance. Kind regards, Jesse Prins

1 0

Probe disconnect and reconnect emails with missing data
by Johan ter Beest 05 Jun '26

05 Jun '26

Hello Atlas friends, We recently changed the templates for the probe disconnect and probe reconnect messages. Unfortunately, there was a small mistake in the message parameters causing the email to appear essentially empty (no probe ID, no since, no probe description). This error has been fixed now. Apologies for the mistake, Kind regards, Johan ter Beest RIPE Atlas Team

1 0

Spam?
by Ernst J. Oud 05 Jun '26

05 Jun '26

Hi, Just received an email from atlas+e76c0ca5(a)ripe.net saying: —- Probe is disconnected () Ernst J., Your probe has been disconnected from the RIPE Atlas infrastructure since 2026-06-05 09:23:26 UTC. —- As shown above, no probe ID is mentioned and the sender’s email address is a bit weird since normal status messages come from no-reply(a)ripe.net. Also all my probes are functional. A test run at RIPE gone wrong? Regards, Ernst J. Oud

2 1

Atlas UI updates for 2026-05-27
by Stephen Suess 27 May '26

27 May '26

Hello Atlas friends, We have just updated the UI with a new and improved LatencyMON, as well as various other fixes and changes that you can read about here: https://atlas.ripe.net/docs/releases/website_index/2026-05-27 Please let us know if you have any questions or feedback. Kind regards, Stephen Atlas UI

1 0

Controller ctr-dub-sw01 problem?
by Ernst J. Oud 17 May '26

17 May '26

My software probe 1004467 disconnected from controller last ctr-dub-sw01 night. The CentOS VM it is running on has no problems. It has internet access. I rebooted it but that didn’t change anything. Problem with this controller not accepting connection requests? Other probes on this controller still work.. Regards, Ernst J. Oud

1 2

probe migration
by Marco Moock 17 May '26

17 May '26

Hello! In case of a hardware switch, is it reasonable to migrate the software probe to the new machine? In cases of that, which files need to be migrated? -- kind regards Marco Muell und Spam bitte an abfalleimer2000(a)stinkedores.dorfdsl.de

2 1

RIPE Atlas Credit Request — Student at UCLA conducting CGN measurement research
by Sarah 15 May '26

15 May '26

Hi all, My name is Sarah Zhao and I am a Computer Science and Engineering student at UCLA. I am currently conducting undergraduate research in computer networking at the UCLA Connection Lab under the mentorship of Professor Leonard Kleinrock. As part of my research I am studying the deployment and impact of Carrier-Grade NAT (CGN) at Internet scale. I plan to use RIPE Atlas traceroute measurements to detect CGN presence via 100.64.0.0/10 address leakage in hop paths, and TCP connect measurements to probe inbound reachability from CGN and non-CGN ASes as comparative vantage points. I need geographically diverse probes across networks in developing regions where CGN deployment is most concentrated. As a new user I have no credits and kindly ask for a donation to get started. An allocation of 200,000 credits would cover my planned measurement phases. My RIPE Atlas account is registered under: sarahzhao01(a)gmail.com I am very eager to share my findings with the community. Thank you in advance for any help! Best, Sarah Zhao UCLA Computer Science

6 7

Rollout of software probe anti farming measures
by Francesco Iannuzzelli 12 May '26

12 May '26

Dear RIPE Atlas users, Some of you may remember earlier discussions about this topic. We’re now ready to enable a feature to address this issue. Supporting each probe requires resources from the system; at the same time having too many probes in the same network and location does not provide much new information (that is, more probes in the same location or network would provide similar measurement results). Therefore we have controls in place to limit the amount of /software/ probes that are connecting from particular networks: 1. Each probe host can connect up to 2 software probes from the same IP address. 2. Each probe host can connect up to 4 software probes from the same IP prefix (as seen in BGP). 3. At most 32 (or 64) probes from the same IPv4 (or IPv6) prefix (as seen in BGP), regardless of the host. Software probes that connect from networks beyond these limits will not be allowed to connect, unless and until other software probes drop out. Note that we may also adjust the particular maximums over time. We realise that in some cases multiple probes belonging to the same user can come seemingly from the same network, violating rule 2 (mostly), yet they arguably still provide enough value for the community. This may be for example because they are in fact geographically widely distributed. In such a case the host can reach out to us via atlas(a)ripe.net with an explanation and we will consider relaxing this limit. While in the past we observed surprising corner cases, the particular limits described above are set partially taking into account the current software deployment. Therefore only a handful of probe hosts should be impacted by this (as I write this, 71 probes from 13 hosts). As I mentioned above, we’re open to adjust the limits if needed. Regards, Francesco Iannuzzelli

5 5

New LatencyMON in beta
by Stephen Suess 11 May '26

11 May '26

Hello Atlas friends, We are currently in beta testing for a modern replacement of LatencyMON. Our plan is to roll this out fairly soon, but we wanted to show it to the community first and ask for your feedback on it. Here are some of the differences from the old version: - Complete migration to Vue3/Quasar code like the rest of Atlas (no legacy jquery, requirejs, backbone, or any of that) - UI refresh and cleanup - New toggle to add groups by distance from target (in addition to the default of countries with greatest number of probes) - Showing min/med/max values (with toggle to only show min) - Groups can be split into single probe charts with button click - Link out to msm ID - Now linking to latencymon from dns/tls/http (as well as ping/traceroute) with better support for these - Fullscreen zoom - Ability to load data outside routequake (aggregated API used for latencymon) limits from regular (non aggregated) results (limit to 10k samples for now for performance) - Areas with packet loss now opacity scaled for better visibility (with tooltip note to zoom in for full data when not in full resolution) - Charts can be drag resized You can check out the new LatencyMON on our beta-ui site (https://beta-ui.atlas.ripe.net/) by going to the link at the top of any measurement detail page (for any periodic measurement). Here is an example: https://beta-ui.atlas.ripe.net/latencymon/93652781 We welcome your feedback and look forward to hearing from you. Kind regards, Stephen Atlas UI

1 0

Our website Bollywood.com is blocked, want to run probes
by Kipling Buis 11 May '26

11 May '26

Dear Members, I am system admin for website Bollywood.com. We are located in California, USA. Unfortunately, our website Bollywood.com is being blocked in India, and other nations, maliciously. We are getting traffic only from bots, and the active "user" number is around 300-400 entities daily. We want to investigate DNS/SNI/TLS level reachability of Bollywood.com from Indian ISPs to diagnose suspected censorship, or malicious filtering by Indian telcom companies. Can we get credits to run these probes on your websites? I would appreciate any help from members. Thanks, Best Regards, Kip

4 4

DNS measurement for newer record types - HTTPS & SVCB & more
by Petr Špaček 06 May '26

06 May '26

Hello! Would it be possible to add newer record types to allowed set of "query_type" parameter values for DNS measurements? Specifically I would like to use "HTTPS" and "SVCB" record types, RFC 9460, published in November 2023. On a more generic note: The filter already allows four RR types with weird corner cases - namely NS, DS, ANY, RRSIG. Based on that I think if anything wanted to explode because of RIPE Atlas DNS queries it already did. If you are open to adding more types, I think adding all standardized values from https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-pa… would be very safe and would expand utility for deployment testing of existing protocols. Even better would be to just take integer value. That's what all DNS software does - see RFC 3597 - published in 2003. With integer value we could even use RIPE Atlas for IETF work in the DNS WGs. Thank you for considering the three options above. -- Petr Špaček Internet Systems Consortium

1 0

[Probes used in measurement]
by SIPASSEUTH Adrien 05 May '26

05 May '26

Hello, I want to supervise health from my measurement with https://atlas.ripe.net/docs/apis/rest-api-manual/measurements/status-checks/ But there are all probes result even probes in "NOT parcipating" status. It is possible to removed probes in stats "NOT particpating" from a measurement ? [cid:dc3f3b43-9c0c-4082-a473-f74b19398a2d] I can't find a endpoint which remove this probes from my measruement. Regards, Adrien

2 1

Atlas UI updates for 2026-04-29
by Stephen Suess 29 Apr '26

29 Apr '26

Hello Atlas fans, We have just updated the UI with a new fullscreen view for the Region Meshes use case, as well as some under the hood changes related to the system used to log in to Atlas. In addition, we are deprecating TraceMon (in favour of Khipu) and will be removing it from Atlas after the upcoming RIPE meeting. If there is functionality that you use in TraceMon that is not available to you elsewhere within Atlas, please let us know and we will evaluate. Kind regards, Stephen Atlas UI

1 0

Requesting Credits for research
by Anugya Sharma 25 Apr '26

25 Apr '26

Hello, I am a grad student at UC Davis. I am trying to research starlink satellite users in developing countries and if their traffic is unnecessarily routed through the US. I am measuring traceroute, DNS, ping and have identified Starlink-connected RIPE Atlas probes (AS14593) in Kiribati, the Marshall Islands, Madagascar, and Guam. I would be so thankful for any credits you can provide so that I can get my measurements going. -Anugya Sharma Department of computer science, UC,Davis

4 3

RIPE Atlas: From Core Concepts to Use Cases (upcoming RIPE NCC Open House Event)
by Stephen Suess 24 Apr '26

24 Apr '26

Hi everyone, We would like to invite you to a two-part RIPE NCC Open House event on RIPE Atlas, with a particular focus on the UI. I will be giving demos and talking about numerous tools and visualisations that are available to help you understand and make sense of Atlas data. Session 1 takes place Thursday, 30 April at 13:00 (UTC+2) Session 2 takes place Tuesday, 12 May at 13:00 (UTC+2) Full details and registration: https://www.ripe.net/meetings/open-house/ripe-atlas-from-core-concepts-to-u… We look forward to seeing you there! Kind regards, Stephen Atlas UI

1 0

Atlas UI updates 2026-04-15
by Stephen Suess 15 Apr '26

15 Apr '26

Hello Atlas friends, We have just released an update to the Atlas frontend. The most notable new feature is the Region Meshes use case, which is a new RIPE Atlas tool that visualises intra-region routing paths, showing where traffic stays local, where it leaves, and how IXPs are being used. You can read about it here: https://labs.ripe.net/author/stephen_suess_1/introducing-region-meshes-visu… And you can link directly to the tool here: https://atlas.ripe.net/use-cases/region-meshes/ Additionally, you can see the full list of what has changed or been fixed in the release notes: https://atlas.ripe.net/docs/releases/website_index/2026-04-15 As always, we welcome your feedback and would love to know what you think. Kind regards, Stephen Atlas UI

1 0

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

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