bgpreport

Network · data from 2026-11-12

AS41108 First Root UG AS41108

Registry name: FirstRoot-AS comtrance service GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41108, 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.206.76.0/23 No ROA RIR databaseRIPE 673 100% 66
195.88.172.0/23 No ROA RIR databaseRIPE 673 100% 66
195.128.168.0/23 No ROA RIR databaseRIPE 673 100% 66
195.242.78.0/23 No ROA RIR databaseRIPE 673 100% 66
195.254.136.0/23 No ROA RIR databaseRIPE 673 100% 66
2a0f:5707:ab26::/48 No ROA RIR databaseRIPE 635 100% 67
2a0c:9a40:8081::/48 Valid None 635 100% 67
91.228.52.0/23 Valid RIR databaseRIPE 673 100% 66
91.228.104.0/22 Valid RIR databaseRIPE 673 100% 66
91.229.229.0/24 Valid RIR databaseRIPE 673 100% 66
91.230.27.0/24 Valid RIR databaseRIPE 673 100% 66
193.3.157.0/24 Valid RIR databaseRIPE 673 100% 66
193.25.100.0/23 Valid RIR databaseRIPE 673 100% 66
195.88.44.0/23 Valid RIR databaseRIPE 673 100% 66
195.110.20.0/24 Valid RIR databaseRIPE 673 100% 66
195.110.21.0/24 Valid RIR databaseRIPE 673 100% 66
2001:67c:12a0::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS41108'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 18 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none91.206.76.0/23No ROA covers it. Add a ROA for AS41108, maxLength 23.673 of 673
ROA: none195.88.172.0/23No ROA covers it. Add a ROA for AS41108, maxLength 23.673 of 673
ROA: none195.128.168.0/23No ROA covers it. Add a ROA for AS41108, maxLength 23.673 of 673
ROA: none195.242.78.0/23No ROA covers it. Add a ROA for AS41108, maxLength 23.673 of 673
ROA: none195.254.136.0/23No ROA covers it. Add a ROA for AS41108, maxLength 23.673 of 673
ROA: none2a0f:5707:ab26::/48No ROA covers it. Add a ROA for AS41108, maxLength 48.635 of 636
Route object: none2a0c:9a40:8081::/48No route object for it. Add a route object with origin AS41108 in the RIR database for the space.635 of 636

Route objects not announced

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

91.228.52.0/24RIPEValid
91.228.53.0/24RIPEValid
91.228.104.0/24RIPEValid
91.228.106.0/24RIPEValid
91.228.107.0/24RIPEValid
91.229.248.0/24RIPEInvalid: origin
193.25.100.0/24RIPEValid
193.25.101.0/24RIPEValid
195.88.44.0/24RIPEValid
195.88.45.0/24RIPEValid
2001:67c:9bc::/48RIPEInvalid: origin

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.