bgpreport

Network · data from 2026-11-12

AS41437 KNAPP-AS KNAPP AG

Registry name: KNAPP-AS KNAPP AG, AT · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 80.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 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 AS41437, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41437, 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.
89.207.127.0/24 Valid Nonecovered by 89.207.120.0/21 673 100% 66
89.207.120.0/21 Valid RIR databaseRIPE 673 100% 66
89.207.120.0/24 Valid RIR databaseRIPE 673 100% 66
89.207.123.0/24 Valid RIR databaseRIPE 673 100% 67
89.207.124.0/24 Valid RIR databaseRIPE 673 100% 66
2001:a00::/32 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS41437 isn't in PeeringDB, where networks name their 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none89.207.127.0/24No route object for it. A route object for 89.207.120.0/21 with origin AS41437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41437 in the RIR database for the space.673 of 673

Route objects not announced

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