bgpreport

Network · data from 2026-11-12

AS55322 NPC-AS-VN - North Power Company

Registry name: NPC-AS-VN - North Power Company, VN · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS55322, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55322, 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.
116.212.32.0/19 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
116.212.32.0/20 No ROA Other IRR onlyNTTCOM 1 0%low visibility 1

AS-SET

AS55322 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 17 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none116.212.32.0/19No ROA covers it. Add a ROA for AS55322, maxLength 19.673 of 673
Route object: RIR116.212.32.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.212.32.0/20No ROA covers it. Add a ROA for AS55322, maxLength 20.1 of 673
Route object: RIR116.212.32.0/20Route object only in NTTCOM. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

116.212.32.0/21NTTCOMNo ROA
116.212.32.0/22NTTCOMNo ROA
116.212.36.0/22NTTCOMNo ROA
116.212.40.0/21NTTCOMNo ROA
116.212.40.0/22NTTCOMNo ROA
116.212.44.0/22NTTCOMNo ROA
116.212.48.0/20NTTCOMNo ROA
116.212.48.0/21NTTCOMNo ROA
116.212.48.0/22NTTCOMNo ROA
116.212.52.0/22NTTCOMNo ROA
116.212.56.0/21NTTCOMNo ROA
116.212.56.0/22NTTCOMNo ROA
116.212.60.0/22NTTCOMNo 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.