Network · data from 2026-11-12

AS200461 v6Node

Registry name: V6NODE-AS Ian David Klemm, DE · PeeringDB

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

3IPv6 routes 0.0% RPKI valid · 66.7% with a route object

0RPKI invalid 0 origin · 0 maxLength

3No ROA 1 with no route object for this origin

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

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

Announced routes

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


2a09:bfc7:2000::/35	No ROA	Nonecovered by 2a09:bfc7::/32	635 100%	67
2a09:bfc7::/32	No ROA	RIR databaseRIPE	635 100%	67
2a0e:fd45:2ec0::/48	No ROA	RIR databaseRIPE	635 100%	67
89.106.80.0/24	Valid	RIR databaseRIPE	673 100%	67
178.18.148.0/24	Valid	RIR databaseRIPE	673 100%	67
185.23.5.0/24	Valid	RIR databaseRIPE	673 100%	67
77.90.44.0/24	Valid	RIR databaseRIPE	672 100%	67
194.110.175.0/24	Valid	RIR databaseRIPE	671 100%	67
178.251.228.0/24	Valid	RIR databaseRIPE	667 99%	67

AS-SET

AS200461's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.

ROA: none3
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2a09:bfc7:2000::/35	No ROA covers it. Add a ROA for AS200461, maxLength 35.	635 of 636
Route object: none	2a09:bfc7:2000::/35	No route object for it. A route object for 2a09:bfc7::/32 with origin AS200461 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200461 in the RIR database for the space.	635 of 636
ROA: none	2a09:bfc7::/32	No ROA covers it. Add a ROA for AS200461, maxLength 32.	635 of 636
ROA: none	2a0e:fd45:2ec0::/48	No ROA covers it. Add a ROA for AS200461, maxLength 48.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2a09:bfc7:2000::/35

No ROA covers it. Add a ROA for AS200461, maxLength 35.

635 of 636

Route object: none

2a09:bfc7:2000::/35

No route object for it. A route object for 2a09:bfc7::/32 with origin AS200461 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200461 in the RIR database for the space.

635 of 636

ROA: none

2a09:bfc7::/32

No ROA covers it. Add a ROA for AS200461, maxLength 32.

635 of 636

ROA: none

2a0e:fd45:2ec0::/48

No ROA covers it. Add a ROA for AS200461, maxLength 48.

635 of 636

Route objects not announced

Every route object with origin AS200461 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.