Network · data from 2026-11-12

AS18129 OKAYAMA NETWORK INC.

Registry name: ONI - OKAYAMA NETWORK INC., JP · PeeringDB

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

0Route objects not announced registered with origin AS18129, seen from no peer

Announced routes

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


27.109.96.0/21	Valid	Other IRR onlyJPIRR, NTTCOM, RADB	671 100%	67
119.47.96.0/20	Valid	Other IRR onlyJPIRR, NTTCOM, RADB	671 100%	67
202.70.224.0/19	Valid	Other IRR onlyJPIRR, NTTCOM, RADB	671 100%	67
202.238.16.0/20	Valid	Other IRR onlyJPIRR, RADB	671 100%	67
219.111.208.0/20	Valid	Other IRR onlyJPIRR, NTTCOM, RADB	671 100%	67
218.231.160.0/19	Valid	Other IRR onlyJPIRR, RADB	670 100%	67
103.154.6.0/23	Valid	Other IRR onlyJPIRR, RADB	669 99%	67
180.200.248.0/22	Valid	Other IRR onlyJPIRR, NTTCOM, RADB	669 99%	67

AS-SET

AS18129'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 8 are in fix.csv.

Route object: RIR8

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	27.109.96.0/21	Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	119.47.96.0/20	Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	202.70.224.0/19	Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	202.238.16.0/20	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	219.111.208.0/20	Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	218.231.160.0/19	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	103.154.6.0/23	Route object only in JPIRR, RADB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	180.200.248.0/22	Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.	669 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

27.109.96.0/21

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

671 of 673

Route object: RIR

119.47.96.0/20

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

671 of 673

Route object: RIR

202.70.224.0/19

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

671 of 673

Route object: RIR

202.238.16.0/20

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

671 of 673

Route object: RIR

219.111.208.0/20

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

671 of 673

Route object: RIR

218.231.160.0/19

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

670 of 673

Route object: RIR

103.154.6.0/23

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

669 of 673

Route object: RIR

180.200.248.0/22

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

669 of 673

Route objects not announced

Every route object with origin AS18129 is announced.

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.