Hi all!
I discovered a disturbing practice how RIPE Atlas probes are used by at least
one major provider which significantly impacts measurement results and
interpretation of these results. I want to share it with you to open discuss
about how to deal with such cases.
I was doing traceroutes f
Hi Grzegorz,
While I don't have an immediate response about whether/what RIPE ATLAS should
do, I'm curious to know whether there's a simple criterion (e.g., ASN?) to
select the probes in question. I'd like to see whether my measurements show any
bias for them.
I'm asking publicly because othe
Grzegorz,
Are these software of hardware probes? If hardware then the “experiment” they
are used in has cost RIPE funds for the hardware. In my opinion that is worse
than using SW probes.
Regards,
Ernst J. Oud
Met vriendelijke groet,
Ernst J. Oud
> On 2 Jul 2024, at 11:38, Ponikierski, Grze
Which ASN does this relate to ?
Colin
Sent from my iPod
> On 2 Jul 2024, at 11:13, Ernst J. Oud wrote:
>
> Grzegorz,
>
> Are these software of hardware probes? If hardware then the “experiment” they
> are used in has cost RIPE funds for the hardware. In my opinion that is worse
> than usin
On Mon, Jul 01, 2024 at 02:30:13PM +,
Ponikierski, Grzegorz via ripe-atlas wrote
a message of 149 lines which said:
> RIPE Atlas probes are not tagged and separated into groups that can
> be used appropriately for public and internal/private measurements.
This is not enirely true, RIPE At
Since we talk about usage of public service, I think that there is nothing to
hide. Let me answer all questions.
Problem refers to these PCCW AS3491 probes:
7007
7010
7032
7079
7080
7172
7198
1002754
1002771
1002785
1002844
1003737
1005609
They are are virtual anchor and software probes. PCCW h
