Resolve any IPv4 or IPv6 address against four RIPE NCC data sources. The headline answer comes from RIPE IPmap — a geolocation system that triangulates real router positions from live RIPE Atlas traceroute data — which is closer to "last hop of the actual route" than any AS-level guess. The other cards give you the supporting evidence: whois holder, the country of the BGP-origin AS, the MaxMind GeoLite consumer-database estimate, and the AS path currently visible to RIS collectors.
The answers will often disagree, and that disagreement is the signal. IPmap is the most accurate for infrastructure IPs (transit routers, IXP hops) but coverage is sparse for end-user space; whois country is bureaucratic; AS origin tells you who announces the route; MaxMind tries to guess where the human sits.
queries run from your browser straight to stat.ripe.net and ipmap-api.ripe.net — no intermediate server
isp — from RIPEstat whois (inetnum / inet6num, netname, descr, country, org) and network-info (prefix, origin ASN), enriched with as-overview for the AS holder. The country here is the registered country of the netblock — typically the org's HQ, not necessarily where the IP physically routes.
ipmap — RIPE IPmap infers infrastructure locations from multiple engines run in parallel. The engine breakdown is shown so you can judge which signal drove the answer. latency triangulates physical position using speed-of-light constraints on the last week of RIPE Atlas traceroute data. single-radius triggers fresh active Atlas measurements when latency lacks data. reverse-dns parses PTR records for embedded location hints (IATA codes, city names) via CAIDA's hoiho. ixp matches the IP against PeeringDB's IXP / facility records. crowdsourced uses operator-contributed locations. Coverage is strong for core infrastructure (transit routers, IXP hops) and thin for end-user / mobile / CG-NAT space — if the exact IP has no data, the tool samples a handful of likely-infrastructure addresses from the same announced prefix and shows the first neighbor with a hit, clearly labelled.
bgp origin — pulls the rightmost ASN from each BGP path returned by looking-glass (that's the origin AS, the network announcing the prefix) and resolves its registered country via whois on the AS object. Multiple origin ASNs are shown when the prefix is anycast or MOAS. This is AS-level only — the actual route may exit anywhere that AS operates.
geodb — RIPE serves MaxMind's GeoLite2 country/city dataset via maxmind-geo-lite; the same dataset most "what's my IP" sites quote. RIPE's geoloc aggregates this with other sources for the containing prefix.
as path — every unique BGP path visible to RIPE RIS collectors right now, sorted shortest-first, with the collector(s) that observe each one. Look for unexpected transit, multiple origins, or short bogus paths as signs of route leaks or hijacks.