Locating an IP address in a specific country seems like a simple operation: you enter the address into an online tool, and you get a result. For the IP 77.87.229.22, the reality is more complex. Depending on the geolocation database queried, this address appears sometimes in Russia (Moscow, MTS PJSC), sometimes in Germany (Bonn), and sometimes simply “in Europe” without further precision.
This divergence between IP geolocation services is not a bug. It reflects a technical operation that most guides gloss over.
Compared results of geolocation databases for IP 77.87.229.22
Querying several IP geolocation tools for the same address produces results that do not always match. The table below summarizes the discrepancies observed for the address 77.87.229.22 according to the available data.
| Source / Database | Displayed Country | City | Operator |
|---|---|---|---|
| Some databases (e.g., MaxMind) | Russia | Moscow | MTS PJSC |
| Other services (e.g., DB-IP) | Germany | Bonn | Not specified |
| Generic tools | Europe (without precision) | – | – |
Three tools, three answers. This type of discrepancy occurs when an IP address block changes geographic allocation between two operators located in different countries. Therefore, searching for the country of IP address 77.87.229.22 implies understanding why these databases do not provide the same answer at the same time.
Why an IP address can change country without warning
IP geolocation databases do not locate a physical device. They locate a block of addresses registered with a regional Internet registry (RIR). In Europe, this registry is RIPE NCC.
Each IP block has a WHOIS record that contains a “country” field and sometimes a “geoloc” field with coordinates. When an operator relinquishes or transfers a block to an entity in another country, the WHOIS record is updated by the RIR.
The lag between WHOIS and commercial databases
The WHOIS update can be quick, but large commercial geolocation databases (MaxMind, IP2Location, DB-IP) only reflect it at their own publication pace. At MaxMind, these cycles occur several times a week. Other databases update less frequently.
During this lag, an address like 77.87.229.22 can be effectively used in a new country while some services continue to display it in the old one. This is the main cause of the contradictions observed in the previous table.
The particular case of CGNAT and mobile IPs
The problem worsens for connections behind a CGNAT (Carrier-grade NAT). In this case, the visible public IP address corresponds to the operator’s gateway, not the user’s actual location. For mobile traffic, the displayed location may reflect a network node located hundreds of kilometers away from the subscriber.
Reliable method to identify the country of an IP address
Relying on a single IP geolocation tool produces a potentially outdated result. Cross-referencing multiple sources reduces this risk. Here are the concrete steps to locate an IP with a reasonable level of reliability.
- Query the WHOIS of the competent RIR (RIPE NCC for European addresses) to read directly the “country” field of the official record, without commercial intermediaries
- Compare with at least two commercial geolocation databases (MaxMind GeoLite2, IP2Location, DB-IP) to detect any discrepancies
- Check if the IP belongs to a range announced via BGP by an identified operator, which gives a clue about the country of the originating network
- Consult a traceroute tool to observe through which network nodes the traffic transits, which can confirm or refute the geographical region
When the results converge (WHOIS, commercial databases, and traceroute point to the same country), the location is reliable. If two or more sources diverge, the WHOIS of the RIR remains the most up-to-date reference as it reflects the administrative status of the address block.
Limits of IP geolocation and regulatory framework
The accuracy of geolocation by IP address varies depending on what is being identified. At the country level, reliability is generally high when databases are up-to-date. At the city level, margins of error increase significantly, especially for mobile connections or IPs shared via CGNAT.
What IP geolocation cannot do
Locating the country of an IP address does not equate to locating a person. The IP address identifies a point on the operator’s network, not a home or office. The CNIL considers the IP address as personal data under GDPR, which strictly regulates its use for profiling or tracking purposes.
For IP 77.87.229.22, the available data indicates a location fluctuating between Russia and Germany depending on the databases consulted. This instability is typical of an address block that has undergone recent reassignment or belongs to a multi-country operator.
One point to remember: no IP geolocation tool is infallible at any given moment. The method that produces the most reliable result remains the cross-referencing of the regional registry WHOIS and at least two commercial databases. For an address whose location diverges between sources, it is the WHOIS record that serves as the reference.