- ripe-atlas - mailman.ripe.net

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