bgpreport

Network · data from 2026-11-12

AS8561 KNIPPWORLDWIDE Knipp Medien und Kommunikation GmbH

Registry name: KNIPPWORLDWIDE Knipp Medien und Kommunikation GmbH, DE · not in PeeringDB

20IPv4 routes 100.0% RPKI valid · 85.0% with a route object
20IPv6 routes 100.0% RPKI valid · 85.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
58Route objects not announced registered with origin AS8561, seen from no peer

Announced routes

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

195.253.114.0/23 Valid Nonecovered by 195.253.96.0/19 673 100% 67
195.253.116.0/23 Valid Nonecovered by 195.253.96.0/19 673 100% 66
195.253.118.0/23 Valid Nonecovered by 195.253.96.0/19 673 100% 67
2a01:5b0:34::/47 Valid Nonecovered by 2a01:5b0:20::/43 636 100% 68
2a01:5b0:36::/47 Valid Nonecovered by 2a01:5b0:20::/43 635 100% 68
2a01:5b0:32::/47 Valid Nonecovered by 2a01:5b0:20::/43 634 100% 67
185.95.96.0/23 Valid Other IRR onlyRADB 261 39% 58
2a00:1c3e:96::/47 Valid Other IRR onlyRADB 194 31% 53
195.253.96.0/24 Valid RIR databaseRIPE 673 100% 67
195.253.102.0/24 Valid RIR databaseRIPE 673 100% 67
195.253.108.0/24 Valid RIR databaseRIPE 673 100% 66
195.253.64.0/24 Valid RIR databaseRIPE 672 100% 67
195.253.94.0/23 Valid RIR databaseRIPE 672 100% 67
195.253.97.0/24 Valid RIR databaseRIPE 672 100% 67
195.253.111.0/24 Valid RIR databaseRIPE 672 100% 66
195.253.98.0/24 Valid RIR databaseRIPE 671 100% 67
195.253.99.0/24 Valid RIR databaseRIPE 671 100% 67
195.253.120.0/24 Valid RIR databaseRIPE 671 100% 66
195.253.92.0/23 Valid RIR databaseRIPE 670 100% 66
195.253.100.0/24 Valid RIR databaseRIPE 670 100% 67
195.253.109.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
2a01:5b0:22::/48 Valid RIR databaseRIPE 636 100% 68
2a01:5b0:23::/48 Valid RIR databaseRIPE 636 100% 68
2a01:5b0:26::/48 Valid RIR databaseRIPE 636 100% 67
2a01:5b0:20::/48 Valid RIR databaseRIPE 635 100% 68
2a01:5b0:21::/48 Valid RIR databaseRIPE 635 100% 67
2a01:5b0:2c::/48 Valid RIR databaseRIPE 635 100% 67
2a01:5b0:2d::/48 Valid RIR databaseRADB, RIPE 635 100% 67
2a01:5b0:2f::/48 Valid RIR databaseRIPE 635 100% 67
2a01:5b0:16::/47 Valid RIR databaseRIPE 634 100% 67
2a01:5b0:24::/48 Valid RIR databaseRIPE 634 100% 67
2a01:5b0:4::/48 Valid RIR databaseRIPE 633 100% 70
2a01:5b0:38::/48 Valid RIR databaseRIPE 633 100% 69
2a01:5b0:14::/47 Valid RIR databaseRIPE 632 99% 68
185.95.98.0/23 Valid RIR databaseRIPE 541 80% 64
2a00:1c3e:98::/47 Valid RIR databaseRIPE 493 78% 66
195.253.88.0/23 Valid RIR databaseRIPE 415 62% 64
2a01:5b0:10::/47 Valid RIR databaseRIPE 254 40% 59
195.253.90.0/23 Valid RIR databaseRIPE 250 37% 58
2a01:5b0:12::/47 Valid RIR databaseRIPE 180 28% 55

AS-SET

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

  • Route object: none6
  • Route object: RIR2
  • Route object: not announced58
ChangePrefix or setDetailFull-table peers
Route object: none195.253.114.0/23No route object for it. A route object for 195.253.96.0/19 with origin AS8561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8561 in the RIR database for the space.673 of 673
Route object: none195.253.116.0/23No route object for it. A route object for 195.253.96.0/19 with origin AS8561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8561 in the RIR database for the space.673 of 673
Route object: none195.253.118.0/23No route object for it. A route object for 195.253.96.0/19 with origin AS8561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8561 in the RIR database for the space.673 of 673
Route object: none2a01:5b0:34::/47No route object for it. A route object for 2a01:5b0:20::/43 with origin AS8561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8561 in the RIR database for the space.636 of 636
Route object: none2a01:5b0:36::/47No route object for it. A route object for 2a01:5b0:20::/43 with origin AS8561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8561 in the RIR database for the space.635 of 636
Route object: none2a01:5b0:32::/47No route object for it. A route object for 2a01:5b0:20::/43 with origin AS8561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8561 in the RIR database for the space.634 of 636
Route object: RIR185.95.96.0/23Route object only in RADB. Add it in the RIR database for the space.261 of 673
Route object: RIR2a00:1c3e:96::/47Route object only in RADB. Add it in the RIR database for the space.194 of 636

Route objects not announced

Route objects with origin AS8561 whose prefix no peer sees AS8561 announce. Many are kept on purpose (backup routes, space announced only in some places).

194.77.54.0/23RIPEValid
195.253.66.0/24RIPEValid
195.253.72.0/24RIPEInvalid: origin
195.253.74.0/24RIPEValid
195.253.88.0/24RIPEValid
195.253.89.0/24RIPEValid
195.253.91.0/24RIPEValid
195.253.92.0/24RIPEValid
195.253.93.0/24RIPEValid
195.253.94.0/24RIPEValid
195.253.95.0/24RIPEValid
195.253.96.0/19RADBValid
195.253.101.0/24RIPEValid
195.253.104.0/24RIPEValid
195.253.110.0/24RIPEValid
195.253.112.0/24RIPEValid
195.253.113.0/24RIPEValid
195.253.114.0/24RIPEValid
195.253.115.0/24RIPEValid
195.253.116.0/24RIPEValid
195.253.117.0/24RIPEValid
195.253.118.0/24RIPEValid
195.253.119.0/24RIPEValid
195.253.121.0/24RIPEValid
195.253.122.0/24RIPEValid
195.253.123.0/24RIPEValid
195.253.124.0/24RIPEValid
195.253.125.0/24RIPEValid
195.253.127.0/24RIPEValid
2a01:5b0:3::/48RIPEValid
2a01:5b0:6::/48RIPEValid
2a01:5b0:c::/48RIPEInvalid: origin
2a01:5b0:d::/48RIPEValid
2a01:5b0:10::/48RIPEValid
2a01:5b0:11::/48RIPEValid
2a01:5b0:12::/48RIPEValid
2a01:5b0:13::/48RIPEValid
2a01:5b0:14::/48RIPEValid
2a01:5b0:15::/48RIPEValid
2a01:5b0:16::/48RIPEValid
2a01:5b0:20::/43RADBValid
2a01:5b0:25::/48RIPEValid
2a01:5b0:28::/48RIPEValid
2a01:5b0:30::/48RIPEValid
2a01:5b0:31::/48RIPEValid
2a01:5b0:32::/48RIPEValid
2a01:5b0:33::/48RIPEValid
2a01:5b0:34::/48RIPEValid
2a01:5b0:35::/48RIPEValid
2a01:5b0:36::/48RIPEValid
2a01:5b0:37::/48RIPEValid
2a01:5b0:39::/48RIPEValid
2a01:5b0:3a::/48RIPEValid
2a01:5b0:3b::/48RIPEValid
2a01:5b0:3c::/48RIPEValid
2a01:5b0:3d::/48RIPEValid
2a01:5b0:3e::/48RIPEValid
2a01:5b0:3f::/48RIPEValid

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.