New sys tags, eyeball networks

[jimaek]

New sys tags, eyeball networks

[alexey-yarmosh]

I think when using the magic field we could then set a location to "amsterdam+eyeball" to limit the probes to non-datacenter, right?

yes

[MartinKolarik]

The options we have here:

• ipinfo privacy.hosting (as suggested) https://ipinfo.io/developers/privacy-detection-database
• maxmind traits.isHostingProvider
• ip2location usage_type (https://blog.ip2location.com/knowledge-base/what-is-usage-type/)

So the question is if we just use ipinfo regardless of who wins the city location or something more advanced. The very first IP I tried, ipinfo got it wrong, so maybe it's worth testing each on our verified IP list.

[jimaek]

Based on what I've read I trust ipinfo more, so maybe we can keep things simple? I was only thinking if we need a fallback or not.

Also I think the maxmind parameter you quoted is on the more expensive tier than the one we pay.

[MartinKolarik]

I don't mind keeping it simple, but I'm somewhat skeptical now that it got an OVH IP wrong. The parameters I listed are what we get in our responses so we have access to all three.

[jimaek]

We have access but we pay per query, and that parameter is part of the more expensive query type. At least that's what I see in the UI.
I dont really worry about accuracy here, we should allow people to modify this field for their own probes too.
I only worry about an ipinfo outage, but I guess the cached data should be enough to keep us running for a while

[MartinKolarik]

We have access but we pay per query, and that parameter is part of the more expensive query type. At least that's what I see in the UI.

Then we are already making those more expensive queries. I didn't change anything about the requests, just looked at what we have already.