Network · data from 2026-11-12

AS203412 kues-data KUES DATA GmbH

Registry name: kues-data KUES DATA GmbH, DE · not in PeeringDB

4IPv4 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 AS203412, seen from no peer

Announced routes

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


79.142.36.0/24	Valid	RIR databaseRIPE	673 100%	66
79.142.44.0/22	Valid	RIR databaseRIPE	673 100%	66
185.125.172.0/22	Valid	RIR databaseRIPE	673 100%	66
194.55.162.0/24	Valid	RIR databaseRIPE	673 100%	66
2a07:f00::/29	Valid	RIR databaseRIPE	634 100%	69

AS-SET

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