Network · data from 2026-11-12

AS56368 Nicola von Thadden

Registry name: NICODUCK Nicola von Thadden, DE · PeeringDB

4IPv4 routes 75.0% RPKI valid · 75.0% with a route object

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

1RPKI invalid 0 origin · 1 maxLength

0No ROA 1 with no route object for this origin

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

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

Announced routes

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


91.198.196.66/32	Invalid: maxLength	Nonecovered by 91.198.196.0/24	2 0%low visibility	6
91.198.172.0/24	Valid	RIR databaseRIPE	673 100%	66
91.198.185.0/24	Valid	RIR databaseRIPE	673 100%	66
91.198.196.0/24	Valid	RIR databaseRIPE	673 100%	66
2a0f:8840::/29	Valid	RIR databaseRIPE	633 100%	67
2a0f:8840::/30	Valid	RIR databaseRIPE	633 100%	67

91.198.196.66/32

Invalid: maxLength

Nonecovered by 91.198.196.0/24

2 0%low visibility

91.198.172.0/24

Valid

RIR databaseRIPE

673 100%

91.198.185.0/24

Valid

RIR databaseRIPE

673 100%

91.198.196.0/24

Valid

RIR databaseRIPE

673 100%

2a0f:8840::/29

Valid

RIR databaseRIPE

633 100%

2a0f:8840::/30

Valid

RIR databaseRIPE

633 100%

AS-SET

PeeringDB's irr_as_set for AS56368: AS-VONTHADDEN-IT. 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 (AS56368 isn't in the set, or no route object for AS56368 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	AS56368 in it	Not covered
AS-VONTHADDEN-IT	RIPE	1	1	5	Yes	1

Name

Database

ASNs

Sets

Route objects

AS56368 in it

Not covered

AS-VONTHADDEN-IT

RIPE

Yes

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 2 are in fix.csv.

ROA: maxLength1
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	91.198.196.66/32	ROA 91.198.196.0/24 AS56368 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.198.196.66/32.	2 of 673
Route object: none	91.198.196.66/32	No route object for it. A route object for 91.198.196.0/24 with origin AS56368 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56368 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

91.198.196.66/32

ROA 91.198.196.0/24 AS56368 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.198.196.66/32.

2 of 673

Route object: none

91.198.196.66/32

No route object for it. A route object for 91.198.196.0/24 with origin AS56368 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56368 in the RIR database for the space.

2 of 673

Route objects not announced

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