Data source

Data from RIPE NCC, delivered clean.

2 datasets pulled from RIPE NCC's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.

  • 2 datasets
  • 1 industry
  • Real rows on request

What Datadory delivers from RIPE NCC

2
Internet Services & Infrastructure RIPE NCC service region: Europe · Current registrations with creation timestamp…

RIPE Database (WHOIS & Routing Registry)

Internet Services & Infrastructure Global — routing and registration coverage ac… · Historical routing and registration records r…

RIPEstat Data API

Pick a catch, see the rows.

Name any RIPE NCC dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.

Get a sample

API, files, or your warehouse. Daily, weekly, or hourly.

Straight answers about RIPE NCC data

How much sits behind the RIPE Database collection?

Millions of objects across roughly twenty-one RPSL object classes: inetnum and inet6num ranges, aut-num entries, route and route6 announcements, as-sets and route-sets, organisations, persons, roles, maintainers, domains and router records, with creation stamps reaching back to the early 1990s across 75 member countries.

Which fields come with each record?

Verified dictionaries cover range and netname, holder organisation, ISO country, status enums such as ASSIGNED PA, administrative, technical and abuse-contact handles, maintainer references, created and last-modified timestamps, import and export policy text, and prefix-plus-origin pairs - plus the documented answer envelope on the aggregation side.

Does the data include history?

By native depth and by accumulation. Registry objects carry created and last-modified stamps back to the early 1990s, routing-history and historical-registration lookups reach back years, and scheduled deliveries turn today's state into a longitudinal record your models can difference.

Are the routing policies measured or declared?

Declared. Route and aut-num objects state what a network intends to announce and accept, which makes them strong for screening and segmentation and a poor substitute for observation. Pair them with the aggregation side's routing-status families when the question is what actually happened.