---
title: "Troubleshooting Node IP Geolocation Inaccuracy"
slug: "troubleshooting-node-ip-geolocation-inaccuracy"
updated: 2023-01-06T15:48:57Z
published: 2023-01-06T15:48:57Z
canonical: "docs.catchpoint.com/troubleshooting-node-ip-geolocation-inaccuracy"
---
> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Troubleshooting Node IP Geolocation Inaccuracy
Geolocation services such as Maxmind do not update their databases automatically, but rather perform manual location updates. This can lead to inaccurate location results when searching for Catchpoint Node IPs, as IPs are subject to change. Catchpoint does not have control over how geolocation services update their database. Results returned by geolocation services should be taken into consideration only after following the troubleshooting guide below.
## Troubleshooting
In order to troubleshoot, consider using multiple geolocation services when checking for an IP's location. Below is a scenario where Maxmind and Ultratools are returning two different locations for the same IP Address. Note that Maxmind geolocation services are not 100% accurate according to their accuracy page.
**MaxMind**
**UltraTools**
Since the services are returning conflicting results, we can confirm which service is up-to-date by running a trace route from our machine to the IP in question. The result below shows that UltraTools is reporting the correct location, since the hops reach Toronto.
