Meta-information dumps for built-in measurements?
Is there any repository like https://ftp.ripe.net/ripe/atlas/measurements/ that contains meta-information about built-in RIPE Atlas measurements (the above repository contains meta-information only for public measurements)? I couldn't find anything similar in the new FTP repository at https://data-store.ripe.net/datasets/atlas-daily-dumps/ I guess using the API is an alternative but it would be more convenient to have such dumps Thanks, Vasileios
On 2018-09-04 03:16, Vasileios Giotsas wrote:
Is there any repository like https://ftp.ripe.net/ripe/atlas/measurements/ that contains meta-information about built-in RIPE Atlas measurements (the above repository contains meta-information only for public measurements)?
I couldn't find anything similar in the new FTP repository at https://data-store.ripe.net/datasets/atlas-daily-dumps/
I guess using the API is an alternative but it would be more convenient to have such dumps
Thanks, Vasileios
Hello, https://atlas.ripe.net/api/v2/measurements/?id__lte=1000000 is a pretty good approximation of what you're after. Built-ins change very rarely, so a one-time query will give you virtually everything about built-ins. Note that the above mentioned full dump of measurement metadata via FTP is not sustainable (in its current form it's growing endlessly) so we'll highly likely to change this in the near future. Regards, Robert
Thanks Robert, With that opportunity just some feedback on the API: it's generally very convenient, my only issue is that for repeated measurements (not one-off) it's not easy to get the queries that have been executed in a certain time frame. You have to parse the results from the start of the measurement and get those executed between the desired time frame by checking its result separately, which is slow (at least I haven't found a better way!) So having some sort of metadata dumps makes it faster to go through the queries that have been executed in a certain period. I guess another alternative is to download the traces dumps but here the bottleneck is the download time even for a period of 1 day. Best, Vasileios ________________________________ From: Robert Kisteleki <robert@ripe.net> Sent: Tuesday, September 4, 2018 7:28 AM To: Vasileios Giotsas Cc: ripe-atlas@ripe.net Subject: Re: [atlas] Meta-information dumps for built-in measurements? On 2018-09-04 03:16, Vasileios Giotsas wrote:
Is there any repository like https://ftp.ripe.net/ripe/atlas/measurements/ that contains meta-information about built-in RIPE Atlas measurements (the above repository contains meta-information only for public measurements)?
I couldn't find anything similar in the new FTP repository at https://data-store.ripe.net/datasets/atlas-daily-dumps/
I guess using the API is an alternative but it would be more convenient to have such dumps
Thanks, Vasileios
Hello, https://atlas.ripe.net/api/v2/measurements/?id__lte=1000000 is a pretty good approximation of what you're after. Built-ins change very rarely, so a one-time query will give you virtually everything about built-ins. Note that the above mentioned full dump of measurement metadata via FTP is not sustainable (in its current form it's growing endlessly) so we'll highly likely to change this in the near future. Regards, Robert
So having some sort of metadata dumps makes it faster to go through the queries that have been executed in a certain period. I guess another alternative is to download the traces dumps but here the bottleneck is the download time even for a period of 1 day.
What I read here is a feature request for filtering the measurement list for entries that ran at least partially between t1 and t2. Is that what you're after? Cheers, Robert
Dear subscribers, is DomainMON service (https://atlas.ripe.net/domainmon/) still available and supported? For a week or two I see no charts, only "There is no data for this measurement yet." for my domains. Corresponding measurements are running with default interval and spread. Regards, -- Marek Zarychta
Hello Marek, We are currently working on fixing this issue. We will let you know when the problem is fixed. Thanks for the email and sorry for the inconvenience. Ciao, Massimo Candela Software Engineer RIPE Atlas On 07/09/2018 09:05, Marek Zarychta wrote:
Dear subscribers,
is DomainMON service (https://atlas.ripe.net/domainmon/) still available and supported? For a week or two I see no charts, only "There is no data for this measurement yet." for my domains. Corresponding measurements are running with default interval and spread.
Regards,
Hi Marek, This issue should now be fixed for you. Apologies for the inconvenience. Please do let us know if you see any further problems. Regards, Chris Amin RIPE NCC On 07/09/2018 10:45, Massimo Candela wrote:
We are currently working on fixing this issue. We will let you know when the problem is fixed.
Thanks for the email and sorry for the inconvenience.
On 07/09/2018 09:05, Marek Zarychta wrote:
Dear subscribers,
is DomainMON service (https://atlas.ripe.net/domainmon/) still available and supported? For a week or two I see no charts, only "There is no data for this measurement yet." for my domains. Corresponding measurements are running with default interval and spread.
Regards,
On Fri, Sep 07, 2018 at 11:59:18AM +0200, Chris Amin wrote:
Hi Marek,
This issue should now be fixed for you. Apologies for the inconvenience. Please do let us know if you see any further problems.
Regards, Chris Amin RIPE NCC
Thank you for fixing this issue. Regards, -- Marek Zarychta
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this. Pointers? Thanks, Hank
Hi Hank,
On 12 Feb 2019, at 17:22, Hank Nussbacher <hank@efes.iucc.ac.il> wrote:
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this.
The PDF’s and Keynote can be found here: https://www.ripe.net/support/training/material#mat <https://www.ripe.net/support/training/material#mat> Kind regards, Johan ter Beest RIPE Atlas Team
Pointers?
Thanks, Hank
On 12/02/2019 18:48, Johan wrote:
Hi Hank,
On 12 Feb 2019, at 17:22, Hank Nussbacher <hank@efes.iucc.ac.il <mailto:hank@efes.iucc.ac.il>> wrote:
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this.
The PDF’s and Keynote can be found here: https://www.ripe.net/support/training/material#mat I had looked at that - specifically: https://www.ripe.net/support/training/material/measurements-and-tools-traini... and started from slide 113-173 and found it a bit outdated (see slide 123). Anything else available?
Thanks, Hank
Kind regards, Johan ter Beest RIPE Atlas Team
Pointers?
Thanks, Hank
Hi,
On 12 Feb 2019, at 18:15, Hank Nussbacher <hank@efes.iucc.ac.il> wrote:
On 12/02/2019 18:48, Johan wrote:
Hi Hank,
On 12 Feb 2019, at 17:22, Hank Nussbacher <hank@efes.iucc.ac.il <mailto:hank@efes.iucc.ac.il>> wrote:
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ <https://atlas.ripe.net/resources/training-and-materials/> and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this.
The PDF’s and Keynote can be found here: https://www.ripe.net/support/training/material#mat <https://www.ripe.net/support/training/material#mat>I had looked at that - specifically: https://www.ripe.net/support/training/material/measurements-and-tools-traini... <https://www.ripe.net/support/training/material/measurements-and-tools-training-course/measurements-and-tools-slides.ppt> and started from slide 113-173 and found it a bit outdated (see slide 123). Anything else available?
These are our current training course slides. We are working on a new training course which will be both up to date and more practical. However that won’t be available any time soon. Johan
Thanks,
Hank
Kind regards, Johan ter Beest RIPE Atlas Team
Pointers?
Thanks, Hank
On 12/02/2019 18:22, Hank Nussbacher wrote: As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes. Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes? What are we doing wrong to entice users to install probes? Regards, Hank
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this. Pointers?
Thanks, Hank
Hard to get new probes these days. On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" <ripe-atlas-bounces@ripe.net on behalf of hank@efes.iucc.ac.il> wrote: On 12/02/2019 18:22, Hank Nussbacher wrote: As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes. Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes? What are we doing wrong to entice users to install probes? Regards, Hank > I have been invited to a large CS dept in a university to give a 40 > minute intro into > what is RIPE ATLAS, how does it work, how do you get credits, how many > probes > are there, what is an anchor, where are they located, how does the GUI > work, what type of measurements > can one do, etc. Very very introductory - just to whet their > appetite. A basic intro to RIPE ATLAS. > So I looked in: > https://atlas.ripe.net/resources/training-and-materials/ > and didn't find anything (PS the webinar link is broken). > I am sure there must be some PPT/PDF presentation out there for this. > Pointers? > > Thanks, > Hank
I think it’s quite easy to get a VM these days as well, so the needs have perhaps changed somewhat. I know that hosting a VM anchor is a lot easier now, and people may have an easier time hosting a VM than a probe in some cases. - Jared
On Feb 14, 2019, at 12:13 PM, James Gannon <james@cyberinvasion.net> wrote:
Hard to get new probes these days.
On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" <ripe-atlas-bounces@ripe.net on behalf of hank@efes.iucc.ac.il> wrote:
On 12/02/2019 18:22, Hank Nussbacher wrote:
As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes. Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes? What are we doing wrong to entice users to install probes?
Regards, Hank
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this. Pointers?
Thanks, Hank
I think it’s worth first considering a couple questions: what is the goal here, and what are the constraints on meeting that goal? If the goal is “lots and lots of probes in ever increasing numbers,” than spinning up lots of VM probes would be great. It would be an easy way to get probes in large numbers cheaply and efficiently. But if the goal is to do actual network performance measurements from the perspective of the end users who actually use the Internet, that doesn’t help much. Where Atlas really shines is in the huge number of measurement points on end user connections all over the world. Need to understand what the network looks like to users on some ISP in Venezuela? Atlas probably has a probe, and can tell you that. Here we get into an issue of the low hanging fruit being pretty saturated. For instance, I could plug in a probe at my house, but it would be the third Atlas probe on Comcast in Oakland, California, and wouldn’t really add anything (thus, I have a probe that I’ve been carrying around in my bag for the last few months waiting until I have time to plug it in somewhere more interesting). But there are still a lot of smaller ISPs that don’t have Atlas probes despite having enough end users for measurements to matter, probably because they don’t have any customers who are part of the global network operations community. It should be possible to get probes installed in a bunch of those, but it would require both available probe hardware and a targeted effort. My second question is what the constraints are on sending out new probes. Is there a shortage at the supplier, or is this just something that needs funding? -Steve
On Feb 14, 2019, at 11:22 AM, Jared Mauch <jared@puck.nether.net> wrote:
I think it’s quite easy to get a VM these days as well, so the needs have perhaps changed somewhat.
I know that hosting a VM anchor is a lot easier now, and people may have an easier time hosting a VM than a probe in some cases.
- Jared
On Feb 14, 2019, at 12:13 PM, James Gannon <james@cyberinvasion.net> wrote:
Hard to get new probes these days.
On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" <ripe-atlas-bounces@ripe.net on behalf of hank@efes.iucc.ac.il> wrote:
On 12/02/2019 18:22, Hank Nussbacher wrote:
As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes. Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes? What are we doing wrong to entice users to install probes?
Regards, Hank
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this. Pointers?
Thanks, Hank
This is an interesting point to note. My local ISPs have many probes but the small ones don’t. It’s easy enough for me (and probably many others) to help people get more probes on those large ISPs but once there are a number of them with good uptime, it’s not as valuable. What is important is those smaller ISPs. Perhaps we should try and make some sort of “official” (as in, on behalf of the RIPE Atlas rather than individually) contact with some of these smaller ISPs and see if they can help get probes in their end user networks. Thanks ~ Bryce Wilson, AS202313, EVIX AS137933
On Feb 19, 2019, at 4:56 PM, scg@gibbard.org wrote:
I think it’s worth first considering a couple questions: what is the goal here, and what are the constraints on meeting that goal?
If the goal is “lots and lots of probes in ever increasing numbers,” than spinning up lots of VM probes would be great. It would be an easy way to get probes in large numbers cheaply and efficiently. But if the goal is to do actual network performance measurements from the perspective of the end users who actually use the Internet, that doesn’t help much.
Where Atlas really shines is in the huge number of measurement points on end user connections all over the world. Need to understand what the network looks like to users on some ISP in Venezuela? Atlas probably has a probe, and can tell you that.
Here we get into an issue of the low hanging fruit being pretty saturated. For instance, I could plug in a probe at my house, but it would be the third Atlas probe on Comcast in Oakland, California, and wouldn’t really add anything (thus, I have a probe that I’ve been carrying around in my bag for the last few months waiting until I have time to plug it in somewhere more interesting). But there are still a lot of smaller ISPs that don’t have Atlas probes despite having enough end users for measurements to matter, probably because they don’t have any customers who are part of the global network operations community. It should be possible to get probes installed in a bunch of those, but it would require both available probe hardware and a targeted effort.
My second question is what the constraints are on sending out new probes. Is there a shortage at the supplier, or is this just something that needs funding?
-Steve
On Feb 14, 2019, at 11:22 AM, Jared Mauch <jared@puck.nether.net> wrote:
I think it’s quite easy to get a VM these days as well, so the needs have perhaps changed somewhat.
I know that hosting a VM anchor is a lot easier now, and people may have an easier time hosting a VM than a probe in some cases.
- Jared
On Feb 14, 2019, at 12:13 PM, James Gannon <james@cyberinvasion.net> wrote:
Hard to get new probes these days.
On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" <ripe-atlas-bounces@ripe.net on behalf of hank@efes.iucc.ac.il> wrote:
On 12/02/2019 18:22, Hank Nussbacher wrote:
As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes. Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes? What are we doing wrong to entice users to install probes?
Regards, Hank
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this. Pointers?
Thanks, Hank
On Tue, 19 Feb 2019, scg@gibbard.org wrote: ASN coverage is just 5.6%. That really doesn't give a complete global view for stats. Rather than return money to LIRs every year in their bill, why not state that any LIR running an active probe within their ASN will get a 50Euro credit on their bill? That alone would increase ASN footprint coverage quickly within RIPE. -Hank
I think it’s worth first considering a couple questions: what is the goal here, and what are the constraints on meeting that goal?
If the goal is “lots and lots of probes in ever increasing numbers,” than spinning up lots of VM probes would be great. It would be an easy way to get probes in large numbers cheaply and efficiently. But if the goal is to do actual network performance measurements from the perspective of the end users who actually use the Internet, that doesn’t help much.
Where Atlas really shines is in the huge number of measurement points on end user connections all over the world. Need to understand what the network looks like to users on some ISP in Venezuela? Atlas probably has a probe, and can tell you that.
Here we get into an issue of the low hanging fruit being pretty saturated. For instance, I could plug in a probe at my house, but it would be the third Atlas probe on Comcast in Oakland, California, and wouldn’t really add anything (thus, I have a probe that I’ve been carrying around in my bag for the last few months waiting until I have time to plug it in somewhere more interesting). But there are still a lot of smaller ISPs that don’t have Atlas probes despite having enough end users for measurements to matter, probably because they don’t have any customers who are part of the global network operations community. It should be possible to get probes installed in a bunch of those, but it would require both available probe hardware and a targeted effort.
My second question is what the constraints are on sending out new probes. Is there a shortage at the supplier, or is this just something that needs funding?
-Steve
On Feb 14, 2019, at 11:22 AM, Jared Mauch <jared@puck.nether.net> wrote:
I think it’s quite easy to get a VM these days as well, so the needs have perhaps changed somewhat.
I know that hosting a VM anchor is a lot easier now, and people may have an easier time hosting a VM than a probe in some cases.
- Jared
On Feb 14, 2019, at 12:13 PM, James Gannon <james@cyberinvasion.net> wrote:
Hard to get new probes these days.
On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" <ripe-atlas-bounces@ripe.net on behalf of hank@efes.iucc.ac.il> wrote:
On 12/02/2019 18:22, Hank Nussbacher wrote:
As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes. Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes? What are we doing wrong to entice users to install probes?
Regards, Hank
I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this. Pointers?
Thanks, Hank
Hi, On Wed, Feb 20, 2019 at 06:52:28AM +0200, Hank Nussbacher wrote:
On Tue, 19 Feb 2019, scg@gibbard.org wrote:
ASN coverage is just 5.6%. That really doesn't give a complete global view for stats. Rather than return money to LIRs every year in their bill, why not state that any LIR running an active probe within their ASN will get a 50Euro credit on their bill? That alone would increase ASN footprint coverage quickly within RIPE.
I like that suggestion :-) (Not sure how that will pan out if we reach 50% of all LIRs, but to get from 5% to 20%, it might definitely be an idea) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Hello, On 2019-02-20 09:36, Gert Doering wrote:
Hi,
On Wed, Feb 20, 2019 at 06:52:28AM +0200, Hank Nussbacher wrote:
On Tue, 19 Feb 2019, scg@gibbard.org wrote:
ASN coverage is just 5.6%. That really doesn't give a complete global view for stats. Rather than return money to LIRs every year in their bill, why not state that any LIR running an active probe within their ASN will get a 50Euro credit on their bill? That alone would increase ASN footprint coverage quickly within RIPE.
I like that suggestion :-)
(Not sure how that will pan out if we reach 50% of all LIRs, but to get from 5% to 20%, it might definitely be an idea)
Interesting idea indeed! Let me try to address a few points that were mentioned before, perhaps by providing some background information along the way. The growth rate is indeed slower than in the early days. As with everything, there's no single reason for this. On one hand we had shortage of hardware probes (which is hopefully solved for the moment, see: https://labs.ripe.net/Members/alun_davies/new-ripe-atlas-version-4-probes/do...). On the other hand, it's harder to reach "uncovered" networks and as someone mentioned before, the "the low hanging fruit being pretty saturated". We measure ASN coverage compared to all ASN-s that announce anything at all, so depending on how hard one wants to argue for having a probe "in every AS", this may or may not need improvement. We're certainly encouraging all our ambassadors and prospective hosts to deploy probes where we don't have them yet. The current application process has a built-in preference for new networks. For a few years now the procurement of new probes is funded exclusively by sponsors. Therefore we'd be very happy to see more sponsors stepping up. Finally: the public graph about the number of users shows the total we have so far (meaning users who interacted with RIPE Atlas while they were logged in via RIPE Access). We can, if this is deemed useful, track the number of recent users too (for some definition of recent). Regards, Robert
Hi Robert, all: One suggestion is to reach out to community networks operating in Europe and beyond to help ensure their networks are being monitored as well. Let me know if you need me to facilitate any introductions to the wider community via the IGF Dynamic Coalition on Community Connectivity (DC3) email list. Best, -Michael On Fri, Mar 1, 2019 at 3:15 PM Robert Kisteleki <robert@ripe.net> wrote:
Hello,
On 2019-02-20 09:36, Gert Doering wrote:
Hi,
On Wed, Feb 20, 2019 at 06:52:28AM +0200, Hank Nussbacher wrote:
On Tue, 19 Feb 2019, scg@gibbard.org wrote:
ASN coverage is just 5.6%. That really doesn't give a complete global view for stats. Rather than return money to LIRs every year in their bill, why not state that any LIR running an active probe within their ASN will get a 50Euro credit on their bill? That alone would increase ASN footprint coverage quickly within RIPE.
I like that suggestion :-)
(Not sure how that will pan out if we reach 50% of all LIRs, but to get from 5% to 20%, it might definitely be an idea)
Interesting idea indeed!
Let me try to address a few points that were mentioned before, perhaps by providing some background information along the way.
The growth rate is indeed slower than in the early days. As with everything, there's no single reason for this. On one hand we had shortage of hardware probes (which is hopefully solved for the moment, see:
https://labs.ripe.net/Members/alun_davies/new-ripe-atlas-version-4-probes/do... ). On the other hand, it's harder to reach "uncovered" networks and as someone mentioned before, the "the low hanging fruit being pretty saturated".
We measure ASN coverage compared to all ASN-s that announce anything at all, so depending on how hard one wants to argue for having a probe "in every AS", this may or may not need improvement. We're certainly encouraging all our ambassadors and prospective hosts to deploy probes where we don't have them yet. The current application process has a built-in preference for new networks.
For a few years now the procurement of new probes is funded exclusively by sponsors. Therefore we'd be very happy to see more sponsors stepping up.
Finally: the public graph about the number of users shows the total we have so far (meaning users who interacted with RIPE Atlas while they were logged in via RIPE Access). We can, if this is deemed useful, track the number of recent users too (for some definition of recent).
Regards, Robert
On 01/03/2019 16:14, Robert Kisteleki wrote:
Hello,
On 2019-02-20 09:36, Gert Doering wrote:
Hi,
On Wed, Feb 20, 2019 at 06:52:28AM +0200, Hank Nussbacher wrote:
On Tue, 19 Feb 2019, scg@gibbard.org wrote:
ASN coverage is just 5.6%. That really doesn't give a complete global view for stats. Rather than return money to LIRs every year in their bill, why not state that any LIR running an active probe within their ASN will get a 50Euro credit on their bill? That alone would increase ASN footprint coverage quickly within RIPE. I like that suggestion :-)
(Not sure how that will pan out if we reach 50% of all LIRs, but to get from 5% to 20%, it might definitely be an idea) Interesting idea indeed!
Let me try to address a few points that were mentioned before, perhaps by providing some background information along the way.
The growth rate is indeed slower than in the early days. As with everything, there's no single reason for this. On one hand we had shortage of hardware probes (which is hopefully solved for the moment, see: https://labs.ripe.net/Members/alun_davies/new-ripe-atlas-version-4-probes/do...). On the other hand, it's harder to reach "uncovered" networks and as someone mentioned before, the "the low hanging fruit being pretty saturated".
We measure ASN coverage compared to all ASN-s that announce anything at all, so depending on how hard one wants to argue for having a probe "in every AS", this may or may not need improvement. We're certainly encouraging all our ambassadors and prospective hosts to deploy probes where we don't have them yet. The current application process has a built-in preference for new networks.
For a few years now the procurement of new probes is funded exclusively by sponsors. Therefore we'd be very happy to see more sponsors stepping up.
Finally: the public graph about the number of users shows the total we have so far (meaning users who interacted with RIPE Atlas while they were logged in via RIPE Access). We can, if this is deemed useful, track the number of recent users too (for some definition of recent).
Regards, Robert
And what about the idea to encourage greater ASN coverage by providing a discount on LIR membership for those who have at least one active ASN probe in their ASN? Regards, Hank
Hello, It's not you, a recent change in the script broke the link. Apologies, this has been fixed now (you probably need to reload). Regards, Robert On 2020-11-09 07:03, Hank Nussbacher wrote:
When viewing the credit page:
https://atlas.ripe.net/user/credits/
One can see numerous lines where one has accumulated credits (see attached screenshot).
Each line has a hotlink similar to:
https://atlas.ripe.net/probes/17879%3E17879
or
https://atlas.ripe.net/probes/17895>17895
This always leads to:
This page does not seem to exist…
What am I doing wrong?
Thanks,
Hank
On 2019-02-14 19:10:17 +0200, Hank Nussbacher wrote:
On 12/02/2019 18:22, Hank Nussbacher wrote:
As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes. Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes?
The page also shows 11000 abandoned probes. Maybe there is an equilibrium between new probes being added and old ones being abandoned, but the user count keeps increasing because inactive users aren't detected? hp -- _ | Peter J. Holzer | we build much bigger, better disasters now |_|_) | | because we have much more sophisticated | | | hjp@hjp.at | management tools. __/ | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/>
participants (15)
-
Bryce Wilson
-
Chris Amin
-
Gert Doering
-
Hank Nussbacher
-
James Gannon
-
Jared Mauch
-
Johan
-
Johan Ter Beest
-
Marek Zarychta
-
Massimo Candela
-
Michael J. Oghia
-
Peter J. Holzer
-
Robert Kisteleki
-
scg@gibbard.org
-
Vasileios Giotsas