bgpreport

Network · data from 2026-11-12

AS50964 Komm-ONE-AS civillent GmbH

Registry name: Komm-ONE-AS civillent GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50964, 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.205.76.0/24 Invalid: maxLength Nonecovered by 91.205.76.0/22 76 11% 34
91.205.78.0/24 Invalid: maxLength Nonecovered by 91.205.76.0/22 76 11% 34
91.205.79.0/24 Invalid: maxLength Nonecovered by 91.205.76.0/22 76 11% 34
91.205.76.0/22 Valid RIR databaseRIPE 673 100% 66
194.0.92.0/24 Valid RIR databaseRIPE 673 100% 66
194.0.93.0/24 Valid RIR databaseRIPE 673 100% 66
194.0.94.0/24 Valid RIR databaseRIPE 673 100% 66
194.0.95.0/24 Valid RIR databaseRIPE 673 100% 66
194.59.36.0/22 Valid RIR databaseRIPE 673 100% 66
194.59.36.0/24 Valid RIR databaseRIPE 673 100% 66
194.59.37.0/24 Valid RIR databaseRIPE 673 100% 66
194.59.38.0/24 Valid RIR databaseRIPE 673 100% 66
194.59.39.0/24 Valid RIR databaseRIPE 673 100% 66
194.76.38.0/23 Valid RIR databaseRIPE 673 100% 66
194.127.180.0/24 Valid RIR databaseRIPE 673 100% 66
195.189.92.0/24 Valid RIR databaseRIPE 673 100% 66
195.189.93.0/24 Valid RIR databaseRIPE 673 100% 66
195.189.94.0/24 Valid RIR databaseRIPE 673 100% 66
195.189.95.0/24 Valid RIR databaseRIPE 673 100% 66
194.76.38.0/24 Valid RIR databaseRIPE 672 100% 66
194.76.39.0/24 Valid RIR databaseRIPE 672 100% 66
2001:67c:2da8::/48 Valid RIR databaseRIPE 635 100% 67
2001:67c:2dac::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • ROA: maxLength3
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength91.205.76.0/24ROA 91.205.76.0/22 AS50964 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 91.205.76.0/24.76 of 673
Route object: none91.205.76.0/24No route object for it. A route object for 91.205.76.0/22 with origin AS50964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50964 in the RIR database for the space.76 of 673
ROA: maxLength91.205.78.0/24ROA 91.205.76.0/22 AS50964 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 91.205.78.0/24.76 of 673
Route object: none91.205.78.0/24No route object for it. A route object for 91.205.76.0/22 with origin AS50964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50964 in the RIR database for the space.76 of 673
ROA: maxLength91.205.79.0/24ROA 91.205.76.0/22 AS50964 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 91.205.79.0/24.76 of 673
Route object: none91.205.79.0/24No route object for it. A route object for 91.205.76.0/22 with origin AS50964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50964 in the RIR database for the space.76 of 673

Route objects not announced

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

194.0.92.0/22RIPEValid
195.189.92.0/22RIPEValid

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.