Network · data from 2026-11-12

AS22598 ALENCO - ALENCO COMMUNICATIONS, INC

Registry name: ALENCO - ALENCO COMMUNICATIONS, INC, US · not in PeeringDB

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

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

4Route objects not announced registered with origin AS22598, seen from no peer

Announced routes

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


67.212.29.0/24	Valid	Other IRR onlyRADB	673 100%	67
67.212.16.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
67.212.17.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
67.212.18.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
67.212.19.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
67.212.24.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
67.212.25.0/24	Valid	RIR databaseARIN	673 100%	67
67.212.28.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
108.160.176.0/24	Valid	RIR databaseARIN	673 100%	67
108.160.177.0/24	Valid	RIR databaseARIN	673 100%	67
108.160.178.0/24	Valid	RIR databaseARIN	673 100%	67
108.160.179.0/24	Valid	RIR databaseARIN	673 100%	67
108.160.180.0/24	Valid	RIR databaseARIN	673 100%	67
108.160.181.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
108.160.182.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
108.160.183.0/24	Valid	RIR databaseARIN	673 100%	67
108.160.186.0/24	Valid	RIR databaseARIN	673 100%	67
108.160.187.0/24	Valid	RIR databaseARIN	673 100%	67
154.7.132.0/24	Valid	RIR databaseARIN	673 100%	67
154.7.133.0/24	Valid	RIR databaseARIN	673 100%	67
154.7.134.0/24	Valid	RIR databaseARIN	673 100%	67
154.7.135.0/24	Valid	RIR databaseARIN	673 100%	67
38.147.144.0/24	Valid	RIR databaseARIN	672 100%	67
38.147.145.0/24	Valid	RIR databaseARIN	672 100%	67
38.147.146.0/24	Valid	RIR databaseARIN	672 100%	67
38.147.147.0/24	Valid	RIR databaseARIN	672 100%	67
67.212.26.0/24	Valid	RIR databaseARIN	672 100%	67
67.212.30.0/24	Valid	RIR databaseARIN, RADB	672 100%	67
67.212.31.0/24	Valid	RIR databaseARIN, RADB	672 100%	67
108.160.188.0/24	Valid	RIR databaseARIN	671 100%	68
108.160.189.0/24	Valid	RIR databaseARIN	671 100%	68
108.160.190.0/24	Valid	RIR databaseARIN	671 100%	68
108.160.191.0/24	Valid	RIR databaseARIN	671 100%	68
67.212.20.0/24	Valid	RIR databaseARIN, RADB	667 99%	68
67.212.27.0/24	Valid	RIR databaseARIN	667 99%	68
108.160.185.0/24	Valid	RIR databaseARIN	667 99%	68
67.212.21.0/24	Valid	RIR databaseARIN	665 99%	68
67.212.22.0/24	Valid	RIR databaseARIN	665 99%	68
67.212.23.0/24	Valid	RIR databaseARIN, RADB	665 99%	68
108.160.184.0/24	Valid	RIR databaseARIN	665 99%	68

AS-SET

AS22598 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 5 are in fix.csv.

Route object: RIR1
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	67.212.29.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

67.212.29.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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


38.147.144.0/22	ARIN	Valid
67.212.16.0/20	ARIN, RADB	Valid
108.160.176.0/20	ARIN, RADB	Valid
154.7.132.0/22	ARIN	Valid

38.147.144.0/22

ARIN

Valid

67.212.16.0/20

ARIN, RADB

Valid

108.160.176.0/20

ARIN, RADB

Valid

154.7.132.0/22

ARIN

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.