Network · data from 2026-11-12

AS210197 RESITVE-AS ROK TAJZEL

Registry name: RESITVE-AS ROK TAJZEL, SI · not in PeeringDB

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

1IPv6 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 AS210197, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210197, 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.


81.30.101.0/24	Valid	RIR databaseRIPE	671 100%	68
85.204.38.0/24	Valid	RIR databaseRIPE	671 100%	68
2a13:f400::/29	Valid	RIR databaseRIPE	635 100%	69

AS-SET

AS210197 isn't in PeeringDB, where networks name their AS-SET.

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 AS210197 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.