March 2025 - ripe-atlas - mailman.ripe.net

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

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

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