- ripe-atlas - mailman.ripe.net

new all-time low in monthy probe report mails
by Gert Doering 02 Aug '26

02 Aug '26

Hi, the monthly reports for the Atlas probes have received a new lower watermark... now I get mails that have a HTML body "with relevant information", and a text body that has basically boilerplate, and and an unsubscribe link (see below). If you send MIME/Multipart, the different parts MUST be identical to be any useful. If you can't ensure that the text/plain part is meaningful, much better to not include it at all. Unfortunately, the readability of the HTML body also reached a new low - it was sort-of-ok-but-annoying in the last months, now it's the usual "optimized for outlook prettyprinting" with a full page of boilerplate and font definitions, and relevant information buried under tons of HTML tags. This is supposed to be a simple table with useful information, not a marketing brochure where "perfect rendering and colours and fonts" is where everyone gets excited about. Which brings me to "why should I want to support this effort at all anymore, if people so obviously do not care what *I* want?"... gert ----- Forwarded message from RIPE Atlas <atlas+3616a83f(a)ripe.net> ----- Date: Sat, 01 Aug 2026 02:06:24 +0000 From: RIPE Atlas <atlas+3616a83f(a)ripe.net> To: Gert Doering <gert(a)space.net> Subject: Monthly probe report for probe #50014 v4 beta probe??? **RIPE NCC** Stationsplein 11, 1012 AB, Amsterdam This email was sent to gert(a)space.net You've received this email because you are registered as a RIPE Atlas probe host. [Unsubscribe](https://r.bulk-email.ripe.net/tr/un/SJYBU8c0ZIM62k2wnWdTQrAVQm… ----- End forwarded message ----- Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Karin Schuler, Sebastian Cler Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: Dr. Frank Thiäner D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

4 5

RIPE Atlas UI updates for 2026-07-29
by Stephen Suess 29 Jul '26

29 Jul '26

Hello Atlas users, We have just pushed another update to the UI. Among the highlights: - You can now set notification email format (in Preferences) to text or html. Please note that as we have moved to a new email sending system, for a short while still there may be an email here or there that needs reworking or is in the process of being converted. - We have replaced the charting library used for many Atlas charts with Apache e-charts. - We have fixed numerous other issues related to measurement cloning, historic data display in LatencyMon, and more. You can see the full list of what has changed in the release notes here: https://atlas.ripe.net/docs/releases/website_index/2026-07-29 Please let us know if you have any feedback or encounter any issues. Kind regards, Stephen Atlas UI

2 1

Firmware updates for v3 probes
by Urban Suhadolnik 29 Jul '26

29 Jul '26

Hi, Do older RIPE probes get updates? I have just recently revived this v3 probe. Best, Urban

3 2

Global timeout event root DNS
by Jesse Prins 23 Jul '26

23 Jul '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

2 1

Request for small Atlas credits for personal network measurement study
by 考生-高亚杰 22 Jul '26

22 Jul '26

Hello everyone,              I am a beginner learning internet measurement with ripe-atlas-tools. My RIPE account email is 2820665306(a)qq.com, my current credit balance is zero so I can't run ping and traceroute tests for study. If anyone has spare credits to donate me about 10000cr, I will really appreciate it. All my measurements are only for personal learning, no commercial use at all.              Thanks very much for your help!

3 2

UI: "Reuse from existing measurement" probe selection
by Lukas Tribus 17 Jul '26

17 Jul '26

Hello, when I'm using the "Reuse from existing measurement" probe selection method, only a single probe (the last probe looks like) from the existing measurement is used, not as expected all the probes from the existing measurement. The low expected daily cost is a good indicator for this as well, a part from actually starting a measurement and confirming that it only contains a single probe. I tried with a new and empty Google Chrome profile just to exclude any interaction with Firefox, browser caches, or the FF extensions I use, and the behavior is clearly reproducible. The UI also suggest that using a *subset* of the probes selected in a previous measurement is possible, however I have not found a way to actually select probes. The arrow pointing down is not doing anything for me (just endlessly loading nothing). This could absolutely be an embarrassing PBKAC issue, considering that I just spent an undisclosed amount of time the other day to diagnose why my anchor selection didn't work for the HTTP requests I was trying to run (of course it's not that you can only run HTTP requests from anchors, it's that you can only run HTTP requests *against* anchors as a target...). Thanks, Lukas

2 3

RIPE Atlas UI updates for 2026-07-15
by Stephen Suess 15 Jul '26

15 Jul '26

Hello Atlas friends, We have just pushed an update to the UI. Among the highlights: - Anchor management refresh: We have redesigned the "My Anchors" dashboard card and rebuilt the anchor change request forms. You can find more details in the Anchor Management documentation: https://atlas.ripe.net/docs/howtos/anchors/anchor-management - Rebuilt probe registration: The hardware and software probe registration forms have both been rebuilt from the ground up, replacing the legacy versions, and there is now a dedicated software probe install page to walk you through setup. - Probe details improvements: Your probe overview will now tell you when a probe is on hold due to a farming violation, and a software probe's current SSH key is now shown on its Manage tab. You can see the full list of what has changed in the release notes: https://atlas.ripe.net/docs/releases/website_index/2026-07-15 As always, we welcome your feedback and would love to know what you think. Kind regards, Stephen Atlas UI

1 0

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