One of my probe is wrongly identified as VPN

[SukkaW]

$ docker logs --tail 25 globalping-probe

Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Checking for the latest version
Current version 0.38.0
Latest version 0.38.0
[2025-06-11T10:49:05.739Z] Current node.js version v20.13.0
[2025-06-11T10:49:05.743Z] Wanted node.js version v20.13.0
[2025-06-11T10:49:05.743Z] No persistent UUID file. Generating a new one.
[2025-06-11 10:49:06 +00:00] [INFO] [general] Starting probe version 0.38.0 in a production mode with UUID 61ed9191.
[2025-06-11 10:49:06 +00:00] [ERROR] [api:error] Connection to API failed: Error: vpn detected: 2.59.[redacted]
[2025-06-11 10:49:06 +00:00] [ERROR] [api:error] Retrying in 1 hour. Probe temporarily disconnected.

If this is Globalping's attitude toward some hosting providers (using IP2Location), I am afraid I have to pull the plug on all my probes and ask my friends in the industry to do so as well.

[jimaek]

Please submit a geo correction request here https://geodebug.globalping.dev/ so we could see the IP and check what is happening

[SukkaW]

https://geodebug.globalping.dev/

?

[jimaek]

Indeed I forgot we run the check :) Please email me the IP to check.

But know that we don't discriminate against hosting providers, we use commercial IP databases to block VPN usage to improve the quality of the probe network.

False positives happen and we try to fix them

[SukkaW]

But know that we don't discriminate against hosting providers, we use commercial IP databases to block VPN usage to improve the quality of the probe network.

As a former contributor of globalping-probe (with 4 commits), I can read code. I know Globalping is using IP2Location, and AFAIK (from my past experience in the IaaS industry), IP2Location is just lazy and they simply mark the entire ASN as "VPN" or "Proxy".

[jimaek]

I'm trying to help. We use ip2location for VPN detection, but we use many geo DBs in general for IP metadata.
We use ip2location specifically for VPN because they were the only ones that provided us that data for free when we wrote the implementation and based on our tests it was reliable enough to be used in production.

If you send me the IP that has the issue I'll take a look at what we can do