Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support ISP as metadata #70

Closed
jimaek opened this issue Apr 3, 2022 · 1 comment · Fixed by #79
Closed

Support ISP as metadata #70

jimaek opened this issue Apr 3, 2022 · 1 comment · Fixed by #79
Assignees

Comments

@jimaek
Copy link
Member

jimaek commented Apr 3, 2022

We already have this info as part of https://globalping-geoip.global.ssl.fastly.net/

"as": {
"name": "internetia sp.z o.o.",

So why not use it. I suggest we start collecting this data from all probes and exposing in our API.
And make it part of POST for measurements too to all users to do limit their tests to certain providers.

Example use-case: I want to understand my performance from AWS to my CDN. Or to choose which Hetzner location I should be using. I could then run a latency test from "network: hetzner".

This means it should also be part of #51

@jimaek
Copy link
Member Author

jimaek commented Apr 6, 2022

We also need ISP data to be actionable. It's a new type of location, so the client must be able to ping from internetia and hetzner like he would from a city or a country

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants