3 ms·
Nice idea, but shoddy implementation, it does not properly detect the starting point based on my IP and the route shown is not matching what I know about the ph
by jacquesm 1y ago
Nice idea, but shoddy implementation, it does not properly detect the starting point based on my IP and the route shown is not matching what I know about the physical topology of the network in this region. You probably should ask infrastructure providers if they are willing to give you access to the endpoint and physical routes rather than just to use geolocation for IP addresses resulting in errors and unrealistic routes. There are only a couple of players in that space, and I think they sell the data. Otoh, given the current situation with attacks on infrastructure they might not be willing to accommodate a party without a strict need.
- PranaFlux 1y agoWould you mind sharing the link (after removing the data you don't want to share)? I'm using IPInfo's data and each hop IP is the end of a segment so it's normal it doesn't follow your expected topology (to which we can add the limitations of traceroute)
- jacquesm 1y agoNot much point, really, it only detects one hop correctly the rest is garbage. So all that's left is my home IP address, and that gets placed well over a 100 km from where I actually am. I don't mind :)
- reincoder 1y agoI work for IPinfo and we provided the data for the project. I would really appreciate your insight on this. We run ping and traceroute operations from 1,200 servers across the world to every (within reason) IP address out there. So, we have ping RTT and traceroute data history of these measurements. Considering the physical network topology does not match the physical network topology, we would love to hear your thoughts. Unrouted IP addresses do not appear on the internet traffic, and we have limited network data for them. If you can share your traceroute output and obfuscate as much data as possible, we will be happy to investigate and share feedback.