[atlas]Re: API Not Working

Hi, I'm not aware of issues recently, data is generally flowing as expected. It's hard to judge why you may have problems without knowing the details, but from your description it could be that the probes you selected were unavailable, or it took them longer than what you expected to do the

[atlas]Re: results page empty

Hello, The page itself works (tried Firefox and Chrome) - I'm not sure why it would not work in Edge or Pale Moon - maybe some extensions/blockers are in the way? Regards, Robert On Tue, Jul 16, 2024 at 8:16 AM Marco Moock wrote: > > Hello! > >

[atlas]Re: Can not target google.com with periodic measurement

Hi, I understand your point and recognise this is inconvenient at the moment. I'd say in the short term we can increase the limit - 25 is just a number like any other :-) - and perhaps administratively close the failing measurements. While I can't make promises about when, but in the longer term

[atlas]Re: Can not target google.com with periodic measurement

Hi, Indeed, this is a global maximum against each target. We have two major reasons for this: * some targets can stand "any amount" of measuring, but most can't / shouldn't have to * once there are $thismany measurements against a particular target, there's a good chance the new ones are

Re: [atlas] Bug reports about Atlas

Hi Stephane, Our 1st line support handles most of the issues/reports we receive, and this is really helpful. Mistakes and misunderstandings can happen of course. Please let me/us know what ticket of yours you have the comment about, and we'll look at how we can improve our responses. Cheers,

Re: [atlas] [HTTP measurements] Units of timing?

Hello again, According to the documentation (https://atlas.ripe.net/docs/apis/result-format/#version-5000) those fields are in milliseconds. I believe this to be correct; your referenced measurement uses resolve-on-probe: false, therefore the DNS resolution is done at specification time and it's

Re: [atlas] [HTTP measurements] What is the use of query_string?

Hello, On Tue, Jun 25, 2024 at 2:04 PM Stephane Bortzmeyer wrote: > > On Tue, Jun 25, 2024 at 11:32:50AM +0200, > Stephane Bortzmeyer wrote > a message of 10 lines which said: > > > The documentation says that you can add a "query_string" parameter in > > a HTTP measurement but the anchor

Re: [atlas] multiple probes down since Jun 24th?

Hello, Indeed we are experiencing some trouble with one of our controllers. This can affect probes and anchors, seemingly up to 10% of the probe population. The team is investigating the issue. Regards, Robert On Tue, Jun 25, 2024 at 8:36 AM Andreas S. Kerber via ripe-atlas wrote: > > Hi, > >

Re: [atlas] repetitive 2fa authentication on every login

Hello, Thank you for this note, we'll take a look at the possible options. Regards, Robert On Wed, Jun 12, 2024 at 3:50 PM wrote: > > Hi team, > https://atlas.ripe.net/probes/mine requires new login upon every browser > open. It even requires 2FA every time. Is it possible to keep the session

[atlas] RIPE Atlas infrastructure maintenance on 11 June 2024

collected and stored. We apologise for the inconvenience this may cause. Regards, Robert Kisteleki, for the RIPE Atlas team -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] How long is a year?

Hello, That calculation is simple: sum_of_connected_time / (now() - first_connection_time) Does this help answering your question? Regards, Robert On Wed, Jun 5, 2024 at 9:28 PM Edward Lewis wrote: > > On my probe’s status page, there is an “All Time” “Time Connected” of 8y 343d > 15h 30m.

[atlas] Summary of the discussions about previous proposals

we’ll only store them for a limited time). All in all, for the time being we do not plan to make behavioural changes about this feature. Regards, Robert Kisteleki RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Meaning and the future of the project

be helpful for this process. Regards, Robert Kisteleki On Tue, Feb 6, 2024 at 12:45 AM Petr Kutalek via ripe-atlas < ripe-atlas@ripe.net> wrote: > Hello, > > I have been involved in this project for over 12 years. For the last few > weeks I have been wondering what the point of >

Re: [atlas] Possible software probe "farming" on AS47583

n Cartwright-Cox > wrote: > > > > Those limits seem reasonable enough, > > > > My own intuition would suggest values of: > > > > X=2 > > Y=3 > > Z=5 > > > > But otherwise, I welcome such a change being implemented! > > > >

[atlas] Operational work on RIPE Atlas

Dear all, A heads-up: we are just about to start scheduled maintenance work on RIPE Atlas. During the maintenance we expect scheduling of new measurements will be delayed and searching for measurements will not yield up-to-date information. Regards, Robert -- ripe-atlas mailing list

Re: [atlas] Confused by the documentation

Hi, You can find this in the documentation at: https://atlas.ripe.net/docs/howtos/anchors.html#http-s Cheers, Robert On Fri, Apr 5, 2024 at 4:33 PM Stephane Bortzmeyer wrote: > > On Fri, Apr 05, 2024 at 10:13:14AM +0200, > Christopher Amin wrote > a message of 44 lines which said: > > > As

Re: [atlas] Empty responses for HTTP tests with a non-existing path?

Dear Stephane, Thank you for pointing this out, it has been fixed: the anchors respond with a proper 404 now. Regards, Robert, reporting for the people who fixed it On Thu, Apr 4, 2024 at 6:48 PM Stephane Bortzmeyer wrote: > > It seems the anchors, when receiving a HTTP request for a

[atlas] Fwd: [ncc-announce] [News] 2FA Mandatory on RIPE NCC Access accounts

on your account. Regards, Robert Kisteleki RIPE NCC Forwarded Message Subject: [ncc-announce] [News] 2FA Mandatory on RIPE NCC Access accounts Date: Tue, 26 Mar 2024 12:12:12 +0100 From: Felipe Victolla Silveira To: ncc-annou...@ripe.net Dear colleagues, This week, two-factor

Re: [atlas] Possible software probe "farming" on AS47583

Is there an immediate way to report these probes other than this mailing list? I don't know of one and so I'm here :) Dear Ben and others, Each new, connected RIPE Atlas probe provides incremental value to the system and its users, but this value decreases with similarity to existing

Re: [atlas] Possible software probe "farming" on AS47583

Hello, On 2024-02-05 16:11, Ben Cartwright-Cox via ripe-atlas wrote: Hi everybody, While doing some measurement work earlier this weekend I discovered that there are a large amount of probes on AS47583 that look like they are being set up to farm credits. With a suspiciously high amount of

Re: [atlas] Retiring old ("legacy") UI pages and deprecated API calls

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

Re: [atlas] 4 probes on different networks suddenly down?

Status update: we identified and fixed the underlying issue, and are recovering now. Normal status, including processing backlogs will likely take some time. We'll post updates on the RIPE NCC status page: https://status.ripe.net/ Regards, Robert On 2024-01-30 14:44, Robert Kisteleki wrote

Re: [atlas] 4 probes on different networks suddenly down?

Hello, Quick note: we are experiencing issues with the controlling infrastructure, trying to determine the root cause. Please stand by. Cheers, Robert On 2024-01-30 14:23, Ernst J. Oud wrote: Hi, At noon today 4 of my probes disconnected. 1005229 61071 55795 1005072 These are on

[atlas] Retiring old ("legacy") UI pages and deprecated API calls

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

Re: [atlas] built-in measurement id 12023

Dear Xiao, You are absolutely right - the documentation (and the API metadata) incorrectly states 900 seconds, in reality it is once a day. Also for measurement 13023 over IPv6. (It would be possible to adjust reality to match the docs instead and adjust this measurement's frequency to 900

Re: [atlas] Fwd: Your credits are decreasing dramatically!

Hi Lukas, The intention of this mail is to warn you in case the system has reasons to believe that you'll run out of credits "soon". A burst of one-off measurements changes the credit consumption rate temporarily, so it kind of makes sense that you see correlation between when you get these

Re: [atlas] auto probe renewal

Hello, Left unattended, over longer periods of time, measurements lose probes. The RIPE Atlas API includes a call that can be used to add or remove probes or groups of probes in an existing measurement, see:

[atlas] The role of aggregators in RIPE Atlas

m, or live at RIPE87. Regards, Robert Kisteleki RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] RIPE NCC measurement data retention

to see discussions about this here on the mailing list, on the RIPE NCC Forum, or live at RIPE87. Regards, Robert Kisteleki RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] decommission of virtual probes

Hello, If you resurrect / reinstall / relocate a probe and you expect to have different network conditions in its new life, then it is better to install it as a new one. If however you are just changing the hardware or just need to replace it's key, then it's better to reuse the ID (the host

Re: [atlas] HE "Supertraceroute" exposes ATLAS traceroute functionality to the public

Hi, Yes, we are aware and we're following up with them. Regards, Robert On 2023-10-19 12:04, Lukas Tribus wrote: Hello, FYI HE's new "supertraceroute" exposes ATLAS traceroute functionality to the public: https://bgp.he.net/traceroute/ Other sources are (NLNOG) RING nodes and other

Re: [atlas] NTP empty results ('result': [{'x': '*'}])

Hi, This means there probe didn't get a useful answer; there was a timeout, the connection failed or similar reasons. Regards, Robert On 2023-10-10 12:41, Giovane C. M. Moura via ripe-atlas wrote: Hi folks, I am getting some NTP results in the following format:   'result': [{'x': '*'}],

Re: [atlas] Changes to RIPE Atlas API keys

Dear all, These changes have now been implemented. Regards, Robert On 2023-09-19 12:11, Robert Kisteleki wrote: 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

[atlas] RIPE Atlas Quarterly Planning Q4 2023

the big data backend. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki Principal Engineer RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Will probes catch up?

On 2023-09-21 12:07, Ernst J. Oud wrote: 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

Re: [atlas] Atlas fully down..

Hi, On 2023-09-20 11:47, Ernst J. Oud wrote: Robert et al, In contrast to your statement below, streaming of results from new or existing measurements using Magellan currently does *not* work… no results are obtained, see below. —- Looking good! Measurement 60182213 was created and

Re: [atlas] Atlas fully down..

Hi, On 2023-09-20 11:56, Stephane Bortzmeyer wrote: On Wed, Sep 20, 2023 at 07:43:20AM +0200, Robert Kisteleki wrote a message of 42 lines which said: All else (continuing to run existing measurements, creating new ones, real-time streaming of the results, APIs, UI, ...) are running

Re: [atlas] One-off measurements stopped after 5-6 minutes without results

Hello, As you've probably seen in the other thread, we have a problem in storing/processing new results. We're working on fixing this. I wrote "all else is working fine" there - which I have to correct now: the above error affects the probe tagging, where because of the lack of "good data"

Re: [atlas] Atlas fully down..

On 2023-09-19 23:04, Ernst J. Oud wrote: 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 Good morning, I'm sad to report that indeed

[atlas] Changes to RIPE Atlas API keys

out 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@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Issues with Atlas back-end

Hi, The issues with RIPEstat have been resolved in about an hour, the problem with the Atlas data backend is unfortunately still ongoing. Regards, Robert On 2023-09-19 00:03, Ernst J. Oud wrote: Hi, From September 18th there is an issue with the Atlas back-end, already 9 hours delay.

Re: [atlas] Built-ins tab in Atlas web interface does not respond

On 2023-09-08 18:21, Ernst J. Oud wrote: It appears to work again. Thanks! Yes, we deployed a fix sometime in the afternoon. And it looks better than before, or am I hallucinating here? AFAIK there were no real changes, maybe some tweaks. Regards, Robert Regards, Ernst -- ripe-atlas

Re: [atlas] Questions with regard to the measurement status and running time

Jerome, My questions are: 1. Why is the measurement "ongoing" even if the results have already been made available? One-off measurements are automatically marked "stopped" after 15 minutes by the system. This is mostly a book-keeping exercise to know what is active and what is not; it does

Re: [atlas] What is the trick with "+Reuse a set from a measurement" ?????

Hello, The UI at the moment does not offer a lookup based on measurement ID for this feature; mostly because in the end one would submit the same ID back to the API, so this is not perceived to be a critical feature. Lookups based on measurement descriptions (the intended use case) work as

Re: [atlas] Built-ins tab in Atlas web interface does not respond

On 2023-09-07 09:53, Ernst J. Oud wrote: 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 Hi, Thank you for reporting, indeed something is not right there. We are looking into it.

Re: [atlas] Probe with ever changing upstreams/ASs?

Hi Carsten, Anyhow: as part of this tunnel setup, the other end of the tunnel changes every 24 to 48 hours - and so does the upstream and therefore also the AS of the upstream provider. I think the short answer is: probably not highly useful. But of course it depends :-) Each result is

Re: [atlas] Easy way to view DNS results?

Hello, We're not parsing and inserting all the bits from the raw response into the JSON mostly because it would inflate the size of the results enormously, while users are generally only interested in specific bits. The UI gives the basics (success, RTT) to show the big picture but exposing

Re: [atlas] Issues downloading large result files

Hello, We've seen periods where someone was downloading 10-30GB result blobs (years' worth of results), multiple downloads in parallel, and while it stressed the service, it worked for the most part. This *could* work, but it's suboptimal. My advice would be to download in chunks (perhaps

Re: [atlas] Delays in backend…

I forgot to mention that the result stream (https://atlas-stream.ripe.net/) does not share fate with the data backend, it is delivering results as expected. Cheers, Robert On 2023-07-01 13:06, Robert Kisteleki wrote: Hello, I can confirm that the data storage backend has been struggling

Re: [atlas] Delays in backend…

Hello, I can confirm that the data storage backend has been struggling in the last couple of days. Our operations people are trying to come up with a permanent solution, but the problem keeps reappearing. The status page has entries about these issues - though admittedly not about all the

[atlas] RIPE Atlas Quarterly Planning Q3 2023

the big data backend. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] RIPE Atlas Quarterly Planning Q2 2023

on restructuring and renewing pages of the user interface. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo

Re: [atlas] Missing ping and traceroute dumps for 2023-01-23

Just an update on this: the issue has been solved in the meantime, the missing dumps have been backfilled. Regards, Robert On 2023-01-31 13:18, Robert Kisteleki wrote: On 2023-01-31 11:40, Maxime Mouchet wrote: Hi, I noticed that there is no ping and traceroute dumps for 2023-01-23

Re: [atlas] Rate limiting on the APIs

Update: we applied this change a few minutes ago. We'll keep observing the system for ill effects. Regards, Robert On 2023-01-30 14:57, Robert Kisteleki wrote: Dear all, We have seen in the past that even with the best intentions, every now and then some users are using excessive amounts

Re: [atlas] Missing ping and traceroute dumps for 2023-01-23

On 2023-01-31 11:40, Maxime Mouchet wrote: Hi, I noticed that there is no ping and traceroute dumps for 2023-01-23: https://data-store.ripe.net/datasets/atlas-daily-dumps/2023-01-23/ The other days are fine though. Ooops. We'll check! Is there any chance to get these dumps? Or are they

[atlas] Rate limiting on the APIs

Dear all, We have seen in the past that even with the best intentions, every now and then some users are using excessive amounts of requests to the RIPE Atlas APIs, in some cases resulting in degraded performance to all users. An example for the curious: some AWS account asking the probe API

Re: [atlas] Encouraging people to upgrade software probe versions

manage the software probe installation? Please consider to distribute a prebuild VM *additionally* to the existing ways and see what happens. I'm sure, most new users will choose a prebuild VM. BR, Simon On 19.01.23 12:48, Robert Kisteleki wrote: That is reasonable; the difference is t

Re: [atlas] Encouraging people to upgrade software probe versions

Hi, On 2023-01-29 20:11, Gert Doering wrote: Hi, On Fri, Jan 27, 2023 at 02:15:44AM +0100, Robert Scheck wrote: On Mon, 09 Jan 2023, Gert Doering wrote: So don't do OS updates. But *do* update the probe software, automatically, and in normal intervals. writing while wearing my hat as a

Re: [atlas] Atlas anchors as ping targets

The idea here is - I have a host in a "home network" that has 2 ISPs, with a global IPv6 address from each of them - one of the ISPs fails, but the host does not know, and keeps using the "broken" IPv6 source address - by cyclic measurements, Brian's tool will see "nah, that

Re: [atlas] Access to probes and documents

Hello, On 2023-01-29 11:08, Mccherry, Paul (Postgraduate Researcher) wrote: Althiough I am logged in when trying to access various probes I do not seem to have the rights, probes such as 91,353,365,3094…. Those probes are (except 3094) marked as private, so authentication is not enough. You

Re: [atlas] Atlas anchors as ping targets

Hi, On 2023-01-28 02:24, Brian E Carpenter wrote: TL;DR: Is it OK to use Atlas anchors as random ping targets? RIPE Atlas anchors are known and willing targets for measurements - so I'd say yes, definitely! Would it be OK to choose the probe target by picking an Atlas anchor at random?

Re: [atlas] Encouraging people to upgrade software probe versions

Hello, On 2023-01-09 10:52, Gert Doering wrote: Hi, On Mon, Jan 09, 2023 at 10:19:34AM +0100, Michel Stam wrote: The automatic update for the CentOS package was removed as of 5080. This means that the update to 5080 will still be automatic, but not any more after this (say 5090 onwards).

Re: [atlas] ripe-atlas Digest, Vol 137, Issue 8

Hello, On 2023-01-09 22:59, Geert Jan de Groot wrote: One question perhaps is if a probe running very obsoleted probe code, is useful or perhaps at some time probes older than version 1234 should not be used for pool measurements? For instance, release 2345 enables measurements on 240/12

Re: [atlas] Ability to traceroute to 240/4 - software vs. hardware probes

What could account for the difference in how hardware and software probes handle this task? I would have thought that the change from last November would make software probes willing to attempt these. I'd believe it's the combination of what versions these probe run (i.e.. is it at least

Re: [atlas] Positively meant critique …

Hi, On 2023-01-07 18:07, Ernst J. Oud wrote: LS. Is there a kind of common understanding what this mailing list is about? What its purpose is? This is the general discussion list for topics related to RIPE Atlas. I see important discussions such as those on private measurements but no

Re: [atlas] A number of built-ins stopped?

Hi, On 2022-12-23 18:25, Ernst J. Oud wrote: L.S. All the probes in NL that I had a look at, in a variety of different ASN’s, have no data available via the Atlas web of via the api (JSON, Magellan) for a.o. built-in measurement 1009 (ping to a.root-servers.net) and several others after

Re: [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]

Hi, The definition of a "small" test could be something like; - maximum 20 probes - runs for maximum 60 minutes - is repeated maximum 10 times   (if you run every 300sec you have to limit the endtime to 50 minutes) What would you propose the API to do if this rule is violated? Should it

[atlas] RIPE Atlas Quarterly Planning Q1 2023

to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki Research and Development Manager RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]

If you can count on one hand the number of users using >90% of the private measurements over a longer timeframe than two weeks, then I submit that the choice is clear. This information is somewhat harder to extract, but we'll try and get back to you! Cheers, Robert -- ripe-atlas mailing

[atlas] Probe status pages -- was: Re: Non-public probes?

On 2022-12-15 14:33, ripe@toppas.net wrote: Hi Chris, sorry for "stealing" this conversation, but it's interesting to hear that there will be a redesign of the probe page coming up soon. Can we have a discussion about that? There are several things, that bother me a bit... BR, Simon

[atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]

, Robert Kisteleki For the RIPE Atlas team -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] Proposal: Add support for STARTTLS measurements [STARTTLS]

, Robert Kisteleki For the RIPE Atlas team -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] Proposal: Generic HTTP measurements [GENERIC-HTTP]

, Robert Kisteleki For the RIPE Atlas team -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] Proposal: Measure well-known CDNs,[CDN-HTTP]

, Robert Kisteleki For the RIPE Atlas team -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] Proposal: remove per-hop “late” packets from traceroute [LATE-PACKETS]

, Robert Kisteleki For the RIPE Atlas team -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Atlas api down

On 2022-12-14 10:03, Alexander Burke via ripe-atlas wrote: Hi Robert, If the status page is manually updated, it should probably show a prominent note to that effect so that it is consumed well-salted. Hi, The event shows up in the "past incidents" section of the page. Is that what

Re: [atlas] Atlas api down

Hello, Our data storage backend experienced two separate issues during the night: one between around 18:30-20:15 (CET) and another one around 1:00-1:45 (CET) I am updating the status page now. Apologies for the issues, Robert On 2022-12-13 19:54, Ernst J. Oud wrote: Hi, As of around

Re: [atlas] atlas related mails come 4 times

Hi, We checked on our end, and it seems your server for some reason did not properly accept the mail from ours, so it was tried multiple times. Peter's answer is likely correct. Cheers, Robert On 2022-12-02 11:16, Endre Szabo wrote: Hi chaps, Just recently any mail from atlas monitoring

[atlas] Removing the "technical updates" RSS feed

e creation of the RSS feed into the new way of publishing the release news, but we would only consider this if there's a strong enough demand for it. So please let us know if you have reasons to insist on keeping the feed alive! Thank you, Robert Kisteleki RIPE Atlas -- ripe-atlas mailing

Re: [atlas] Issue to create measurement on the webpage

On 2022-12-07 00:14, Alexis MARCOU wrote: Hi All, I'm trying to create a measure on the website : https://atlas.ripe.net/measurements/form/ But, when I click on the "Ping", a query is sent, but the interface is not updated with the parameters

[atlas] Format change for index pages of RIS MRT data files and RIPE Atlas daily dataset dumps

at: https://ris.ripe.net/docs/20_raw_data_mrt.html#name-and-location Kind regards, Oleg Muravskiy, Robert Kisteleki RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Can't register software probe

Hi, This is strange as this should work (I just tried with a newly generated random key). Are you sure you're pasting the public part? ;-) Together with the prefix "ssh-rsa WHATEVERBITS"? If so, please send me the (again, public) key and I'll check what's wrong with it. Cheers, Robert

Re: [atlas] placing a probe into wireless networks (not terrestrial)

On 2022-10-28 10:04, Kurt Kayser wrote: I would be offering support to try to establish such a probe and help to setup a project defition. Any thoughts or feedback to this idea? In addition to what's already been said: it's useful for the whole community to increase the diversity of the

Re: [atlas] Shared probes not shown anymore in "my atlas"

On 2022-10-19 01:09, Dave wrote: Hi, In the past the probes that had shared management were shown below the owned probes. This is not the case anymore. Is this intentional? Can it be restored? Thanks, Dave Hi, I'll reach out to you for details privately. Cheers, Robert -- ripe-atlas

Re: [atlas] Tagging probes which are using the ISP's DNS server?

I believe it would be informative if we assembled some statistics about the current state, ie. how many probes would get what kind of tags if we applied them today. Perhaps Max already has some up his sleeve? Here's a quick-and-dirty answer to this: what the tags could look like if we

Re: [atlas] Revive an abandoned probe?

On 2022-10-06 21:11, Ernst J. Oud wrote: Hi, As a result of my experiments some three moments ago I have an abandoned probe (OpenWRT). If I power it again will it start working again or do I need te re-apply for a new probe? Regards, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud

Re: [atlas] Tagging probes which are using the ISP's DNS server?

Inside-AS DNS Outside-AS DNS RFC1918 DNS We probably need a "localhost DNS" too I would still argue that the "big" public resolvers warrant their own tags. Apart from that, should there be separate tags for RFC1918 and ULA? Paraphrasing a quote from may decades ago: "probe DNS tagging is

Re: [atlas] Tagging probes which are using the ISP's DNS server?

Hello, This seems to be an interesting question. We can certainly apply some (system) tags for probes that have the popular resolvers 8.8.8.8, 9.9.9.9 and so on in the resolver configuration. This would allow users like you to easily filter for, or filter out, probes that do this. One

Re: [atlas] V5 probes

On 2022-10-06 09:29, Daniel AJ Sokolov wrote: Out of curiosity: How many active V1 probes are still out there? How many were distributed? BR Daniel AJ The maximum number of v1 probes ever alive at the same time was about 1000 (in 2012). We made about 1500 of these. The maximum number of

Re: [atlas] V5 probes

On 2022-10-03 12:37, Simon Brandt via ripe-atlas wrote: Hi Robert, i noticed that v1 probes are stuck with Firmware Version 4790. Does that mean, they are missing crucial functionalities of the later firmwares? BR, Simon Indeed v1-v2 probes have not received new functionality since

Re: [atlas] V5 probes

lier probes, as long as those still work. Of course we're always interested in new locations/networks to cover, so feel free to propose that! :-) Regards, Robert Kisteleki for the RIPE Atlas team -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] RIPE Atlas Quarterly Planning Q4 2022

. Kind regards, Robert Kisteleki Research and Development Manager RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] RIPE Atlas Quarterly Planning Q3 2022

we should work on. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki Research and Development Manager RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/lis

Re: [atlas] DNS issues

Hi, There is a short description about how these tags are applied at https://atlas.ripe.net/docs/probe-tags/ "DNS resolution" section. Basically, the system looks at results of DNS measurements delivered by the probe and applies/removes tags based on how successful those were. I believe

Re: [atlas] RIPE Atlas down?

Hello, The data back-end behind RIPE Atlas, RIS and RIPEstat experienced issues yesterday evening; some of these are still affecting the data processing. In particular RIPE Atlas data is experiencing result delays since around 03:30 (CEST). The system is catching up now, but it hasn't

Re: [atlas] Looking for a hardware probe

Can the probe ambassador page be updated to display the probe version handed out next to each probe? Thanks, Hank Yes, that sounds useful and it's certainly something that we can do! Regards, Robert -- ripe-atlas mailing list ripe-atlas@ripe.net

Re: [atlas] RIPE-Atlas measurements showed "No recent report available"

real-time. The result streaming interface is not affected by this issue. We put out a status update to https://status.ripe.net/ which is admittedly new, not everyone is aware yet. We apologise for the inconvenience! Robert Kisteleki -- ripe-atlas mailing list ripe-atlas@ripe.net https://list

Re: [atlas] Overuse of software probes

Hello All, I think we can separate out two issues here: 1. I believe we should keep incentivising (for the lack of a better word) "benevolent" probe hosts - ie. if someone would like to host a probe, either hw or sw, then they should be able to do so and enjoy the benefits. Having said this,

[atlas] RIPE Atlas Quarterly Planning Q2 2022

. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki Research and Development Manager RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Location of probe controllers

Hello, On 2022-01-28 09:55, Malte Appel wrote: My guesses from the DNS names are based on IATA airport codes: ctr-ams02.atlas.ripe.net (Amsterdam, NL) ctr-ams03.atlas.ripe.net (Amsterdam, NL) ctr-ewr01.atlas.ripe.net (Newark, NJ, US) ctr-fnc01.atlas.ripe.net (Funchal, PT)

  1   2   3   >