September 2023 - ripe-atlas - mailman.ripe.net

Thanks!
by Ernst J. Oud 04 Jan '24

04 Jan '24

Hi, I know I was a bit harsh commenting about the degraded performance of Atlas the last couple of days. Therefore herewith also kudos now that the problems appears to be solved. I guess a number of people have worked hard on the issue. Appreciated! Ernst J. Oud

4 3

Questions with regard to the measurement status and running time
by Jerome Mao 20 Oct '23

20 Oct '23

Hi RIPE Atlas Team and Community, I would like to know more about the status of measurements - I have scheduled a one-off ping measurement which utilized 15 anchors. I polled the measurement status and results from my local desktop to the restful API through cousteau Python lib. The results were returned to me in less than a minute, but it took around 13 minutes for the measurement to transition from "ongoing" to "stopped." On the other side, the time delta between the "requested start time" and "requested stop time" on the RIPE Atlas portal is 9 minutes. My questions are: 1. Why is the measurement "ongoing" even if the results have already been made available? 2. What is the meaning of the "requested start time" and "requested stop time" on the RIPE Atlas portal? 3. Will a one-off measurement release one slot from the measurement rate limit once its result becomes available even if it’s still in "ongoing" state? Thanks! Best, Jerome

3 3

Changes to RIPE Atlas API keys
by Robert Kisteleki 04 Oct '23

04 Oct '23

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

1 1

Changes to RIPE Atlas API auth status codes on 2 Oct
by Chris Amin 02 Oct '23

02 Oct '23

Dear colleagues, Currently the RIPE Atlas REST API (https://atlas.ripe.net/api/v2/) returns a 403 Forbidden status code in two cases: * When a request requires authentication but the user has not provided any credentials, or has provided incorrect credentials * When a user has authenticated correctly, but they or their API key lacks the permissions needed for a particular request Distinguishing between these two cases is important because in the first case the client can potentially get access by authenticating, and in the second case there is no point in retrying authentication with the same credentials. In order to enable this distinction, and to generally conform to web standards and best practices, on Monday, 2nd October we will change the REST API so that a completely unauthenticated request will receive a response with a 401 Unauthorized status code. The 403 Forbidden status code will still be returned for users and API keys that are authenticated but lack the necessary permissions for the request. As a temporary migration measure, the API will keep the same behaviour (always return 403) if either: * The "Referer" header contains "RIPE Atlas Tools" and a version string <= 3.1.1, or * An "X-Compat" header is set and contains the string "auth-2022" This temporary measure is guaranteed to work for the rest of 2022, after which it will be removed and the API will always make the 401/403 distinction. Kind regards, Chris Amin RIPE Atlas team

2 4

Will probes catch up?
by Ernst J. Oud 21 Sep '23

21 Sep '23

Hi, Some of my probes, all on different providers, (for instance: https://atlas.ripe.net/probes/1005104/#tab-builtins) have not catched up after the recent disruption. Will this happen automatically? They are connected, streaming results are ok., so I guess I don’t need to restart them? Regards, Ernst J. Oud

2 1

Atlas fully down..
by Ernst J. Oud 20 Sep '23

20 Sep '23

Considering the fact that all of Atlas is completely down for more than 24 hrs., I find the silence a bit deafening. No status updates, nothing. Weird. Not up to RIPE standards. Regards, Ernst J. Oud

7 16

One-off measurements stopped after 5-6 minutes without results
by Gerdriaan Mulder 20 Sep '23

20 Sep '23

Hi list, A few hours ago (around 15:00Z), I launched some one-off measurements[1][2][3] on the platform for a select number of probes (based on ASN and region). The target in all three cases was 2a02:1807:1020:700::1 (no hostname, purely the address). Although the number of requested and participating probes varied a bit, it seems none of the measurements yielded any results. At the time I didn't look at recent posts on this mailing list, nor was I aware of this ongoing incident[4] on the Atlas backend. It seems like that incident might be the cause of the (current) unavailability of these results. It would be great if anyone can confirm that (viewing results of) user-defined measurements are affected as well. Aside, I suppose the following messages on "My RIPE Atlas Dashboard" are also caused by the mentioned incident[4]? --->8--- 2023-09-18 16:40 UTC Your probe #11nnn was automatically untagged as "system: Resolves AAAA Correctly" 2023-09-18 16:40 UTC Your probe #11nnn was automatically untagged as "system: Resolves A Correctly" 2023-09-18 16:20 UTC Your probe #11nnn was automatically untagged as "system: IPv6 Works" 2023-09-18 16:20 UTC Your probe #11nnn was automatically untagged as "system: IPv4 Works" ---8<--- Perhaps the incident page[4] can include a few lines of the current (estimated) impact, as well. Best regards, Gerdriaan Mulder [1] https://atlas.ripe.net/frames/measurements/60161706/ (default IPv6 traceroute) [2] https://atlas.ripe.net/frames/measurements/60162230/ (IPv6 traceroute, paris=0) [3] https://atlas.ripe.net/frames/measurements/60162753/ (default IPv6 ping) [4] https://status.ripe.net/incidents/wfd7qywz3v68

3 4

Issues with Atlas back-end
by Ernst J. Oud 19 Sep '23

19 Sep '23

Hi, From September 18th there is an issue with the Atlas back-end, already 9 hours delay. Built-ins show data until around 14:00 UTC. It is now midnight. I am confused, the status page (https://status.ripe.net/) at the bottom says: “Resolved - The backend team could restore the service level and with that issues in RIPEstat stopped as well. Sep 18, 15:11 UTC” It clearly is not resolved. On the top of that status page it says: “Investigating - We are experiencing issues with the RIPE Atlas backend and currently are investigating this issue. Sep 18, 2023 - 14:07 UTC” So what is the status? Regards, Ernst J. Oud

2 1

New Atlas Measurement Creation Form (BETA)
by Stephen Suess 18 Sep '23

18 Sep '23

Hello Atlas fans, As part of our ongoing User Interface renewal activity we've been working on a redesign of the measurement creation form. Today, we're excited to announce the release of this new form in beta, and we would love your feedback and suggestions as we continue to develop it. Notable improvements include: - A simplified and cleaner user interface. - Client-side functionality, eliminating the need for external libraries, websites, or APIs (except for cost calculations and final submit). - Enhanced performance. - Mobile-friendly design. - Clearer probe selection information. - Presentation of API specification with and without the cURL command. You can find the new form at https://atlas.ripe.net/mform or in the menu under "Measurements -> Create Measurement (BETA)". Your input and feedback is highly appreciated, you can reply to this message or directly to me or in the forum at https://forum.ripe.net/t/new-measurement-form-beta/678 Thanks! Stephen RIPE Atlas UI

1 0

Built-ins tab in Atlas web interface does not respond
by Ernst J. Oud 11 Sep '23

11 Sep '23

Hi, In the web interface clicking the tab “Built-ins” does not work, it shows “loading” and nothing happens. Tried different browsers. Regards, Ernst J. Oud

2 3