COMMUNITY BUILT. EVIDENCE FIRST.
IP addresses tell part of the story.
We’re building the map together.
Find a network’s approximate location, with the evidence and uncertainty behind it.
Enter an IP to see what the community knows. If there isn’t enough data, we’ll say so.
Public network summaries are available as CC0 data. Build with them, improve them, share them.
Using this lookup does not request GPS. Location contributions start with an explicit choice.
IP locations are estimates. Each result carries an accuracy radius and the age of its evidence.
02 / REVERSE LOOKUP
Find published network prefixes whose estimated locations overlap an area.
A geographic search of our published estimates. Results describe networks, not people or individual devices.
Choose coordinates and a radius to see the network evidence available nearby.
03 / THE PUBLIC DATASET
Download the latest public network summaries. No account needed.
Machine-readable network prefixes, approximate locations, uncertainty, and evidence timestamps.
Checking the latest snapshot…
An empty dataset downloads with its schema. No location data is invented to fill gaps.
SMALL BUSINESS. PUBLIC RESOURCE.
Public data and an open SDK form the foundation. Managed service, private deployments, and support can keep the project sustainable.
Project goal, not a statement of current paid product availability.
HELP SHAPE THE SERVICE
Register interest in managed hosting, a dedicated deployment, or support. Your response helps us decide what to build next.
Paid plans are not active yet; no payment is taken.
04 / MEASUREMENT
Held-out evaluation, kept separate from the observations used to build an estimate.
Observations held out from their evaluated estimate
Half the evaluated estimates fall within this distance
Nine in ten evaluated estimates fall within this distance
Evaluating an estimate against the same observations that created it can overstate accuracy. Independent results need held-out evidence.
A map pin represents an area. Uncertainty grows for sparse observations, mobile networks, VPNs, and networks used in several places.
No observed accuracy means no accuracy claim. Global percentages need representative coverage, not just a successful local test.
05 / DEVELOPERS
Ask for browser location with a clear notice, then use an approximate IP estimate if access is declined or unavailable.
Browser location & IP fallback
View SDK (opens in a new tab) APPLENative Apple API client
View SDK (opens in a new tab) ANDROIDNative Android API client
View SDK (opens in a new tab) FLUTTERMobile & desktop API client
View SDK (opens in a new tab) SERVERServer-side API client
View SDK (opens in a new tab)Show your visitors a clear contribution notice before calling the SDK. Browser location permission alone is not permission to improve a public dataset.
Say that a successful location will automatically contribute coarse location evidence.
The SDK requests location only when your application calls it.
When agreed and granted, contribute automatically. Otherwise return an IP estimate when available.
Call after a user action. A declined location request does not send a GPS contribution.
START BUILDING
Get an origin-restricted browser app token. The initial free quota is 100,000 requests per month.
This token is for your client application. Register only site origins you control, including a port for local development.
/api/lookup?ip=…IP → network location
/api/reverse?latitude=…&longitude=…Place → known prefixes
/api/observationsConsented evidence · app token required