bgpreport

Network · data from 2026-11-12

AS1821 NETWORKINV-AS1 - Network Innovations Inc.

Registry name: NETWORKINV-AS1 - Network Innovations Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1821, 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.
162.255.204.0/24 No ROA Nonecovered by 162.255.204.0/22 673 100% 67
162.255.205.0/24 No ROA Nonecovered by 162.255.204.0/22 673 100% 67
162.255.206.0/24 No ROA Nonecovered by 162.255.204.0/22 673 100% 67
8.22.179.0/24 No ROA Other IRR onlyALTDB 673 100% 67
8.34.42.0/24 No ROA Other IRR onlyALTDB 673 100% 67
162.251.77.0/24 No ROA RIR databaseARIN 673 100% 66
103.212.112.0/24 Valid RIR databaseAPNIC 673 100% 66
103.212.114.0/24 Valid RIR databaseAPNIC 673 100% 66
103.212.115.0/24 Valid RIR databaseAPNIC 668 99% 67

AS-SET

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

  • ROA: none6
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none162.255.204.0/24No ROA covers it. Add a ROA for AS1821, maxLength 24.673 of 673
Route object: none162.255.204.0/24No route object for it. A route object for 162.255.204.0/22 with origin AS1821 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1821 in the RIR database for the space.673 of 673
ROA: none162.255.205.0/24No ROA covers it. Add a ROA for AS1821, maxLength 24.673 of 673
Route object: none162.255.205.0/24No route object for it. A route object for 162.255.204.0/22 with origin AS1821 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1821 in the RIR database for the space.673 of 673
ROA: none162.255.206.0/24No ROA covers it. Add a ROA for AS1821, maxLength 24.673 of 673
Route object: none162.255.206.0/24No route object for it. A route object for 162.255.204.0/22 with origin AS1821 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1821 in the RIR database for the space.673 of 673
ROA: none8.22.179.0/24No ROA covers it. Add a ROA for AS1821, maxLength 24.673 of 673
Route object: RIR8.22.179.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none8.34.42.0/24No ROA covers it. Add a ROA for AS1821, maxLength 24.673 of 673
Route object: RIR8.34.42.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none162.251.77.0/24No ROA covers it. Add a ROA for AS1821, maxLength 24.673 of 673

Route objects not announced

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

162.255.204.0/22ALTDBNo ROA

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.