We experienced an issue where some nodes from our API were returning unexpected geolocation for IPv4 IP addresses between 128.0.0.0 and 191.255.255.255.
The issue was caused by human error. We've added additional guards to minimize such issues to happen in the future. We apologize for the inconvenience.
