Network · data from 2026-11-12

AS197000 RIPE NCC Authoritative DNS

Registry name: RIPE-NCC-AUTHDNS-AS Reseaux IP Europeens Network Coordination Centre (RIPE NCC), NL · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS197000, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS197000, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


193.0.8.0/24	Valid	RIR databaseRIPE	672 100%	71
193.0.8.0/23	Valid	RIR databaseRIPE	671 100%	69
193.0.9.0/24	Valid	RIR databaseRIPE	669 99%	71
2a13:27c0:30::/44	Valid	RIR databaseRIPE	636 100%	70
2a13:27c0:30::/48	Valid	RIR databaseRIPE	636 100%	71
2a13:27c0:3f::/48	Valid	RIR databaseRIPE	636 100%	71

AS-SET

PeeringDB's irr_as_set for AS197000: RS-AUTHDNS-AMS RS-AUTHDNS-LON RS-AUTHDNS-BMA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS197000 isn't in the set, or no route object for AS197000 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS197000 in it	Not covered
RS-AUTHDNS-AMS	A route-set, not an AS-SET; route-sets aren't expanded.
RS-AUTHDNS-LON	A route-set, not an AS-SET; route-sets aren't expanded.
RS-AUTHDNS-BMA	A route-set, not an AS-SET; route-sets aren't expanded.

Name

Database

ASNs

Sets

Route objects

AS197000 in it

Not covered

RS-AUTHDNS-AMS

A route-set, not an AS-SET; route-sets aren't expanded.

RS-AUTHDNS-LON

A route-set, not an AS-SET; route-sets aren't expanded.

RS-AUTHDNS-BMA

A route-set, not an AS-SET; route-sets aren't expanded.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS197000 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.