bgpreport

Network · data from 2026-11-12

AS41913 Computerline Group

Registry name: COMPUTERLINE Computerline GmbH, CH · PeeringDB

14IPv4 routes 92.9% RPKI valid · 85.7% with a route object
3IPv6 routes 33.3% RPKI valid · 66.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS41913, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41913, 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.
156.67.38.0/23 No ROA RIR databaseRIPE 673 100% 67
2a12:8b40:10::/47 No ROA RIR databaseRIPE 636 100% 69
2a12:8b40:20::/47 No ROA RIR databaseRIPE 636 100% 69
185.172.198.0/24 Valid Nonecovered by 185.172.198.0/23 672 100% 67
185.172.199.0/24 Valid Nonecovered by 185.172.198.0/23 672 100% 67
2a01:278::/32 Valid Nonecovered by 2a01:278::/29 636 100% 69
89.36.170.0/23 Valid RIR databaseRIPE 673 100% 67
89.36.170.0/24 Valid RIR databaseRIPE 673 100% 67
91.103.152.0/23 Valid RIR databaseRIPE 673 100% 67
91.103.154.0/23 Valid RIR databaseRIPE 673 100% 67
91.135.64.0/20 Valid RIR databaseRIPE 673 100% 67
185.20.208.0/24 Valid RIR databaseRIPE 673 100% 67
185.20.209.0/24 Valid RIR databaseRIPE 673 100% 67
185.20.210.0/24 Valid RIR databaseRIPE 673 100% 67
185.20.211.0/24 Valid RIR databaseRIPE 673 100% 67
89.36.171.0/24 Valid RIR databaseRIPE 672 100% 67
136.143.168.0/23 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS41913's PeeringDB record names no 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 14 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none156.67.38.0/23No ROA covers it. Add a ROA for AS41913, maxLength 23.673 of 673
ROA: none2a12:8b40:10::/47No ROA covers it. Add a ROA for AS41913, maxLength 47.636 of 636
ROA: none2a12:8b40:20::/47No ROA covers it. Add a ROA for AS41913, maxLength 47.636 of 636
Route object: none185.172.198.0/24No route object for it. A route object for 185.172.198.0/23 with origin AS41913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41913 in the RIR database for the space.672 of 673
Route object: none185.172.199.0/24No route object for it. A route object for 185.172.198.0/23 with origin AS41913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41913 in the RIR database for the space.672 of 673
Route object: none2a01:278::/32No route object for it. A route object for 2a01:278::/29 with origin AS41913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41913 in the RIR database for the space.636 of 636

Route objects not announced

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

91.208.227.0/24RIPEValid
156.67.38.0/24RIPENo ROA
156.67.39.0/24RIPENo ROA
185.20.208.0/22RIPEValid
185.172.198.0/23RIPEValid
185.230.212.0/23RIPEInvalid: origin
185.230.214.0/23RIPEInvalid: origin
2a01:278::/29RIPENo ROA

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.