Network · data from 2026-11-12

AS14499 ALORICA - ALORICA INC

Registry name: ALORICA - ALORICA INC, US · not in PeeringDB

31IPv4 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

3Route objects not announced registered with origin AS14499, seen from no peer

Announced routes

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


208.90.64.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
122.55.92.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	69
142.192.0.0/16	Valid	RIR databaseARIN	673 100%	67
142.192.3.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.10.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.12.0/23	Valid	RIR databaseARIN	673 100%	67
142.192.200.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.201.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.202.0/24	Valid	RIR databaseARIN	673 100%	69
142.192.204.0/23	Valid	RIR databaseARIN	673 100%	67
142.192.204.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.216.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.217.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.218.0/23	Valid	RIR databaseARIN	673 100%	67
142.192.218.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.219.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.224.0/23	Valid	RIR databaseARIN	673 100%	67
142.192.224.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.225.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.227.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.240.0/24	Valid	RIR databaseARIN, NTTCOM, RADB	673 100%	69
142.192.248.0/24	Valid	RIR databaseARIN	673 100%	67
142.192.250.0/23	Valid	RIR databaseARIN	673 100%	67
170.8.0.0/16	Valid	RIR databaseARIN	673 100%	67
222.127.107.0/24	Valid	RIR databaseAPNIC	673 100%	69
222.127.141.0/24	Valid	RIR databaseAPNIC	673 100%	69
208.94.8.0/23	Valid	RIR databaseARIN	672 100%	67
208.94.12.0/23	Valid	RIR databaseARIN	672 100%	67
27.110.129.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	69
142.192.242.0/24	Valid	RIR databaseARIN, NTTCOM, RADB	671 100%	69
142.192.203.0/24	Valid	RIR databaseARIN, NTTCOM, RADB	670 100%	69

AS-SET

AS14499 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 4 are in fix.csv.

Route object: RIR1
Route object: not announced3

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

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

208.90.64.0/24

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

673 of 673

Route objects not announced

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


142.192.12.0/24	ARIN	Valid
142.192.250.0/24	ARIN	Valid
208.90.64.0/22	ARIN	Valid

142.192.12.0/24

ARIN

Valid

142.192.250.0/24

ARIN

Valid

208.90.64.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.