🇮🇴IP address lookup for British Indian Ocean Territory

What a lookup returns for British Indian Ocean Territory

The country block is filled in from the address itself — you do not pass the country in. Region, city and network vary per address.

{
  "ip": "203.0.113.42",
  "location": {
    "country": {
      "name": "British Indian Ocean Territory",
      "code": "IO",
      "capital": "Diego Garcia",
      "phoneCode": "+246",
      "flag": "🇮🇴"
    },
    "region": { "name": "…", "code": "…" },
    "city": "…",
    "latitude": 0.0,
    "longitude": 0.0,
    "accuracyRadius": 50
  },
  "connection": { "asn": 0, "isp": "…", "org": "…" }
}

How accurate is geolocation in British Indian Ocean Territory?

Country-level accuracy is reliable — the address blocks allocated to networks operating in British Indian Ocean Territory are well documented by the regional registry. City-level accuracy is not a guarantee anywhere: an address is mapped to where its network announces it, which is often a provider hub rather than the user's suburb.

Every response carries an accuracyRadius in kilometres. Treat the coordinates as the centre of a circle that size, not as a pin. Mobile and corporate connections in British Indian Ocean Territory routinely resolve to a different city entirely, and anyone on a VPN will resolve wherever the exit node sits.

Common uses

• Showing prices in the local currency and applying the right tax treatment for visitors from British Indian Ocean Territory.
• Defaulting the country and calling code (+246) on sign-up forms so people are not scrolling a list of 200.
• Meeting content licensing or regulatory rules that differ by country.
• Flagging logins from an unexpected country during fraud review.