bgpreport

Network · data from 2026-11-12

AS41132 sol-as Applied Technologies Co.

Registry name: sol-as Applied Technologies Co., SA · not in PeeringDB

2IPv4 routes 100.0% RPKI valid · 50.0% with a route object
0IPv6 routes
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
11Route objects not announced registered with origin AS41132, seen from no peer

Announced routes

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

217.145.240.0/20 Valid Other origin only 672 100% 67
212.33.160.0/19 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS41132 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 12 are in fix.csv.

  • Route object: none1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: none217.145.240.0/20Route objects for it name AS31416. Add a route object with origin AS41132 in the RIR database for the space.672 of 673

Route objects not announced

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

85.237.128.0/19RADB, RIPEValid
85.237.128.0/21RIPEInvalid: maxLength
85.237.136.0/21RIPEInvalid: maxLength
85.237.144.0/21RIPEInvalid: maxLength
85.237.152.0/21RIPEInvalid: maxLength
212.33.160.0/21RIPEInvalid: maxLength
212.33.168.0/21RIPEInvalid: maxLength
212.33.176.0/21RIPEInvalid: maxLength
212.33.184.0/21RIPEInvalid: maxLength
212.33.186.0/24RIPEInvalid: maxLength
212.33.187.0/24RIPEInvalid: maxLength

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.