ip2location.com reports inaccurate data (and does not want to correct them)

ip2location.com provides IP to geographical location service. They provide various databases that allow to make a link between an IP address and different informations (location, country, city, language etc.)

As a small Internet Service Provider, we noticed that some data stored in the ip2location.com database are incorrect. The problem concerns in particular the “ISP” field, as well as “City”.

We contacted ip2location to report and have these errors corrected. Unlike other competing solutions, they do not offer an interface to make or suggest changes to the database: you have to go through the contact service.

And it is here that the problems begin.

You will find below the content of the exchanges with the customer support. Obviously, the people who manage ip2location.com do not understand the difference between a LIR and an ISP, which is a bit surprising when managing such a database. I leave you to judge their strange argument, which involves… North Korea.

Are we the only ISP affected by this problem? Probably not. Given their response, it is likely that part of the ip2location database contains errors, at least for the “ISP” field.

Before using their services or buying their products, it is worth knowing this information. Other competing solutions exist. They are probably not free of errors, but at least they do the right thing to correct them when they are discovered, and they do not treat users with contempt.

TO: Support

Dear Sir or Madam,

We have been trying for several months to correct incorrect data in your databases about our IPv6 range. This problem that poses real difficulties for us.

We are an ISP located in Switzerland. We provide IPv6 connectivity and services to end-users. We own the 2a0c:b641:270::/44 ipv6 prefix, as you can check on ripeDB.

For some reason, this range has been attributed to ISP “Cedric Rossius” in your database. Correct value should be “Zaledia.com networks” Location is not accurate, too: “Bern, CH” must be replaced by “Fully, CH”. Domain value should be “zaledia.com”

cedric Rossius is the org. who provides us with our IP range, but it is NOT our ISP. Moreover, it is illogical to put an upstream in the value “ISP”, since we are precisely our own ISP.

For example, when people go to www.whatismyip.com (which uses your data) from our IP addresses, they should see that the ISP is “zaledia.com” and not “Cedric rossius”.

These errors cause confusion and misunderstandings among our users. The current content of your database does not reflect the reality.

Could you please update the “ISP” “City” and “domain” records, based on the information provided above, for prefix 2a0c:b641:270::/44 ? is there some interface so that users can update their data?

I remain at your disposal for any information, with my best regards.

best regards, J.Sansonnens

reply:
Hi Julien,

Can you share with us more information how do you get the range from “Cedric Rossius”?

Regards,

Kim Loong
IP2Location Customer Success Team
Hexasoft Development Sdn Bhd
Website: http://www.ip2location.com
Facebook: https://www.facebook.com/ip2location
Twitter: https://www.twitter.com/ip2location

reply:

Hi

Thanks for your reply.
Cedric Rossius is not an ISP, it’s a LIR (local internet registry). They get IP blocks from RIPE and then allocate them to ISP’s like us. Then, we allocate ips to our customers,
cedric Rossius is definitely not our upstream, as we use Hurricane-electric, Cogent and others. But that does not change the problem: the IP address block should be linked to the ISP, ie the organization that provides internet connectivity to its customers: Zaledia.com.
People querying services using your database (ie: whatismyip.com) don’t care about upstreams, LIRs, RIPE and so on: they just want to know which ISP they are using, ie “zaledia.com” for out ipv6 block 🙂
I remain at your disposal for any info
Best regards, Julien
reply:
Hi Julien,

We do aware the this range is belonging to LIR.

We have received many complaints regarding the reallocation abuse in the range you are currently in.

For example, the IP address range 2a0c:b641:21f::/48 has been reported as in North Korea (KP) which we could not verified after numerous efforts. There are many more cases.

After discussion with our customers including law enforcers, we must report it as “Cedric Rossius” because it is the legal entity verified by RIPE.

Regards,

Kim Loong
IP2Location Customer Success Team
Hexasoft Development Sdn Bhd
Website: http://www.ip2location.com
Facebook: https://www.facebook.com/ip2location
Twitter: https://www.twitter.com/ip2location

reply:
I think there is a big misunderstanding here. Are you telling me that for all IP address blocks in your database, you’re reporting the LIR and not the ISP ? This seems unbelievable to me, because it means that the “ISP” field actually has no use as the information reported is wrong.
You write that Cédric Rossius is the legal entity verified in the RIPE for our block: this is incorrect. Our IPv6 range is legaly and very clearly assigned to “Zaledia.com”, not to Cédric Rossius. Please, look here: https://apps.db.ripe.net/db-web-ui/#/lookup?source=ripe&key=2a0c:b641:270::%2F44&type=inet6num
Once again, I do not understand the reasons you keep incorrect values in the DB. Zaledia.com is not responsible for the erroneous assignment of other blocks to North Korea! What is the relationship with us?
We kindly request that the official information contained in the RIPE be properly reported in your database. Currently, the information in your database is wrong and does not reflect reality. Once again, this causes us some prejudice, as the wrong information is spread on many services using your DB. As you may understand, we cannot accept this situation.
Commentaires facebook

Leave a Comment

Votre adresse de messagerie ne sera pas publiée. Les champs obligatoires sont indiqués avec *