Operator geofeeds
Registries and geofeeds. What Operator geofeeds is, on what terms it is used, which fields of the IP answer it feeds, how big it is today and when it was last synced.
| Kind | Registries and geofeeds |
|---|---|
| Publisher | https://www.rfc-editor.org/rfc/rfc8805 |
| Terms | Each geofeed is published by its network operator; the finder that discovers them is BSD-licensed. |
| Refresh | weekly |
| Size today | 468,189 IPv4 ranges and 217,469 IPv6 ranges compiled from the feed. |
| Last synced | 2026-09-08 |
| Answers | location_source, location_confidence, city |
What it is
Every RFC 8805 geofeed the registries point at, discovered and validated weekly across the five registries with the open geofeed-finder tool. A geofeed is the operator's own statement of where a prefix is used, so it outranks the database on country and city and grades location_confidence high.
What it answers
In the IP response this source feeds location_source, location_confidence, city. Every answer names the datasets it read in its sources block with the date each was synced, so the figure on this page and the one in an answer are the same figure.
curl https://spaw.co/api/v1/ip \
-H "Authorization: Bearer $SPAW_KEY" \
-H "Content-Type: application/json" \
-d '{"ip": "203.0.113.9"}'How to read this page
A source names a network or an operator, never a person. An address inside one of these ranges tells you what the connection is — a cloud instance, a VPN exit, a gateway, a listed host — and nothing about who is behind it.
More sources in registries and geofeeds
counts and dates read from the installed feed · checked 2026-09-13
More free tools
All free toolsNeed this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.