> On Dec 20, 2022, at 8:38 AM, ripe.net@toppas.net wrote:
>
> On the one hand i agree with Stephane, but on the other hand, it is a fact that there are a few large providers/CDNs who have a significant share... of specific webservices. I don't like that either, but i can't deny it either. I agree, that manually selecting those providers/CDNs for such a measurement could be understood as a statement. But maybe there's another way, to select which one of those providers/CDNs to measure? Instead of manually selecting them, there could be some sort of "threshold" which a provider/CDN has to reach, to be part of this kind of measurement. This way, it wouldn't be a statement, but a static delimitation. I am unsure what kind of threshold it could be, and how to detect it. It should probably be some sort of technical value.
>


I’m also thinking of those of us that also have multiple CDN planes, etc.. and the fact that if we give out a test-point, those customers tend to get billed for the usage.  There’s also a lot of regionality to content and things, it’s unlikely you would see the same performance in a far-flung geolocation to a primarily US property or vice-versa.

Even if you were to do $employer.com that doesn’t mean that content is hosted on all our servers, they have various functions and roles on our side, so you end up with all the measurement bias that would occur from there.  I know that things are similar at other CDNs.

- Jared
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas