Skip to main content

​
What this page is for

At /settings/ip-location (singular), the IP Locations page lets you define Public Locations — IP ranges mapped to friendly named locations. IP Locations page with Public Locations heading and No public locations found empty state By default, Protect geolocates devices using their public IP via standard databases (e.g. resolving 203.0.113.x to “London, United Kingdom”). That works for most cases but misses some realities:
  • VPN egress IPs lump remote workers into one city
  • Branch offices on shared upstreams look like the head office
  • Cloud-NAT’d traffic gets attributed to the provider’s region
Public Locations override the default geolocation for specific IP ranges with your real-world names.

​
Adding a location

1

Click + New Location

Top-right.
2

Provide the location details

  • Name — friendly label (e.g. HQ London, Branch — Manchester, VPN — Engineering)
  • Public IP / range — single IP or CIDR (203.0.113.0/24)
  • City / Region / Country — what Protect will display for devices behind this IP
3

(Optional) coordinates

Latitude / longitude for accurate map plotting (Device Explorer’s globe).
4

Save

Devices currently appearing as the default-geolocated location will re-attribute on the next sync.

​
Common patterns

​
Why it matters

The location.country and location.city fields are used in many places:
  • Devices grid Location column
  • Tag rules like location.country:United Kingdom
  • Dashboard Tag Coverage Map (when location-based tags exist)
  • Geographic risk reporting — “devices in restricted countries”
  • Saved views filtered by region
A device incorrectly attributed to “Mountain View, US” because it’s behind a VPN to a different region pollutes every downstream view. Correct IP-Locations fix this cleanly.

​
Best practices

The most common geolocation surprise — remote workers appearing to be in the VPN exit’s city. Configure these first.
Cloud-hosted servers behind NAT or load balancers can attribute to the cloud provider’s data centre, not your business region. Override.
Once you’ve got accurate locations, build location-based tags (UK, EMEA, APAC) and use them in Vitals requirements.
When you change ISPs, restructure NAT, or migrate offices, re-validate your IP Locations.

​
Cross-references

Device Explorer

Where the map view uses these locations

Tags & Logic Engine

Location-based tag rules

Query Language

Filter by location.* fields