Network · data from 2026-11-12

AS35132 Enivest

Registry name: Enivest-AS Enivest AS, NO · PeeringDB

15IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 50.0% RPKI valid · 50.0% with a route object

1RPKI invalid 1 origin · 0 maxLength

0No ROA 1 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS35132, seen from no peer

Announced routes

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


2a0a:2200::/29	Invalid: origin	Other origin only	1 0%low visibility	1
37.32.48.0/21	Valid	RIR databaseRIPE	673 100%	67
62.50.160.0/19	Valid	RIR databaseRIPE	673 100%	67
89.20.224.0/19	Valid	RIR databaseRIPE	673 100%	67
93.89.32.0/20	Valid	RIR databaseRIPE	673 100%	67
95.111.160.0/19	Valid	RIR databaseRIPE	673 100%	67
109.122.48.0/21	Valid	RIR databaseRIPE	673 100%	67
217.149.112.0/20	Valid	RIR databaseRIPE	673 100%	67
109.235.100.0/22	Valid	RIR databaseRIPE	671 100%	67
185.141.156.0/22	Valid	RIR databaseRIPE	671 100%	67
185.186.132.0/22	Valid	RIR databaseRIPE	671 100%	67
185.197.220.0/22	Valid	RIR databaseRIPE	671 100%	67
185.214.16.0/22	Valid	RIR databaseRIPE	671 100%	67
185.243.176.0/22	Valid	RIR databaseRIPE	671 100%	67
188.119.80.0/22	Valid	RIR databaseRIPE	671 100%	67
178.249.120.0/21	Valid	RIR databaseRIPE	670 100%	67
2a02:1660::/29	Valid	RIR databaseRIPE	635 100%	67

2a0a:2200::/29

Invalid: origin

Other origin only

1 0%low visibility

37.32.48.0/21

Valid

RIR databaseRIPE

673 100%

62.50.160.0/19

Valid

RIR databaseRIPE

673 100%

89.20.224.0/19

Valid

RIR databaseRIPE

673 100%

93.89.32.0/20

Valid

RIR databaseRIPE

673 100%

95.111.160.0/19

Valid

RIR databaseRIPE

673 100%

109.122.48.0/21

Valid

RIR databaseRIPE

673 100%

217.149.112.0/20

Valid

RIR databaseRIPE

673 100%

109.235.100.0/22

Valid

RIR databaseRIPE

671 100%

185.141.156.0/22

Valid

RIR databaseRIPE

671 100%

185.186.132.0/22

Valid

RIR databaseRIPE

671 100%

185.197.220.0/22

Valid

RIR databaseRIPE

671 100%

185.214.16.0/22

Valid

RIR databaseRIPE

671 100%

185.243.176.0/22

Valid

RIR databaseRIPE

671 100%

188.119.80.0/22

Valid

RIR databaseRIPE

671 100%

178.249.120.0/21

Valid

RIR databaseRIPE

670 100%

2a02:1660::/29

Valid

RIR databaseRIPE

635 100%

AS-SET

AS35132'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 3 are in fix.csv.

ROA: origin1
Route object: none1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	2a0a:2200::/29	ROAs covering it name AS8542, not AS35132. If AS35132 should announce it, add a ROA for AS35132.	1 of 636
Route object: none	2a0a:2200::/29	Route objects for it name AS8542. Add a route object with origin AS35132 in the RIR database for the space.	1 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

2a0a:2200::/29

ROAs covering it name AS8542, not AS35132. If AS35132 should announce it, add a ROA for AS35132.

1 of 636

Route object: none

2a0a:2200::/29

Route objects for it name AS8542. Add a route object with origin AS35132 in the RIR database for the space.

1 of 636

Route objects not announced

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


2a02:1660::/32	RIPE	Valid

2a02:1660::/32

RIPE

Valid

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.