- ripe-atlas - mailman.ripe.net

Ripe Probes clock update
by Giovane C. M. Moura 12 May '25

12 May '25

Hi Atlas folks, I was wondering if there is an update on how Atlas probes sync their clocks from the article from 10 years ago[0]. * Anchors: `pool.ntp.org` * v1: fallback mechanism using HTTP * v2 : ntpclient (but which ntp servers?) * v3: opentpd (but which ntp servers)? What about newer probes version? v4? v5? vms? Thanks, /giovane [0] https://labs.ripe.net/author/philip_homburg/ntp-measurements-with-ripe-atla…

2 1

Atlas UI update - New Internet Maps
by Stephen Suess 01 May '25

01 May '25

Hello Atlas Community, We have just released an update to the UI that completely reworks the Internet Maps section: Root Name Server Instances & RTT to well-known destinations Performance: many times faster than previous maps Sharable URLs with all params Clickable legend tags to filter probe markers Probes on maps are searchable by ID, ASN, Country, IP, Prefix Time travel up to 30 days in the past You can find these maps here: https://atlas.ripe.net/maps/ Over the next couple of months we plan to bring many of the performance improvements of these maps to other areas of Atlas as well as refining and adding to the Internet Maps collection. And as always, we hope you find these changes useful and we welcome your feedback. Kind regards, Stephen Atlas UI

2 2

RIPE Atlas API rate limits
by Huseyn Gambarov 30 Apr '25

30 Apr '25

Hello. While looking for the rate limits defined for the RIPE Atlas API, I found the mail sent by Robert Kisteleki two years ago saying: > The measurement API in particular will impose a limit of 150 queries/second (if done over multiple connections) Can you tell me please, if the requests sent to the Streaming API are also considered in this limit? Thank you. Original mail: https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/thread/7K4JC7ZZN… With regards, Huseyn Gambarov Research Assistant PhD Student in Computer Science Case Western Reserve University

1 0

bulk-email.ripe.net
by Marco Moock 29 Apr '25

29 Apr '25

Hello! Some mails regarding RIPE atlas are being sent via bulk-email.ripe.net. Is there a reason RIPE uses that 3rd party (IPv4-only) service instead of its own infrastructure? -- Gruß Marco

8 12

Newbish DNS question
by Hank Nussbacher 29 Apr '25

29 Apr '25

Perhaps a newbie question: I am doing a DNS measurement and almost all probes return NXDOMAIN (expected), yet one probe returns NOERROR. How can I determine which DNS server it is using to provide a NOERROR? See attached json. Thanks, Hank

4 3

Atlas credits fallen way below zero
by Seth David Schoen 23 Apr '25

23 Apr '25

Hi, I created some rather large measurements a few months ago. I got a notice at some point that I was going to run out of credits and that the measurements would be stopped -- something which has happened to me before. Somehow, it looks like the measurements didn't stop (or maybe did stop and were then resumed), and my account balance has gone very significantly negative before I got around to checking what was going on. I keep getting e-mail notifications warning me that my balance is nearly exhausted, but these notifications (correctly?) state that my balance is already negative, and will run out a negative amount of time into the future. Can I assume this is a backend bug, where some part of the logic for credit exhaustion wrongly assumes that one's balance is currently positive, and then never triggers after it somehow becomes negative? My dashboard page somewhat comically states Daily credit spending currently (approximately) / your limit: 7160665 / 1000000 Daily measurement result flow (approximately) / your limit: 721024 / 100000 I didn't mean to "overdraw" the system or use resources without contributing resources back; I just didn't realize the cost of some particular measurements, and had previously seen that measurements that one's account couldn't afford would in fact be terminated. Can I "declare bankruptcy" and get my balance reset to zero? And can someone take a look at the credit logic to understand how this credit overdraft phenomenon can come about? Thanks!

2 1

Atlas Account Disabled
by cassianoaquino＠me.com 22 Apr '25

22 Apr '25

Hi, I was trying to login to my atlas ripe account and forgot I had multiple authenticators configured and kept trying with the wrong one which gave me an error about the account being disabled to contact "your administrator". Now when I try to login it says "Invalid email address or password". Is there someone who can help me or point me on how to contact "your administrator"? The atlas login email is the same I use here on the mailing list. Thanks in advance!

1 0

how to delete a never used software probe
by Hans Mayer 17 Apr '25

17 Apr '25

Dear All, by a mistake I submitted the wrong SSH key during the installation of a software probe. Therefore I have now in my list of probes a second probe ID which is hidden and was never connected. Querying the Internet tells me Click on your probe and Click the "Write off your probe" function on the probe's detailed information page But when I do so I see an almost empty screen with the probe ID and "This probe was Never Connected" and nothing else. Any help is welcome. Kind regards Hans --

2 2

Decreasing number of probes
by Felix Hoffmann 09 Apr '25

09 Apr '25

Hey, I am currently running multiple scheduled measurements (ids: 85023653, 85023729, 85023782, 85023852). In the wizard, I selected the probes by area with the following settings: WW, 1000 probes. At the beginning of the measurements, mostly all probes reported, but meanwhile the number of probes reporting has decreased constantly. Is there an option to rotate the probes regularly to ensure a certain amount of active probes? Best regards, Felix Hoffmann

5 5

Atlas software probe on FreeBSD
by Marco Moock 09 Apr '25

09 Apr '25

Hello! Are there any people who have the RIPE Atlas software probe daemon running on FreeBSD? I have a virtual machine that could host a probe, although I haven't found any info if the daemon runs there. -- kind regards Marco Send unsolicited bulk mail to 1744132937muell(a)stinkedores.dorfdsl.de

2 1

Monthly probe reports for March 2025 missing?
by ripe＠nurfuerspam.de 07 Apr '25

07 Apr '25

Hi, I don't recall having seen the monthly probe report for March 2025, and also cannot find anything when explicitly looking for them. Did anyone else get the probe report for March 2025? In the past, they usually came in the very early hours of the first day of the month. Thanks! Kind regards, R.

2 2

RIPE Atlas Anchor Certificate Change
by Robert Kisteleki 07 Apr '25

07 Apr '25

Dear colleagues, We will be carrying out planned maintenance on RIPE Atlas anchors to replace the existing Lets Encrypt certificates with self-signed ones. There is no action needed by anchor hosts. The only visible change for users - should they want to visit an anchor URL using their browser - will be the standard notification asking them whether they trust the certificate before proceeding. This change is not expected to have a significant impact on functionality as the HTTPS service on RIPE Atlas anchors is not intended to be accessed by regular users in browsers but from measurements and scripts. Kind regards, Robert Kisteleki

1 0

Software Probe version 5110 released
by Trix Taiclet 02 Apr '25

02 Apr '25

Dear colleagues, We have released a new version of the RIPE Atlas Software Probe, version 5110. This 5110 release contains the following changes: * Added support for Raspberry Pi OS 12 (added Debian 12 arm64 package) * Rewrote GitHub README and BUILD instructions * Display Probe registration instructions during installation for RHEL and Debian * Generate Probe keys after installation without requiring service startup * Using the signing key introduced in 5100 to sign RHEL packages. The current RHEL key is deprecated as of this release. * Fixed compilation error by adding a missing include to telnetd.c (authored by César de Tassis Filho <ctassisf(a)gmail.com>) * Hardened the security of the RIPE Atlas service unit (reported by Marek Küthe <m.k(a)mk16.de>) * Added missing requirement for procps-ng on RHEL9 to RHEL probe package specfile (authored by Robert Scheck <robert-scheck(a)users.noreply.github.com>) * Document runtime options for custom TCP ports (authored by AtlasMUC <AtlasMUC(a)mail.de>) * Fixed typo in GitHub org url for RHEL ripe-atlas-anchor specfile (authored by Pouria Mousavizadeh Tehrani <info(a)spmzt.net>) * Fixed typo in GitHub org url for RHEL ripe-atlas-probe specfile (authored by eeple <m.renusson(a)gmail.com>) This release does not contain any functional changes to the measurement code. You can find more information and instructions on the GitHub repository: https://github.com/RIPE-NCC/ripe-atlas-software-probe/ You might have seen this release before our announcement; we faced an issue with the arm64 repo package, which caused us to delay that specific package and our announcement. Please let us know if you find any issues with this release. Regards, Trix Taiclet & Marios Mavropoulos RIPE NCC

1 0

How to set a probe non-public?
by Robby van de Meulenhof 01 Apr '25

01 Apr '25

Hello, At the moment i have 3 probes. 1 of the 3 probes i would like set non-public. With the new detail page i can't change the Shared Publicy (no checkbox like the old design) I switch to /Legacy Probe Detail/ i can *uncheck Shared Publicy* when i save it a get an error "You cannot make a public probe non-public." I can'tt find how i set a probe to non-public. How i do that? Regards, Robby

2 3

API-Key grants: There were problems with your request
by Bjoern Franke 01 Apr '25

01 Apr '25

Hi, I created a new API key and tried to set some measurements permissions. Yesterday evening and also now I'm only getting "There were problems with your request" and no grants are set. Regards Bjoern

1 0

Atlas UI and Docs updates
by Stephen Suess 25 Mar '25

25 Mar '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

1 0

Missing data in connection and uptime history for probe
by Anton Bobov 21 Mar '25

21 Mar '25

Hello! I am experiencing an issue with incorrect uptime and connection history for my probe (ID: 1006959 https://atlas.ripe.net/probes/1006959/network). I am currently running a software probe on Rocky Linux 8.10, with the probe version 5100. There was a power outage between 2025-03-14 04:25 and 2025-03-14 05:25 (UTC), which seems to have affected the data. I downloaded the connection history for the specified period, and it shows the following entries: seq timestamp (UTC) event stored_timestamp (UTC) ---------------------------------------------------------------------- 1 2025-02-08 23:13:51 disconnect 2025-02-08 23:13:51 2 2025-02-08 23:17:18 connect 2025-02-08 23:17:18 3 2025-03-14 04:25:35 disconnect 2025-03-14 04:25:36 4 2025-03-14 05:25:06 connect 2025-03-14 05:25:06 5 2025-03-14 06:49:19 disconnect 2025-03-14 06:49:19 6 2025-03-14 06:52:46 connect 2025-03-14 06:52:47 7 2025-03-15 22:36:49 disconnect 2025-03-15 22:36:50 8 2025-03-15 22:39:17 connect 2025-03-15 22:39:17 However, entries [2] to [7] are missing from the connection history, and only [1] (last disconnect) and [8] (last connect) are displayed. Additionally, this period is also missing from the uptime history. Could this be a bug, or is there another explanation for this issue? -- Cheers, Anton

2 4

Unable to remove probe's Description
by ripe＠brite.cz 20 Mar '25

20 Mar '25

Hi team, I wanted to remove the Description, before I make new one. When click Edit button, delete the description and click Save, I get "Failed to update probe info". Only if I enter any valid character then it saves fine. I would suggest to allow empty string to be saved as well, since sometimes you just want to remove the description instead of writing a new one. Cheers from Czechia Jiri

1 0

purpose of *untagged* status
by ripe.net＠toppas.net 06 Mar '25

06 Mar '25

Hi everyone, can anyone explain to me the reason of system tags not being set (for long time)? There are system tags for every case, but there's also the case, that no tag is being set. For example: ipv6-works check (three possible cases): 1. tagged: system-ipv6-works 2. tagged: system-ipv6-doesnt-work 3. untagged (none of the above tags is set) I don't see the purpose of the untagged status. Either IPv6 / IPv4 works, or not. What is the completely untagged status supposed to tell me? The same applies to DNS checks. There's a tag for every case, plus the "no-tag status": DNS resolving check: 1. tagged: system-resolves-a-correctly 2. tagged: system-resolves-a-incorrectly 3. tagged: system-doesnt-resolve-a 4. untagged (none of the above tags is set) I would like to know the condition, how the controllers (?) decide this. Or in other terms: if a system tag is removed (untagged) shouldn't this implicate, that the opposite system tag has to be applied immediately? This is not a matter of a short time period, completely untagged probes do exist for long time periods. Thanks & best regards, Simon

3 3

DNS EDE w/ ripe atlas
by Jared Mauch 05 Mar '25

05 Mar '25

1) the client on the probes, does this have the capability to return EDE in DNS measurements? I'm trying to look at something and would like to sample this if it's possible. 2) When logging in at https://atlas.ripe.net/my/ once you go through MFA it's landing on my profile page vs the oriignal URL - Hoping this is something that can be looked at easily :-) - Jared -- Jared Mauch | pgp key available via finger from jared(a)puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.

1 1

RIPE Atlas UI: Revamped Probe Detail Pages released
by Stephen Suess 05 Mar '25

05 Mar '25

Dear Atlas community: After several months of development and beta testing, we are excited to announce the launch of the new RIPE Atlas probe detail pages! The probe details area includes the following panels: * Overview: Probe info, Location, Traffic, Current Measurements (link), Well-known Targets, Uptime, Event Log * Anchor (if probe is an Anchor): Anchor Info, Sponsor/Host logos (and links), Mesh/Probe measurements, Change History * Network: IPv4/IPv4 configuration, Probe Address Discovery, Connection History/Download * Results: Grouped, zoomable time-series charts for Well-knowns and Built-ins, with traceroute popups * Manage (if user has rights): Sharing, Notifications, Transfer, SSH Key, Write-off We hope you find these pages useful and would love to hear your feedback. Additionally, users who prefer the previous version will still have the option to switch back to the legacy interface for some time. You can read more about the new features in the following article on RIPE Labs: https://labs.ripe.net/author/stephen_suess_1/ripe-atlas-ui-revamped-probe-d… Kind regards, Stephen Atlas UI

4 9

Request for Additional RIPE Atlas Credits for Large-Scale Internet Measurements
by Semebia Wurah 04 Mar '25

04 Mar '25

Dear RIPE Atlas Community, I hope this email finds you well. My name is Semebia Wurah, and I am a Research Associate at Carnegie Mellon University Africa, working under the supervision of Prof. Theophilus Benson. We are conducting large-scale traceroute measurements using RIPE Atlas to analyze the Internet ecosystem in Africa, with a particular focus on AS peering growth and IXP utilization. This research aims to quantify interconnection trends, detect inefficiencies in routing, and assess the impact of IXPs on regional traffic exchange. Given the scale of our study, we require a substantial number of credits (approximately 500,000,000) to sustain our measurements over an extended period of at least 4 months. These credits will allow us to: - Capture peak and off-peak Internet behavior by running measurements at different times of the day. - Measure interconnectivity across African ASes and IXPs to analyze how traffic is exchanged regionally. - Ensure statistically meaningful results by collecting data over multiple weeks. We truly appreciate any additional credits the community can share, as this will significantly enhance the depth and accuracy of our findings. We are happy to share insights from our research with the RIPE community. Thank you in advance for your time and support. Please feel free to reach out if you have any questions or require further details about our study. Best regards, Semebia Wurah Research Associate Carnegie Mellon University Africa -- Semebia Yaa Wurah Research Associate Pronouns: she/her/hers Carnegie Mellon University Africa Regional ICT Center of Excellence Bldg Plot No A8, Kigali Special Economic Zone Phase, Rwanda Phone: +250 798945462 | Email: swurah(a)andrew.cmu.edu

7 7

Re: Request for Additional RIPE Atlas Credits for Large-Scale Internet Measurements
by Ernst J. Oud 04 Mar '25

04 Mar '25

Semebia, Just transferred 50 million credits into your account. Good luck with your research! Greetings from The Netherlands. Regards, Ernst J. Oud > On 4 Mar 2025, at 00:59, Semebia Wurah <swurah(a)andrew.cmu.edu> wrote: > > > Thank you, Ernst! Kindly send it to swurah(a)andrew.cmu.edu. > >> On Tue, Mar 4, 2025 at 1:55 AM Ernst J. Oud <ernstoud(a)gmail.com> wrote: >> Semebia, >> >> To what RIPE account (email address) should we transfer credits? >> >> Regards, >> >> Ernst J. Oud >> >>>> On 4 Mar 2025, at 00:50, Semebia Wurah <swurah(a)andrew.cmu.edu> wrote: >>>> >>> >>> Dear RIPE Atlas Community, >>> >>> I hope this email finds you well. My name is Semebia Wurah, and I am a Research Associate at Carnegie Mellon University Africa, working under the supervision of Prof. Theophilus Benson. >>> >>> We are conducting large-scale traceroute measurements using RIPE Atlas to analyze the Internet ecosystem in Africa, with a particular focus on AS peering growth and IXP utilization. This research aims to quantify interconnection trends, detect inefficiencies in routing, and assess the impact of IXPs on regional traffic exchange. >>> >>> Given the scale of our study, we require a substantial number of credits (approximately 500,000,000) to sustain our measurements over an extended period of at least 4 months. These credits will allow us to: >>> >>> Capture peak and off-peak Internet behavior by running measurements at different times of the day. >>> Measure interconnectivity across African ASes and IXPs to analyze how traffic is exchanged regionally. >>> Ensure statistically meaningful results by collecting data over multiple weeks. >>> We truly appreciate any additional credits the community can share, as this will significantly enhance the depth and accuracy of our findings. We are happy to share insights from our research with the RIPE community. >>> >>> Thank you in advance for your time and support. Please feel free to reach out if you have any questions or require further details about our study. >>> >>> Best regards, >>> Semebia Wurah >>> Research Associate >>> Carnegie Mellon University Africa >>> >>> >>> -- >>> Semebia Yaa Wurah >>> Research Associate >>> Pronouns: she/her/hers >>> Carnegie Mellon University Africa >>> >>> Regional ICT Center of Excellence Bldg >>> Plot No A8, Kigali Special Economic Zone Phase, Rwanda >>> Phone: +250 798945462 | Email: swurah(a)andrew.cmu.edu >>> >>> ----- >>> 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/ > > > > -- > Semebia Yaa Wurah > Research Associate > Pronouns: she/her/hers > Carnegie Mellon University Africa > > Regional ICT Center of Excellence Bldg > Plot No A8, Kigali Special Economic Zone Phase, Rwanda > Phone: +250 798945462 | Email: swurah(a)andrew.cmu.edu >

3 2

How to contact probe operator
by Peter Thomassen 03 Mar '25

03 Mar '25

Hi, I'd like to dig a little deeper into some of the results we've seen last year [1] during our PQC DNSSEC measurements [2]. Questions are around the resolver software used etc. Is there a way to directly contact the operator a probe? Or do I have to resort to abuse email addresses from IP whois and the like? Thanks, Peter [1]: https://iepg.org/2024-07-21-ietf120/slides-120-iepg-sessa-field-experiments… slides 12/13: the curious Flacon AD bit via UDP (to right, turquoise histogram boxes) [2]: https://pq-dnssec.dedyn.io/ -- Like our community service? 💛 Please consider donating at https://desec.io/ deSEC e.V. Möckernstraße 74 10965 Berlin Germany Vorstandsvorsitz: Nils Wisiol Registergericht: AG Berlin (Charlottenburg) VR 37525

3 4

Re: Changes to RIPE Atlas API keys
by Ponikierski, Grzegorz 26 Feb '25

26 Feb '25

Hi! > * We'll deprecate and remove the ability to use the URL form in about a > year (around October 2024). > * We plan to send further reminders about this change over time, as well > as reaching out to heavy users of the to-be-removed format. It’s October 2024. Is this plan still valid? I admit that I have a bunch of tools which use URL form which I would have to update to use "Authorization" header. Regards, Grzegorz From: Robert Kisteleki <robert(a)ripe.net> Organisation: RIPE NCC Date: Tuesday, 19 September 2023 at 12:11 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Changes to RIPE Atlas API keys Dear RIPE Atlas users, We'd like to update you on some upcoming changes regarding API keys in RIPE Atlas. TL;DR nothing changes regarding how you can use your API keys in the short term - as long as you're actually using them. However, we'll change how unused or forgotten keys are handled as well as remove the less secure in-URL use of them. At the moment RIPE Atlas users can query their existing API keys via the UI and API, including the possibility to retrieve old keys. In order to improve the security of how we handle these, we'll introduce the following changes in October 2023: * The listing (retrieval) of keys will only reveal parts of the keys (enough to identify them) in the API as well as in the UI. * We'll add the ability to "regenerate" an API key, which will replace the secret UUID of the key while keeping exactly the same permissions. * Unused API keys will automatically be frozen after 1 year of not being used. Active keys (i.e. the ones that have been used at least once) will not be frozen. You still have the ability to save your keys until these changes are done and, as written above, you will be able to regenerate them later. We'll notify this list when the changes are about to be done. In addition, in order to further increase the security of our system, in the long run we'll make changes about how these API keys are communicated to the API: * At the moment the API accepts these either in HTTP headers ("Authorization" header) or in the URL (?key=xyz), although the Authorization header version has been documented as the preferred version for some time. * We'll deprecate and remove the ability to use the URL form in about a year (around October 2024). * We plan to send further reminders about this change over time, as well as reaching out to heavy users of the to-be-removed format. Regards, Robert Kisteleki RIPE Atlas team -- ripe-atlas mailing list ripe-atlas(a)ripe.net<mailto:ripe-atlas@ripe.net> https://urldefense.com/v3/__https://lists.ripe.net/mailman/listinfo/ripe-at…<https://urldefense.com/v3/__https:/lists.ripe.net/mailman/listinfo/ripe-atl…>

2 5