Skip to content

Geo

Locate an IP address and identify the network that operates it.

Public, rate-limited per IP

No auth required. Held to the shared public budget (~1,200 requests/min per IP, 429 over). Sustained or high-volume use should authenticate to run against plan quotas instead. See rate limits.

Every device on the internet sits inside an Autonomous System (AS), a network run by one organisation, identified by a number (its ASN). Cloudflare, AWS, and your home ISP are each an AS. Knowing the AS behind an address tells you who is really carrying the traffic, which is often more useful than a city name.

  • Base path: https://ws.latency.app/v1/geo/<ip>
  • Auth: none (public)

Request

bash
curl "https://ws.latency.app/v1/geo/1.1.1.1"

Response

json
{
  "ip": "1.1.1.1",
  "geo": {
    "city": "…",
    "country": "…",
    "latitude": 0,
    "longitude": 0
  },
  "ripe": {
    "asn": "13335",
    "asn_name": "CLOUDFLARENET"
  }
}
FieldMeaning
geoApproximate location (city, country, coordinates).
ripe.asnThe Autonomous System number operating the address.
ripe.asn_nameThe operator's name, e.g. CLOUDFLARENET.

TIP

Location data is approximate: it reflects where an address is registered or routed, which for cloud and CDN IPs is often a data-centre region, not a user. The ASN is the more reliable signal.

How we source it

Geolocation and ASN come from a local, regularly-updated database (no third-party call per request), behind a single internal seam, so the source can be upgraded without changing this response shape.

  • DNS: resolve a name to the IP you then geolocate
  • Inspect: geo plus hosting and status in one call
© 2026 Latency Labs LLC
latency

© 2026 Latency Labs LLC.