[{"data":1,"prerenderedAt":60},["ShallowReactive",2],{"doc:\u002Fgetting-started\u002Fdata\u002Faccuracy":3},{"page":4,"toc":56},{"path":5,"title":6,"description":7,"blocks":8},"\u002Fgetting-started\u002Fdata\u002Faccuracy","Methodology & verification","How IPScope separates declared registry country from physical routing reality and calibrates confidence.",[9,12,17,19,25,28,51,54],{"type":10,"text":11},"p","IP addresses do not have built-in GPS coordinates. Operators lease blocks across borders, announce anycast prefixes from dozens of PoPs, and publish RFC 8805 geofeeds. IPScope exposes both the paperwork registration and the physical routing location directly in every `geo` response.",{"type":13,"level":14,"text":15,"id":16},"heading",2,"Declared vs. physical country (`is_virtual_location`)","declared-vs-physical-country-is-virtual-location",{"type":10,"text":18},"Every lookup includes three country fields inside `geo`:",{"type":20,"items":21},"list",[22,23,24],"`declared_country_code`: the country recorded in RIR WHOIS\u002FRDAP allocation paperwork or operator geofeed.","`physical_country_code`: the country where BGP routing and active latency measurements place the infrastructure.","`is_virtual_location`: `true` whenever a prefix is registered in one country (`declared_country_code`) but physically routed in another (`physical_country_code`).",{"type":13,"level":14,"text":26,"id":27},"Interpreting `accuracy_radius_km` and `confidence`","interpreting-accuracy-radius-km-and-confidence",{"type":29,"columns":30,"rows":34},"table",[31,32,33],"Network type","Typical `accuracy_radius_km`","Typical `geo.confidence`",[35,39,43,47],[36,37,38],"Fixed residential broadband (FTTH \u002F cable)","5 – 25 km","`0.88` – `0.97`",[40,41,42],"Regional datacenter \u002F cloud PoP","5 – 15 km","`0.92` – `0.99`",[44,45,46],"Cellular carrier gateway (4G\u002F5G CGNAT)","50 – 250 km","`0.70` – `0.85`",[48,49,50],"Global anycast prefix (`location_type: \"anycast\"`)","Country-level or PoP-nearest","`0.65` – `0.80`",{"type":13,"level":14,"text":52,"id":53},"Reporting a correction","reporting-a-correction",{"type":10,"text":55},"Network operators and customers can submit corrections programmatically via [`POST \u002Fv1\u002Ffeedback`](\u002Fapi-reference\u002Fendpoints\u002Fmeta) or by emailing [abuse@ipscope.io](mailto:abuse@ipscope.io) with an RFC 8805 geofeed URL.",[57,58,59],{"id":16,"text":15,"level":14},{"id":27,"text":26,"level":14},{"id":53,"text":52,"level":14},1793226504196]