There are a number of factors that can influence the performance and results of a software probe within the same ASN, within the context of an ASN that is a last mile network operator... I would say that the community is somewhat reliant upon people self-reporting the general street address and physical location of the probe correctly. Within the same ASN in a regional last mile broadband network there might be probes on DOCSIS3 last mile technology, GPON, active ethernet, in datacenter space/colocation, etc. My probe which is singlehomed to a spacex starlink v1 beta terminal for a while was in the same Google ASN as a bunch of terrestrial 10/100GbE fiber stuff but its results were obviously quite different. On Thu, 31 Mar 2022 at 12:28, Hugo Salgado <hsalgado@nic.cl> wrote:
On 20:43 31/03, Andreas Härpfer wrote:
Of course I am wildly guessing here, but the 15 probes in Hostinger Sao Paulo actually look a bit fishy to me. Consecutive probe numbers, all created at roughly the same time, all in the same v4 /24 and v6 /64. To me this looks like an "Atlas credit mining farm" … so more a mis-use than an overuse.
So right there is the disincentive of having probes in the same ASN: they accumulate progressively fewer credits, until they reach zero.
Hugo
-- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas