- ripe-atlas - mailman.ripe.net

Call for presentation LACNIC’s Internet Measurements WG
by Elisa 08 Mar '24

08 Mar '24

Hi all, I would like to use this mailing list to send a quick reminder about this initiative that is seeking presentations on Internet Measurements (including, but not limited to, Atlas). The Internet Measurements Working Group (IMWG) at LACNIC41 (10 May). Seeking remote/in-person presentations. Submission deadline 12 April. Instructions: https://listas.nog.lat/archives/list/imwg@listas.nog.lat/thread/KEOIK7VC7GQ… Kind regards, Elisa R&D - LACNIC

1 0

Tomhais STARTTLS: Cad a tharla?
by Niall O'Reilly 06 Mar '24

06 Mar '24

Back in December 2022, there was a proposal to support STARTTLS measurements. (https://www.ripe.net/ripe/mail/archives/ripe-atlas/2022-December/005234.html) I wonder, whether this proposal was implemented ? I've just tried using the measurement definition form (https://atlas.ripe.net/measurements/form/), where the only TLS-related option seems to need the target to be ready to receive a client hello. /Niall

2 1

IP & MAC
by Randy Bush 05 Mar '24

05 Mar '24

i have a remote probe. on the web gui, how can i see what its lan address (it is behind a soho nat) and mac are? i thought i knew how to do this, but the moon must be in klutz. thanks. randy

3 3

Retiring old ("legacy") UI pages and deprecated API calls
by Robert Kisteleki 05 Feb '24

05 Feb '24

Dear all, As part of the RIPE Atlas user interface renewal last year, we released a new measurement scheduling form and new probe and measurement lists. Since these changes the old pages were still accessible via changed URLs. By now the use of these pages all but disappeared, and we'll remove these from the UI in the coming weeks. On a similar note, we'll also remove support for the API calls that took the form /api/v2/measurements/<TYPE>/ [*]. These have been deprecated for a long time, and since the last active user moved way most queries ending up here either come from the legacy pages or from hacking attempts. [*] in fact this has effectively been an alias for /api/v2/measurements/?type=<TYPE> so no functionality is lost and it is trivial to change code that otherwise used these calls Please reach out to us if you believe the legacy pages provided some functionality you think you'll miss so we can help you. Regards, Robert

1 1

4 probes on different networks suddenly down?
by Ernst J. Oud 30 Jan '24

30 Jan '24

Hi, At noon today 4 of my probes disconnected. 1005229 61071 55795 1005072 These are on different ISP’s and one of these is in Oracle’s cloud. So this is not a problem on my side. Restarted the 61071 since that one is nearby and easily restarted since it is a hardware probe, but that does not work. Flashing red LED. What is going on? Regards, Ernst J. Oud

3 5

Atlas weather report: bad day
by Stephane Bortzmeyer 25 Jan '24

25 Jan '24

As reported by <https://atlas.ripe.net/>, indeed, measurements timeout today.

1 0

destination_ip_responded field in traceroute measurements
by Malte Tashiro 24 Jan '24

24 Jan '24

Hi, to my delight I discovered that there is now a "destination_ip_responded" field contained in traceroute measurement results. I often want to know this and had to handle it myself until now so I'm very happy that this seems to be a built-in field now. I only wonder if this is a feature to stay (since it's not in the documentation yet), and if it is server side, i.e., always available independent of the probe firmware? Best, Malte

2 3

built-in measurement id 12023
by Xiao Song 23 Jan '24

23 Jan '24

Hi all, Hope this email finds you well. The document says that this built-in measurement #12023 requires all available probes to send http requests to the target every 900s, but actually it seems like all probes send requests once a day. I was wondering if there exists inconsistency between the document and the actual measurements? Any suggestions would be appreciated. Thank you! Best, Xiao

2 1

mesures prices
by POULET Benoit 19 Jan '24

19 Jan '24

Hello, we tried to build some monitoring with the Atlas ripe network but we were blocked because of the measure's prices. Our goal is to ping an IP address every 5 minutes, with 3 packets from 3 countries in EU. The UI of Atlas give theses cost : ######################################### One-off mesure : Costs PER PROBE 6 credits for each result of a single probe 6 credits per day per probe FOR ALL PROBES 18 credits for 3 probes in total ######################################### 5 min interval mesure : Costs PER PROBE 3 credits for each result of a single probe 864 credits per day per probe FOR ALL PROBES 2592 credits for 3 probes in total per day ######################################### We have 3 Atlas probes, connected 24/24, 7/7, theses probes provide us 34 944 credits / day. With theses credits we do : * 6 One-off mesures, done every 5 mins * 13 Regular mesures, 5 min interval We were surprised at how few measures we could afford we 3 Atlas probes. Are we missing something ? Perhaps we are miss understanding what is Atlas for. Regards.

1 0

Fwd: Your credits are decreasing dramatically!
by Lukas Tribus 12 Jan '24

12 Jan '24

Hello, the "Your credits are decreasing dramatically!" emails have always been a mystery to me. I always get them a few days after a "troubleshooting session" with a number of one-off measurements. Here's the latest one; on January 6th, between 14:00 and 16:00 UTC I made a number of one-off Atlas measurements. The youngest (latest) Requested Stop Time which matches Systems Stop Time is: 2024-01-06T14:35:02Z I did not request any other measurements, and I have no "continuous" measurements running currently. And yet, on January 10th 00:48 UTC I get an warning: > Our records show that you've consumed 40500 RIPE Atlas credits in the last 48 hours, or approximately 14.06 credits/minute. On January 11th, 01:56 UTC I get the same exact warning again: > Our records show that you've consumed 40500 RIPE Atlas credits in the last 48 hours, or approximately 14.06 credits/minute. The data in those emails is just wrong, I did not use any credits for at least 72 hours (first email) and at least 96 hours (second email). It looks like already stopped one-off measurements are used for predictions not only of the future but for the past 48 hours as well? This is not a first, I got many of those erroneous messages in the past. Thanks, Lukas ---------- Forwarded message --------- From: RIPE Atlas <no-reply(a)ripe.net> Date: Thu, 11 Jan 2024 at 02:56 Subject: Your credits are decreasing dramatically! To: Lukas Tribus <lukas(a)ltri.eu> Dear RIPE Atlas probe host, Our records show that you've consumed 40500 RIPE Atlas credits in the last 48 hours, or approximately 14.06 credits/minute. We're pleased that you find the user-defined measurements useful and encourage you to keep conducting them! However, we'd like to give you a heads up that you have 2d 16h 6m before you will run out of credits at this rate. We recommend you stop some of your current measurements before this happens. If you do run out of credits, we will have to automatically stop running some of your measurements so that you do not reach a negative balance. If you would like to continue running a large number of user-defined measurements, you might want to consider applying for another probe or sponsoring a block of probes in order to earn more credits. Learn more about sponsoring probes at https://atlas.ripe.net/get-involved/become-a-sponsor/ Thank you for participating in RIPE Atlas! Kind regards, RIPE Atlas Team

3 3