bgpreport

Network · data from 2026-11-12

AS59118 NRI SecureTechnologies AS59118

Registry name: FNC-O2 - NRI SecureTechnologies, Ltd., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59118, 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.
133.250.0.0/21 No ROA Other IRR onlyJPIRR 672 100% 67
192.50.138.0/23 No ROA Other IRR onlyJPIRR 672 100% 67
192.50.140.0/22 No ROA Other IRR onlyJPIRR 672 100% 67
192.50.144.0/22 No ROA Other IRR onlyJPIRR 672 100% 67

AS-SET

AS59118'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 18 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none133.250.0.0/21No ROA covers it. Add a ROA for AS59118, maxLength 21.672 of 673
Route object: RIR133.250.0.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none192.50.138.0/23No ROA covers it. Add a ROA for AS59118, maxLength 23.672 of 673
Route object: RIR192.50.138.0/23Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none192.50.140.0/22No ROA covers it. Add a ROA for AS59118, maxLength 22.672 of 673
Route object: RIR192.50.140.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none192.50.144.0/22No ROA covers it. Add a ROA for AS59118, maxLength 22.672 of 673
Route object: RIR192.50.144.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

192.50.138.0/24JPIRRNo ROA
192.50.139.0/24JPIRRNo ROA
192.50.140.0/24JPIRRNo ROA
192.50.141.0/24JPIRRNo ROA
192.50.142.0/24JPIRRNo ROA
192.50.143.0/24JPIRRNo ROA
192.50.144.0/24JPIRRNo ROA
192.50.145.0/24JPIRRNo ROA
192.50.146.0/24JPIRRNo ROA
192.50.147.0/24JPIRRNo 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.