Hacker News Reader

Comment by misframer | Hacker News Reader

The following shows up at Fremont but it should be NYC, right?

    7  100ge10-1.core1.nyc6.he.net (184.105.64.178)  10.344 ms  9.712 ms  20.411 ms

View on HN

Yes this is the disadvantage of traditional IP geolocation databases. They work mostly by sourcing information from RIRs and ISPs. Unfortunately for a lot of larger organizations which typically exist in internet backbone that is very inaccurate. This skews the traceroute mapping significantly.

I don't want to shamelessly plug-in stuff here but we have geolocation API which uses latency triangulation and does not suffer from those issues.

Stefan - I would be more than happy to donate the API access if you have time to integrate it. Can I email you with details ?

> we have geolocation API which uses latency triangulation and does not suffer from those issues

Who is "we"? I'd like to test drive a service like that.

You can send me email to janusz@speedchecker.xyz or through contact us page on www.speedchecker.xyz

We operate large scale testing platform which can ping from many locations so we can triangulate better, demo here - http://www.maplatency.com

Here is more information and demo page> http://www.speedchecker.xyz/server-geolocation.html

Reply on news.ycombinator.com