- ripe-atlas - mailman.ripe.net

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

upgrading 5080 swprobe to 5100 on Debian loses config?
by Alexander Bochmann 25 Feb '25

25 Feb '25

Hi - I tried upgrading a software probe that runs on Debian from version 5080 to the 5100 binaries provided by the project, and while the old atlasswprobe package is being removed, it seems there is no attempt to migrate the existing probe key or other configuration? What's the recommended path here, back up the key and copy it into the new configuration directory, or just start a new probe from scratch? Alex.

4 5

Call for presentations for LACNIC's Internet Measurments WG (IMWG) in Sao Paulo
by Elisa 24 Feb '25

24 Feb '25

Hi all, Call for presentations is now open! Seeking presentations on Internet Measurements (including, but not limited to, Atlas). The Internet Measurements Working Group session will be held at the LACNIC43 meeting in Sao Paulo, Brazil, on May 5-9. Presentations can be remote or in-person. Submission deadline April 18. Instructions: https://listas.nog.lat/archives/list/imwg@listas.nog.lat/thread/3NZZPT3PWRP… Kind regards, -- Elisa Peirano *Analista de Datos I+D* R&D Data Analyst /www.lacnic.net <http://www.lacnic.net> Latin American and Caribbean Internet Addresses Registry/

1 0

Porting RIPE Atlas to Microcontrollers
by Urban Suhadolnik 18 Feb '25

18 Feb '25

Hi, I would like to port RIPE Atlas probes to ESP32 as part of my Master's project at TU Graz. Usage of microcontrollers could be an interesting approach to increase the physical availability of probes and to decrease the cost and energy usage. Would it be possible to get some support in this endeavour from the Atlas dev team? I would need some help with the communication with Atlas servers. Best, Urban Suhadolnik

3 3

I don't receive a one-time code when I'm trying to log in
by Vasileios Giotsas 08 Feb '25

08 Feb '25

Hi folks, When I'm trying to login, after entering my email address and password, I'm being asked to enter a one-time code. However, I don't receive any such email with a one-time code. I've tried multiple times, different browsers and also checked spam folder but it seems it's not sent. I managed to log in using the recovery codes (miraculously I didn't lose them :) ) but there seems to be a bug with send the one-time code. Best, Vasilis

4 5

Ask For Credit for Traceroute Measurements
by Semebia Wurah 06 Feb '25

06 Feb '25

Hello everyone, I hope this 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 traceroute measurements using RIPE Atlas to analyze the Internet ecosystem in Africa, focusing on the growth of AS peering and IXP utilization. Our research aims to provide insights into the region’s interconnection landscape and help identify opportunities for improving local traffic exchange. We would greatly appreciate any credits you can share to continue our measurements. These credits will enable us to perform additional traceroutes and expand our analysis. Please let me know if you need any further information. Thank you in advance for your time and support! Best regards, Semebia Wurah -- 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

4 3

Credits Available
by Daryl Morse 06 Feb '25

06 Feb '25

Hello, I have credits available. Let me know who you are, how many you need and what you will do with them. Regards.

1 0

Re: Ask For Credit for Traceroute Measurements
by Ernst J. Oud 06 Feb '25

06 Feb '25

Semebia, Just transferred 10 million credits to your e-mail address. Let me know if you need more. Wishing you success with your research. Regards, Ernst J. Oud > On 5 Feb 2025, at 23:59, Semebia Wurah <swurah(a)andrew.cmu.edu> wrote: > > > Thank you, Ernst! Kindly send it to swurah(a)andrew.cmu.edu > >> On Thu, Feb 6, 2025 at 12:57 AM Ernst J. Oud <ernstoud(a)gmail.com> wrote: >> Semebia, >> >> Nice! No problem. To what email address should I transfer 10 million credits? >> >> Regards, >> >> Ernst J. Oud >> >>>> On 5 Feb 2025, at 23:48, Semebia Wurah <swurah(a)andrew.cmu.edu> wrote: >>>> >>> >>> Hello everyone, >>> I hope this 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 traceroute measurements using RIPE Atlas to analyze the Internet ecosystem in Africa, focusing on the growth of AS peering and IXP utilization. Our research aims to provide insights into the region’s interconnection landscape and help identify opportunities for improving local traffic exchange. >>> >>> We would greatly appreciate any credits you can share to continue our measurements. These credits will enable us to perform additional traceroutes and expand our analysis. >>> >>> Please let me know if you need any further information. Thank you in advance for your time and support! >>> >>> Best regards, >>> Semebia Wurah >>> >>> -- >>> 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 > MSc Electrical and Computer Science > 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 >

1 0

Open postdoc position at HPI, Potsdam
by Vaibhav Bajpai 04 Feb '25

04 Feb '25

Dear colleagues, I am currently seeking a full-time postdoctoral researcher to join my chair (Data- intensive Internet Computing) at the Hasso Plattner Institute, Germany. We do systems research, and publish papers at the intersection of Internet measurements, security and privacy. We actively use RIPE atlas in our measurement projects. The work place is in Potsdam (near Berlin), Germany. Interested candidates, please apply here: https://jobs.plattnerfoundation.org/HPI/job/Potsdam-Postdoctoral-Researcher… Kind regards, -- Vaibhav ------------------------ Prof. Dr. Vaibhav Bajpai, www.vaibhavbajpai.com

1 0

Credits for an assignment
by Stuhrberg, Florian 03 Feb '25

03 Feb '25

Dear all, I hope you are doing well. My name is Florian Stuhrberg, and I am a master's student at Hasso-Plattner-Institut in Germany. As part of an assignment, I am currently investigating in DNS over UDP and DNS over TLS response times, using the RIPE Atlas and the corresponding API. However, after my measurements for DNS over UDP, I do not have sufficient credits to conduct the measurements for DNS over TLS. Is it possible that you could kindly share some RIPE Atlas credits, so that I can finish the assignment? Please feel free to let me know if you need any more information. Thank you in advance. Kind regards, Florian Stuhrberg

4 3

Why measurements using api are apt to fail while those using web interface can usually succeed?
by 孙乐童 02 Feb '25

02 Feb '25

Dear all, I have been attempting to use Atlas to launch traceroute measurements recently. Initially, I used ripe.atlas.cousteau to run the measurements in batches, keeping the total number under 10,000 to avoid exceeding the measurement limit. However, only 10% of the measurements returned successful results, while the other 90% showed the status "scheduling denied." Next, I tried launching only 12 measurements in batch, where each measurement contained one traceroute from a specific probe to a designated IPv4 destination. Out of these, 4 succeeded and the other 8 showed the status "specified". Following that, I launched the 12 measurements one by one with 2-second intervals, resulting in a success rate of 6 out of 12. However, when I increased the interval to 3 seconds, the success rate dropped to 4 out of 12. Interestingly, when I created the same measurements for the designated probes and destinations through the web interface, all of them were successful. Below is the Python code I used to launch the measurements: fromripe.atlas.cousteauimport ( Traceroute, AtlasSource, AtlasRequest, AtlasCreateRequest, AtlasResultsRequest, AtlasLatestRequest, ProbeRequest ) traceroute=Traceroute(af=4, target=dstip, description="traceroute subpref ip {} from {}{}".format(dstip, probe_type, probe_value), protocol='ICMP') if probe_type =='asn': probe_value =int(probe_value) source = AtlasSource(type=probe_type, value=probe_value, requested=1, tags={"include": ["system-ipv4-capable"]}) _key = ATLAS_API_KEY_2 for _ inrange(2): atlas_request = AtlasCreateRequest( start_time=datetime.utcnow() + timedelta(random.randint(0, 1)), key=_key, measurements=[traceroute], sources=[source], is_oneoff=True ) (is_success, response) = atlas_request.create() if is_success: print('create_task', dstip, is_success, response) msm_id = response['measurements'][0] return Could you kindly let me know if there might be an issue with my approach or provide any advice on how to improve this process? I would greatly appreciate any guidance. Thank you very much! Best regards, Sun Letong

4 7

Ripe Atlas Measurement Results and API Usage
by Huseyn Gambarov 30 Jan '25

30 Jan '25

Hello. I was implementing a mechanism to read the measurement results from the Ripe Atlas for many asynchronous measurements. In this process, I have faced multiple questions regarding the internal mechanisms of Ripe Atlas, and I would be thankful if you could help me clarify them. First, in the Ripe Atlas, I sometimes get “-1” in the result indicating 100% packet loss and sometimes very long RTTs. Can you tell me please what is the condition when Ripe gives up on a target and marks it as "-1”? Second, I have implemented asynchronous reading using web sockets and faced a rate limit on several concurrent web socket connections. The error message said: 'There are too many connections from this IP address. Try making multiple subscriptions on the same connection.’ Can you tell me please, if there is a limit on the number of subscriptions on the same connection? To solve the issue in the second question, I implemented a polling mechanism that periodically checks if the measurement is finished. In order to not overload the API, I attempted to retrieve multiple measurement results in a single call using the following API endpoint: GET /api/v2/measurements/{pk}/latest/ The documentation of that API endpoint states: "Get the most recent results from one or more measurements”. However, I need help understanding how to specify multiple measurement IDs in this endpoint, because all options I tried failed with HTTP status code 405 (Method Not Allowed). Could you please show me the correct way of using this API endpoint? Thank you! With regards, Huseyn Gambarov

3 2

Atlas UI: Redesigned Probe Detail Pages in Beta
by Stephen Suess 29 Jan '25

29 Jan '25

Hello Atlas friends, We’re excited to announce the early beta release of our redesigned probe detail pages in the Atlas UI. Over the past few months, we’ve been rethinking the structure and usability of these pages, and we’re sharing this early version to gather your feedback as we continue to develop and refine the design and features. Here’s how they are organised: - Overview: Probe information, map, traffic chart, links to measurements, and well-known target stats. - Network: IPv4/IPv6 overview and history. - Results: Grouped time-series charts for well-known targets and built-in measurements. - Manage: Tools for Sharing, Notifications, Transfer, SSH Key management, and Write-off. This release is very much a work in progress, and you can expect further changes and improvements as we iterate on the design and features. You can try it out by enabling the beta toggle in your preferences (https://atlas.ripe.net/prefs) We’d love for you to explore the new design and share your thoughts—your feedback will be instrumental in shaping the final version. For the full release notes you can go here: https://atlas.ripe.net/docs/releases/website/2025-01-28.html Thanks for being part of the community, and we look forward to hearing from you. Kind regards, Stephen Atlas UI

3 2

weird probe "outage"
by Sulev-Madis Silber 28 Jan '25

28 Jan '25

i just recently got message that my 65133 mox probe is offline according to status logs, it was offline for a ~week before this notice was sent out. notices are sent after 30min offline i didn't touch probe nor network nor do i know why that report was late or whether it even was really offline this is some recent issue maybe? or brand new issue? sos shows probe itself is up since i got it, 3+ months

1 0

Schroedinger's AAAA?
by Peter Eckel 28 Jan '25

28 Jan '25

I have a strane effect with probe 10293. Under "System Tags" I have both "Resolves AAAA Correctly" and "Resolves AAAA Incorrectly" listed. Apparently only one of the tags can be correct - or am I missing something? Best regards and seasonal wishes, Peter.

5 4

Oddity in "atlas-probe-traffic" measurement data/graph
by ripe＠nurfuerspam.de 28 Jan '25

28 Jan '25

Hi, Probes report the traffic volume they see on the device's/machine's interfaces in built-in measurement #9002 (on software probes, this needs to be enabled manually for privacy reasons). I use that to keep an eye on the behavior/health of the probe's host machine via the graphs generated by RIPEstat, which works well most of the time. Sometimes, however, there is an oddity in the data, namely extreme outliers. See attached graph, showing a peak of greater than 6.6 Gbps, when the "normal" traffic rarely exceeds 2Mbit/s. The underlying data shows an unusual high amount of bytes/packets sent/received for one instant that is pretty much impossible, here the data points around the anomaly (from [1]): [...] { "timestamp": 1736330734, "bytes_recv": 70881.58333333333, "bytes_sent": 63566.92222222222, "packets_recv": 737.8166666666667, "packets_sent": 700.6, "interfaces": [ "eth0" ] }, { "timestamp": 1736330921, "bytes_recv": 925866981.9732621, "bytes_sent": 820879052.6524065, "packets_recv": 8351935.347593583, "packets_sent": 8177239.866310161, "interfaces": [ "eth0" ] }, { "timestamp": 1736331101, "bytes_recv": 106008.85555555555, "bytes_sent": 88055.43333333333, "packets_recv": 1100.5944444444444, "packets_sent": 971.6666666666666, "interfaces": [ "eth0", "he-ipv6" ] }, [...] I think I've seen similar behavior on all of my software probes at one time or another, don't recall whether this also previously occured with my HW probe. So far, I have not been able to manually reproduce this, but it seems this is typically related to issues in communication with the controller, be it something on the controller side, like was more frequent/pronounced during the migration to the new controller infrastructure. Be it something on the probe side, e.g., temporary issue in network stack configuration. My current hypothesis is that when the probe cannot send off the measurement data, the accumulated data _for this particular measurement type_ is somehow getting corrupted, and the corrupted data is then sent once the communication issues are resolved, and data upload resumes. E.g., in this case, from the logs, it looks as if a reregistration with the controller was being done during minute 10:08, with the measurement data for #9002 taken just when the re-registration started. Not sure whether that is just coincidence, or whether there is a causal relation between the two. Anyone else seeing something similar, occasionally at least? Any idea what might be going on? (Have not gotten too far yet scouring through the probe/measurement code to see whether that yields any hints.) Thanks! R. [1] https://stat.ripe.net/data/atlas-probe-traffic/data.json?probe_id=1008486&m…

2 2

Small upcoming change in measurement metadata daily dumps
by Robert Kisteleki 28 Jan '25

28 Jan '25

Hello, We plan to make a small change in the measurement metadata daily dumps available at https://ftp.ripe.net/ripe/atlas/measurements/. Up until now these files contain the "current working set" which is defined as any measurement that runs right now or has been running in the past 14 days. (This also means that there's considerable overlap between today's and yesterday's dump.) We'll shorten this period to 7 days in early February. This has zero effect on the vast majority of our users. Those who periodically download and use these files with lower than 7 day frequency will need to update their scripts accordingly. Regards, Robert Kisteleki for RIPE Atlas team

1 0

Iso installation issue with RIPE Atlas anchor for LACNIC (uy-mvd-as28000)
by Elisa 07 Jan '25

07 Jan '25

Good morning, We received the ISO image to install the anchor but we encountered an issue. When we execute the "Install RIPE NCC Atlas Anchor" (see image) at some point the machine tries to resolve ks.atlas.ripe.net <http://ks.atlas.ripe.net/>, but it isn't connected to the network yet because to connect to the network we have to be inside the operating system, the installation process can't continue. We've been following instructions in: https://atlas.ripe.net/docs/howtos/installing-atlas-anchor.html and the machine has the following characteristics: 1 CPU type x86-64-v2 4 GB ram 50 GB disco Se carga la iso del disco local de Proxmox Can you help us move forward? Kind regards, -- Elisa Peirano *Analista de Datos I+D* R&D Data Analyst /www.lacnic.net <http://www.lacnic.net> Latin American and Caribbean Internet Addresses Registry/

2 2

Re: Ask for credits for my experiment.
by Departamento de Conectividad | Adam 07 Jan '25

07 Jan '25

Hi, Here comes 100 million from Adam. Enjoy them! Greetings. Ferran Pons • Departamento de NOC <Tel:+34> Tel:+34 934 465 000 / +34 911 161 770 email: <mailto:ferran.pons@adam.es> ferran.pons(a)adam.es <http://www.adam.es/> www.adam.es <https://www.linkedin.com/company/adam-tic> <https://twitter.com/adam_tic> <https://adam.es/conectividad/interconexion> <https://adam.es/politica-privacidad> Aviso Legal / Protección de datos No imprimas si no es necesario. Protejamos el Medio Ambiente. On Tue, 7 Jan 2025 at 14:26, YUNPENG XING < <mailto:xingyunp123@gmail.com> xingyunp123(a)gmail.com> wrote: Hello everyone! I hope this message finds you well. My name is Yunpeng Xing, and I am a master's student at Tsinghua University in China. I am currently working on an experiment to test the performance of global DNS Anycast using RIPE Atlas. However, I do not currently have any credits for this purpose. I would greatly appreciate it if you could kindly provide me with some credits to facilitate my research. Please let me know if you need any further information. Thank you for your time and consideration. Best regards, Yunpeng Xing ----- 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/

1 0

Ask for credits for my experiment.
by YUNPENG XING 07 Jan '25

07 Jan '25

Hello everyone! I hope this message finds you well. My name is Yunpeng Xing, and I am a master's student at Tsinghua University in China. I am currently working on an experiment to test the performance of global DNS Anycast using RIPE Atlas. However, I do not currently have any credits for this purpose. I would greatly appreciate it if you could kindly provide me with some credits to facilitate my research. Please let me know if you need any further information. Thank you for your time and consideration. Best regards, Yunpeng Xing

4 3

Probe on ctr-dub-hw01 disconnected
by Ernst J. Oud 25 Dec '24

25 Dec '24

Hi, My probe 55795 disconnected from ctr-dub-hw01. Could it be that this controller has an issue? My other probes on other controllers are fine. Regards, Ernst J. Oud

2 4

Conflicting tags for resolver
by RIPE 22 Dec '24

22 Dec '24

Hi, I just noticed my probe (1008458) shows a strange status: System Resolves A or AAAA Records Incorrectly But looking at the tags I see both the resolves correctly and the resolves incorrectly tags are set for both A and AAAA. That looks like a strange combination of tags. Any idea what’s causing this ? Cheers, Paul

1 0

cannot forward src on fbsd
by Sulev-Madis Silber 21 Dec '24

21 Dec '24

i have fbsd box with pf that routes my traffic i get this endlessly: cannot forward src fe80:24::4e6d:580f:fc89:81ae, dst 2001:7d0:8437:13bf:da58:d7ff:fe 03:1274, nxt 58, rcvif vlan3, outif vlan91 cannot forward src fe80:24::4e6d:580f:fc89:81ae, dst 2001:7d0:8437:13bf:da58:d7ff:fe 03:1274, nxt 58, rcvif vlan3, outif vlan91 cannot forward src fe80:24::4e6d:580f:fc89:81ae, dst 2001:7d0:8437:13bf:da58:d7ff:fe 03:1274, nxt 58, rcvif vlan3, outif vlan91 sometimes androids do this a few times, but probes do it all the time. multiple hw ver probes. for a decade i get few obscure results when i look that up but don't know what this is or why i tried to sniff and iirc i found weird icmp ttl exceeded packets i think kernel is correct on that cannot forward part. i'm unsure what measurements my probes actually run the src is apparently some linklocal, dst is my probe v6, recv if is vlan3, this is my v4/v6 wan to isp, out is vlan91, this is dedivated v5 probe vlan in local network did i misconfigure something or isp or ripe or else or? does it affect measurements? i'm not sure what this issue is. i think you can't forward that traffic indeed, from ll ip to global ip? google doesn't help to even shed some light on this weird behaviour, let alone any fix doesn't bother me, just curious i'm not surprised, as this device sends and receives traffic i don't have any control of. and is specifically ip measuring device so, unsure... about all this!

1 0

Requested and participating probes
by Huseyn Gambarov 13 Dec '24

13 Dec '24

Hello. I am currently working on a project that heavily relies on Ripe Atlas Ping measurements. During the development, I noticed that sometimes when, let’s say, I request 3 probes, only 2 are participating in the measurement. In the Ripe Archive, I found that there was a similar discussion here - https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/thread/D6QZS4WC5… I have two questions, that I could not find answers to, and I would be very grateful if you could help me with them. First, in the mentioned discussion it is said that there are multiple reasons why fewer probes are participating and there is ongoing work to allow users to obtain information about specific conditions that occurred during the measurement creation. Can you tell, if there is a way to get that information via API? Second, do you know if there is a reasonable timeout to wait before a new attempt to reschedule the probe that failed to participate in the first measurement? Thank you for your help. With regards, Huseyn Gambarov.

2 1

Understanding how to use the `paris` parameter
by Bhaskar, Abhishek Vasisht 13 Dec '24

13 Dec '24

Hello y'all! I'm a PhD student from Georgia Tech and had a question about the "paris" field when performing traceroute measurements. The RIPE documents states that ```Paris - A number greater than 0 will indicate the number of variations to be used for a Paris traceroute. Setting the value to 0 makes the measurement use the standard traceroute``` But regardless of what Paris value I give to the traceroute measurement, I only get one path with a single paris_id. I would expect that if I gave a paris value of 10, I should see 10 potential variations of the path between A and B, correct? Please correct me if I'm wrong. Here is an example measurement https://atlas.ripe.net/measurements/84562046 Thanks! -- Abhishek Vasisht Bhaskar Student, PhD in Computer Science Georgia Institute of Technology https://abhishekvasishtb.github.io/

1 0

MTU tracepath in RIPE atlas
by Marco Moock 12 Dec '24

12 Dec '24

Hello! Maybe some people here know the Linux tracepath application. It tests the PMTU to a destination. Could such a feature be implemented in RIPE Atlas? -- kind regards Marco Send unsolicited bulk mail to 1734020167muell(a)stinkedores.dorfdsl.de

1 0

Join Us for the "Exploring the RIPE Atlas UI" Webinar on 17 December 2024
by Michela Galante 11 Dec '24

11 Dec '24

Dear all, We are excited to invite you to the upcoming Exploring the RIPE Atlas UI Webinar, scheduled for Tuesday, 17 December 2024. Join Stephen Suess for a 45-minute webinar showcasing the key features and tools of the RIPE Atlas UI. This interactive session is designed to enhance your understanding and usage of this powerful platform. By the end of this webinar, you will be able to: • Identify and utilise key RIPE Atlas UI features to efficiently find and analyse existing Internet measurements. • Evaluate various data visualisation and analysis tools to gain meaningful insights from measurement results. • Customise the RIPE Atlas UI to suit specific usage patterns and prioritise the information you need. For more information and to register, please visit: https://learning.ripe.net/w/courses/64-exploring-the-ripe-atlas-ui/305 Kind regards, Michela Galante Senior Community Development Officer RIPE NCC

1 0

Re: Transfer of Atlas anchor ownership
by Robert Kisteleki 03 Dec '24

03 Dec '24

Hi, Can you please see to this change request? Thanks, Robert On Thu, Nov 28, 2024 at 4:05 PM Luuk Hendriks <luuk(a)nlnetlabs.nl> wrote: > Hi Robert, > > > We'd like to transfer the ownership of the Atlas anchor that I installed > at the University of Twente many moons ago. It's attached to my personal > account and we could not find a way to transfer it via the web > interface. > > It's anchor ID 6113, currently under ripe(a)luukhendriks.eu > and should go to Roland's account, roland(a)nlnetlabs.nl . > > > If there's anything more you need from me, please let me know. > > > Cheers, > luuk >

1 0

Probe #2413 somehow failing
by ripe＠brite.cz 29 Nov '24

29 Nov '24

Hi team, please have a look at Probe #2413, it shows connected but it seems it is not providing any measurements results. I tried different cables, power sources, connected to different switch, and finally move it to completely different location. It is v1 so it does not have USB memory stick. Please advise. Thanks Jiri

7 8

Streaming result data missing probe information with "enrichProbes: true"
by Wouter de Vries 27 Nov '24

27 Nov '24

Hi folks, When using the Streaming API there is an option called "enrichProbes" which should cause probe metadata to be added to every result. That seems to have worked for a while, but it has stopped working. Example code (in python) to reproduce (it's the example from the docs, with just enrichProbes set to true): import json import websocket ws = websocket.WebSocket() ws.connect("wss://atlas-stream.ripe.net/stream/") params = {"streamType": "result", "msm": 1001, "enrichProbes": True} ws.send(json.dumps(["atlas_subscribe", params])) for data in ws: print(data) Example result: ["atlas_result",{"fw":5080,"mver":"2.6.2","lts":66,"dst_name":"193.0.14.129","af":4,"dst_addr":"193.0.14.129","src_addr":"192.168.1.20","proto":"ICMP","ttl":56,"size":32,"result":[{"rtt":21.447667},{"rtt":21.226292},{"rtt":21.253375}],"dup":0,"rcvd":3,"sent":3,"min":21.226292,"max":21.447667,"avg":21.3091113333,"msm_id":1001,"prb_id":50274,"timestamp":1731917452,"msm_name":"Ping","from":"85.107.81.62","type":"ping","step":240}] As you can see there is no probe metadata present. I'm fairly sure I'm doing this right and I think this worked previously. Is something broken in the backend? Best regards, Wouter

2 2

UI feature wish: "Daily Credits Balance" pie chart widget
by ripe＠nurfuerspam.de 26 Nov '24

26 Nov '24

Hi, I very much like/liked the "Daily Credits Balance" pie chart widget from the old UI dashboard (https://atlas.ripe.net/my/) It gives an instant overview of the credit revenue and expenditure stream, not only the grand total, but also the _share_ of individual probes and measurements in the revenue and expenditure streams. With the actual number being shown when hovering over an individual slice of the pie. And clicking on a slice would take one to the page of the respective probe or measurement (though it seems currently broken for measurements, possibly because of the ongoing restructuring). Is there a way to get it back in the new dashboard, refreshed obviously, and integrated into the new overall site layout? Thanks! Kind regards, R.

2 1

Probe flash drive corrupted
by Michael J. Oghia 20 Nov '24

20 Nov '24

Hi team, all: I just checked my dashboard, and one of my probes is offline. The error message says: "Your probe was automatically untagged as "system: Flash drive filesystem corrupted." Does anyone know how to fix it? Or does it require me to change the probes? If the latter is the case, how can I go about doing that? Kind regards, -Michael

2 4

Feature idea: new status "Probe (temporarily) closed for new UDMs"
by ripe＠nurfuerspam.de 20 Nov '24

20 Nov '24

Hi, Obviously, measurements are the purpose of being of the RIPE Atlas system. Thus, e.g., I take greate care to maximize probe uptime so measurements scheduled on them don't get disrupted by local events that are likely not representative of what most measurements are looking at. However, sometimes, temporary disruption may be known to come up, but is unavoidable, e.g., for maintenance of, or around the probe. Or a probe needs to be taken out of service "for good". In those cases, it is obviously hardly possible to avoid long-running measurements from being impacted, either by a short-term disruption, or by the removal of a probe altogether. And measurement owners obviously are aware of that, and need to take that into account in a way specific to each measurement's purpose. And it is obviously possible to remove, e.g., defunct probes from a running measurement and replace them with new ones. However, when a probe host knows _ahead of time_ that their probe will experience some event potentially disrupting measurements (like during planned maintenance activities), or will have to be decommissioned at a specific time in the future, how about if they could signal that condition to the Atlas infrastructure, and the infrastructure would at least not schedule _new_ measurements on such probes? E.g., by having a new probe "status" that can be explicitly set by the probe host to say, "this probe shall (perhaps just temporarily) not get any _new_ UDMs scheduled at this time (while the status is set)". Just a thought, not sure how much effort that would be to implement, and whether that would be worth the benefit of disrupting "fewer" measurements in case of foreseeable issues with a probe (or anchor), especially also upon an upcoming need to decommission one entirely. Thanks! Kind regards, R.

1 0

Re: [opensource-wg] RV: [ripe-list] Update on the Community Projects Fund 2024
by Rodolfo García Peñas (kix) 18 Nov '24

18 Nov '24

Hello, I would like to congratulate all the projects selected by the Community Projects Fund. I also wish to express my gratitude to the organising committee for initially selecting our project, 'RIPE Atlas distributed network telescope'. I am currently engaged in doctoral research on IBR traffic, and together with my supervisory team, we have proposed this project. We saw this as an ideal opportunity for the community to collect IBR traffic and make it available. We currently have a small working network of sensors (HoDiNT, Home Distributed Network Telescope [1]) and our objective is to extend the network and have RIPE manage the traffic collected. The HoDiNT sensors receive IBR traffic forwarded from the home connection router and forward it to a collector for analysis. They are fully compatible with Atlas sensors. This would enrich the traffic of other research centres, such as CAIDA or Merrit, and offer other students and research centres the possibility of having IBR traffic available for analysis. I was delighted that our project was selected, but a few hours later the organisation sent us an email stating that the RIPE Atlas team had raised some concerns about our proposal which may impact our ability to receive funding. We were requested to attend a meeting with the organisation and the RIPE Atlas team to discuss the proposal a few days later. The meeting was unfortunately not attended by a representative of RIPE Atlas. We were informed that the project was not deemed feasible. I would like to thank Alastair, who had to pass on the news to us, which is not an easy situation. I accept the decision taken, although I do not agree with either the substance or the form. I think we should have been given the opportunity to reformulate the project, maintaining the original objective but circumventing the limitations exposed. We will continue to improve HoDiNT in order to make it available to the community as soon as possible. If anyone is interested in contributing to the project, improving the code (mainly Python) and/or hosting sensors, please contact us. Due to limited resources, it is not possible to add sensors to the network openly, and we are doing so with sensors from colleagues and friends whom we thank for their time and resources. Regards, Rodolfo. [1] https://www.sciencedirect.com/science/article/pii/S138912862400402X [2] https://drive.google.com/file/d/1VGJ4PEcf-kHtFVT7rsXd9QYDqRL6rGH6/view?usp=… -- Rodolfo García Peñas (kix) http://www.kix.es/ "I asked him once how to change the key bindings and Dave said 'You use the Change Configuration command. On Unix it is abbreviated as cc.' Dave Conroy and Lawrence Stewart. On Friday, November 15th, 2024 at 14:18, Marcos Sanz via opensource-wg <opensource-wg(a)ripe.net> wrote: > FYI. Sorry for the cross-posting. > > > -----Mensaje original----- > > De: Alastair Strachan projectsfund(a)ripe.net > > Enviado el: jueves, 14 de noviembre de 2024 12:55 > > Para: ripe-list(a)ripe.net > > Asunto: [ripe-list] Update on the Community Projects Fund 2024 > > > > Dear all, > > > > After the announcement of this year’s Community Projects Fund recipients, > > some challenges emerged with the RIPE Atlas distributed network telescope > > project which would have prevented the project from achieving the goals > > outlined in the project plan. > > > > After careful consideration, the Selection Committee made the difficult > > decision to withdraw funding for the project. While we understand this is > > really disappointing for the recipients, we sincerely hope they will continue > > initiatives that bring value to our community and the Internet. > > > > The Selection Committee has now chosen another project to support from our > > pool of finalists: OpenPenny - An open-source tool to identify non-spoofed > > traffic. You can read about the project on the Community Projects Fund 2024 > > page: > > https://www.ripe.net/community/community-initiatives/cpf/previous- > > funding-recipients/funding-recipients-2024/ > > <https://www.ripe.net/community/community-initiatives/cpf/previous- > > funding-recipients/funding-recipients-2024/> > > > > Warm regards, > > Alastair Strachan > > Community Projects Fund Coordinator > > ----- > To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/opensource-wg.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/

2 1

RIPE Atlas Community Project Update
by Michael J. Oghia 15 Nov '24

15 Nov '24

Hi all, See the message below from Alastair from NCC. Does anyone know if the project can re-apply for the next round of funding? Kind regards, -Michael ---------- Forwarded message --------- From: Alastair Strachan <projectsfund(a)ripe.net> Date: Fri, Nov 15, 2024 at 8:48 AM Subject: [ripe-list] Update on the Community Projects Fund 2024 To: <ripe-list(a)ripe.net> Dear all, After the announcement of this year’s Community Projects Fund recipients, some challenges emerged with the RIPE Atlas distributed network telescope project which would have prevented the project from achieving the goals outlined in the project plan. After careful consideration, the Selection Committee made the difficult decision to withdraw funding for the project. While we understand this is really disappointing for the recipients, we sincerely hope they will continue initiatives that bring value to our community and the Internet. The Selection Committee has now chosen another project to support from our pool of finalists: OpenPenny - An open-source tool to identify non-spoofed traffic. You can read about the project on the Community Projects Fund 2024 page: https://www.ripe.net/community/community-initiatives/cpf/previous-funding-r… Warm regards, Alastair Strachan Community Projects Fund Coordinator

2 2

Probe registration problem
by Robert Kisteleki 13 Nov '24

13 Nov '24

Hello, I just put up a status page entry to https://status.ripe.net/ as follows: We're experiencing a problem with accepting new and reconnecting probes in the infrastructure. Probe that are currently connected, as well as new and ongoing measurements and data delivery are not affected. Regards, Robert

1 1

Probe disconnected, will not register. Registration servers down?
by Ernst J. Oud 13 Nov '24

13 Nov '24

My software probe 1009171 disconnected yesterday, precisely when my WAN IP address changed. Since then it tries to register but fails. So I restored it from a backup with the same result. What it tries to do, over and over again already for 9 hours, is: —- /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 1731484426 REG_WAIT_UNTIL expired go re-reg 1731484366 now 1731484426 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(a)reg04.atlas.ripe.net INIT reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1731484557 condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists —- The address it uses for the ssh session to the registration server cycles between the 2 IPv4 and 2 IPv6 addresses shown on the REGHOSTS line above. Is this a problem on my end or are the registration servers down? Regards, Ernst J. Oud

4 4

probes getting free "stress test" by postal system
by Sulev-Madis Silber 13 Nov '24

13 Nov '24

i think we need more fun here. actually it's serious too i received my v1/v2 in post in just envelope with corner open my v3 came from our vesna herself (by hands) now, v5, came in huge box with just paper sheet and probe in it. the one corner was smashed in. and poor device had been flapping around, naked, in that box, so, that introduction leaflet developed several holes in it from sharp corners of probe enclosure sure, it's free, hence maybe it's unfair but maybe they need more love. unsure who even packs them. i would guess there could be *some* padding available to stuff there? from yt comments on probe introduction video i learned that they sometimes are questionable quality too. mass produced cheap? mine survived all this abuse and i attributed the flimsily glued box to what i learned from elsewhere, that it's a budget stuff but unsure what to think...

2 1

Anomaly in NTP measurement data
by ripe＠nurfuerspam.de 13 Nov '24

13 Nov '24

Hi, In the data to date of an NTP measurement (#80845985), I find a single strange outlier with respect to the RTT value calculated: { "fw": 5090, "mver": "2.6.4", "lts": 281, "dst_name": "time2.cloud.tencent.com", "ttr": 0.413039, "dst_addr": "119.28.229.79", "src_addr": "45.11.104.146", "proto": "UDP", "af": 4, "li": "no", "version": 4, "mode": "server", "stratum": 2, "poll": 8, "precision": 1.19209E-7, "root-delay": 0.0000915527, "root-dispersion": 0.0249329, "ref-id": "647a24c4", "ref-ts": 3939345482.4404373, "result": [ { "origin-ts": 3939346062.989854, "receive-ts": 3939346062.999974, "transmit-ts": 3939346063.0000167, "final-ts": 3939346062.995442, "rtt": 4294967296.005545, "offset": -0.007347 } ], "msm_id": 80845985, "prb_id": 7030, "timestamp": 1730357262, "msm_name": "Ntp", "from": "45.11.104.146", "type": "ntp", "group_id": 80845985, "stored_timestamp": 1730357293 }, When I do the math by hand, the "rtt" value I get is 0.0055453, nicely matching the fractional part found in the measurement data. Does anyone have an explanation as to where the weird integer part might come from? Some overflow/underflow or other issue with decimal math on a binary machine? (I am not sufficiently versed in computer science to fully understand that topic, just that there are challenges in that area.) Thanks! Kind regards, R.

2 1

request for RIPE Atlas credits
by 权晓文 30 Oct '24

30 Oct '24

Hello! I'm a PhD student at Tsinghua University in China. I'm currently involved in a measurement research project, which undertakes large - scale measurements similar to Ping and Tracert by means of RIPE Atlas. As a new user, I have no credits for further progress. Therefore, I'm asking for help. I would be very grateful if someone could provide me with some RIPE Atlas credits. Thank you so much.

5 8

Fwd: RIPE Atlas Virtual Anchor Registration for DCS1 (sg-sin-as37989)
by Sanjeev Gupta 30 Oct '24

30 Oct '24

Good morning, https://atlas.ripe.net/probes/7247 I had setup an anchor last year, on a VM. I realised today while cleaning up my Atlas account, that the anchor was shown as "Down". From what I can figure out, the VM was unregistered/deleted 6 months ago. Should I apply for a new Anchor, or can I re-install and re-register (I assume the ISO will be Atlas-specific). Regards -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane ---------- Forwarded message --------- From: RIPE Atlas <no-reply(a)ripe.net> Date: Thu, 27 Jul 2023 at 22:22 Subject: RIPE Atlas Virtual Anchor Registration for DCS1 (sg-sin-as37989) To: Sanjeev Gupta <ghane0(a)gmail.com> Dear Sanjeev Gupta, Thank you for registering the technical information for your RIPE Atlas virtual anchor! Your FQDN is: sg-sin-as37989.anchors.atlas.ripe.net You will need now to setup the Virtual Machine according to these instructions: (https://atlas.ripe.net/docs/anchor-installation-vm/) It is important that once you have setup the virtual machine, you log in to your RIPE Atlas account, go to the "My Atlas" menu and then "Anchors", and check the boxes “Software is installed” and "Anchor is connected to the network" so we are notified and can begin the tests. Please note that your anchor will not be fully activated until we have finished these internal tests. We will notify you once we have finished testing and your virtual anchor is ready to use. If you have any questions, please do not hesitate to contact us at atlas(a)ripe.net You registered the following details: IPv4 address: 203.123.48.20 IPv4 ASN: 37989 IPv6 address: 2405:fc00::20 IPv6 ASN: 37989 Kind regards, RIPE Atlas Team

1 0

The MAT session is about to start
by Massimo Candela 29 Oct '24

29 Oct '24

A reminder that the Measurement, Analysis and Tools (MAT) session of RIPE89 is about to start in the main room at RIPE89! Streaming: https://ripe89.ripe.net/live/main/ Agenda: https://ripe89.ripe.net/programme/meeting-plan/mat-wg/ Ciao, Massimo On 17/10/2024 23:48, Massimo Candela wrote: > Dear all, > > > The MAT working group session will take place on Tuesday 29 October at > 16:00 CET. > > This is the agenda: > > 16:00 - 16:05 - Welcome - Chairs > 16:05 - 16:20 - Measuring and Visualizing DNS Watersheds - Jim Cowie > 16:20 - 16:30 - A First Look at User-Installed Residential Proxies From > a Network Operator's Perspective - Etienne Khan > 16:30 - 16:45 - IoT bricks over v6 - Tianrui Hu > 16:45 - 17:00 - Target Acquired? Evaluating Target Generation Algorithms > for IPv6 - Lion Steger > 17:00 - 17:15 - What’s in the Dataset? Unboxing the APNIC User > Populations - Vasilis Giotsas > 17:15 - 17:25 - RPKI flutter - Emile Aben > 17:25 - 17:30 - Closing Remarks - Chairs > > > If you are not already registered: https://ripe89.ripe.net/attend/register/ > > See you in Prague! > > Ciao, > Massimo (for the MAT WG chairs) > ----- > To unsubscribe from this mailing list or change your subscription > options, please visit: https://mailman.ripe.net/mailman3/lists/mat- > wg.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/

1 0

Request for Atlas Credits
by Felix Hoffmann 29 Oct '24

29 Oct '24

Hello All, I am Felix, a Master student at the University of Potsdam (Hasso-Plattner-Institut). I am working on a measurement research project that requires longitudinal data to validate censorship (at least that is what I want to try). For that, I would like to perform measurements like Ping, DNS, and HTTP. As it's just the start of the project, I can not yet estimate how many credits I need. For the beginning, it would be great to get some and then go from there. Therefore, I am reaching out for help. I would appreciate it if some of you could offer me some RIPE Atlas credits. My account at RIPE NCC is on this email: felix.hoffmann(a)student.hpi.uni-potsdam.de Best, Felix Hoffmann

11 15

Re: Request for Atlas Credits
by Ziad Attia 29 Oct '24

29 Oct '24

Hi Felix, 30 million credits have been sent. Best of luck with your project. Kindest regards Ziad On Oct 29, 2024 11:22, Felix Hoffmann <felix.hoffmann(a)student.hpi.uni-potsdam.de> wrote: Hello All, I am Felix, a Master student at the University of Potsdam (Hasso-Plattner-Institut). I am working on a measurement research project that requires longitudinal data to validate censorship (at least that is what I want to try). For that, I would like to perform measurements like Ping, DNS, and HTTP. As it's just the start of the project, I can not yet estimate how many credits I need. For the beginning, it would be great to get some and then go from there. Therefore, I am reaching out for help. I would appreciate it if some of you could offer me some RIPE Atlas credits. My account at RIPE NCC is on this email: felix.hoffmann(a)student.hpi.uni-potsdam.de<mailto:felix.hoffmann@student.hpi.uni-potsdam.de> Best, Felix Hoffmann

1 0

Re-activated SW probe: How to get rid of red banner?
by ripe＠nurfuerspam.de 27 Oct '24

27 Oct '24

Hi I successfully reactivated and reconnected my software probe #1005585 that I had officially written off a few weeks ago. Now, how do I get rid of the red banner at the top of the probe management page reading "Note: this probe is most likely not operational, and as such it has been written off [...]"? Thanks! Kind regards, R.

1 0