Network · data from 2026-11-12

AS59122 Ranger-Systems Co., Ltd.

Registry name: R-SYS - Ranger-Systems Co., Ltd., JP · PeeringDB

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

1Low visibility seen by under 10% of full-table peers

8Route objects not announced registered with origin AS59122, seen from no peer

Announced routes

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


103.215.56.0/22	Valid	Other IRR onlyJPIRR, NTTCOM	669 99%	67
219.100.232.0/22	Valid	Other IRR onlyJPIRR, NTTCOM	669 99%	67
219.100.233.0/24	Valid	Other IRR onlyJPIRR	2 0%low visibility	3

103.215.56.0/22

Valid

Other IRR onlyJPIRR, NTTCOM

669 99%

219.100.232.0/22

Valid

Other IRR onlyJPIRR, NTTCOM

669 99%

219.100.233.0/24

Valid

Other IRR onlyJPIRR

2 0%low visibility

AS-SET

AS59122'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 11 are in fix.csv.

Route object: RIR3
Route object: not announced8

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	103.215.56.0/22	Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.	669 of 673
Route object: RIR	219.100.232.0/22	Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.	669 of 673
Route object: RIR	219.100.233.0/24	Route object only in JPIRR. Add it in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

103.215.56.0/22

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

669 of 673

Route object: RIR

219.100.232.0/22

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

669 of 673

Route object: RIR

219.100.233.0/24

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

2 of 673

Route objects not announced

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


103.215.56.0/24	JPIRR	Valid
103.215.57.0/24	JPIRR	Valid
103.215.58.0/24	JPIRR, NTTCOM	Valid
103.215.59.0/24	JPIRR	Valid
219.100.232.0/24	JPIRR	Valid
219.100.234.0/24	JPIRR	Valid
219.100.235.0/24	JPIRR, NTTCOM	Valid
2401:a1c0::/32	JPIRR	No ROA

103.215.56.0/24

JPIRR

Valid

103.215.57.0/24

JPIRR

Valid

103.215.58.0/24

JPIRR, NTTCOM

Valid

103.215.59.0/24

JPIRR

Valid

219.100.232.0/24

JPIRR

Valid

219.100.234.0/24

JPIRR

Valid

219.100.235.0/24

JPIRR, NTTCOM

Valid

2401:a1c0::/32

JPIRR

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