- ripe-atlas - mailman.ripe.net

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

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