Geofeed Service

Self-Published Geolocation Data

Authoritative geographic information for our IP address blocks, in the RFC 8805 format and linked from our ARIN registration records.

What is a Geofeed?

A geofeed is a plain CSV file in which the holder of an IP address block states where that block is actually used. Geolocation databases infer location from latency, routing and user reports, which gets prefixes that move between sites badly wrong. Publishing a geofeed replaces that guesswork with a first-party answer.

Why it matters

  • Correct country and city for our prefixes
  • Fewer wrong-region redirects and content blocks
  • Updates take effect without waiting for re-inference

Standards

  • RFC 8805 — the geofeed format itself
  • RFC 9632 — finding and authenticating geofeeds
  • ISO 3166-1 and 3166-2 country and region codes

Loading network location data…

How to Use Our Geofeed

File Format

Comma-separated, one prefix per line. Lines beginning with # are comments, and empty fields are permitted where a value is not applicable.

# Format: network,country,region,city,postal# Example: 95.128.158.0/24,US,US-CA,San Jose,95120

Discovery and Verification

  • Whois / RDAP reference

    Our ARIN records carry a Geofeed comment pointing at this URL, so the feed can be found from the registry rather than trusted because a web page said so.

  • Direct HTTPS fetch

    Retrieve the file over TLS; no authentication and no rate limit for reasonable use.

  • Cross-check the holder

    Confirm each prefix is registered to HashTable, Inc. (ARIN Org ID HASHT) before importing it. A geofeed is only authoritative for space its publisher actually holds.

Resources & Documentation

Download Geofeed

The current file, containing every network location mapping we publish.

Download geofeed.txt

RFC Standards

The specifications this feed is written against.

Consumer Guidance

Cache appropriately

Honour the HTTP caching headers. Checking once an hour is more than enough; the file changes rarely.

Validate before importing

Check the CSV parses and that every prefix is well-formed before it reaches your production database.

Re-read on change

Prefixes move between sites. Treat this file as the current answer, not a one-off import.