Network · data from 2026-11-12

AS55902 TS-NET - TS-NET of TOSET, Inc. in Japan

Registry name: TS-NET - TS-NET of TOSET, Inc. in Japan, JP · not in PeeringDB

15IPv4 routes 66.7% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

5No 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 AS55902, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55902, 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.247.88.0/24	No ROA	Other IRR onlyJPIRR, NTTCOM	673 100%	70
103.247.89.0/24	No ROA	Other IRR onlyJPIRR, NTTCOM	673 100%	70
103.247.90.0/24	No ROA	Other IRR onlyJPIRR, NTTCOM	673 100%	70
103.247.91.0/24	No ROA	Other IRR onlyJPIRR, NTTCOM	673 100%	70
103.247.88.0/22	No ROA	Other IRR onlyJPIRR, NTTCOM	670 100%	67
43.249.244.0/24	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	673 100%	70
43.249.245.0/24	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	673 100%	70
43.249.246.0/24	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	673 100%	70
43.249.247.0/24	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	673 100%	70
103.31.12.0/24	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	673 100%	70
103.31.13.0/24	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	673 100%	70
103.31.14.0/24	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	673 100%	70
103.31.15.0/24	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	673 100%	70
43.249.244.0/22	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	670 100%	67
103.31.12.0/22	Valid	RIR databaseAPNIC, JPIRR, NTTCOM	670 100%	67

AS-SET

AS55902 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 10 are in fix.csv.

ROA: none5
Route object: RIR5

Change	Prefix or set	Detail	Full-table peers
ROA: none	103.247.88.0/24	No ROA covers it. Add a ROA for AS55902, maxLength 24.	673 of 673
Route object: RIR	103.247.88.0/24	Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.	673 of 673
ROA: none	103.247.89.0/24	No ROA covers it. Add a ROA for AS55902, maxLength 24.	673 of 673
Route object: RIR	103.247.89.0/24	Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.	673 of 673
ROA: none	103.247.90.0/24	No ROA covers it. Add a ROA for AS55902, maxLength 24.	673 of 673
Route object: RIR	103.247.90.0/24	Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.	673 of 673
ROA: none	103.247.91.0/24	No ROA covers it. Add a ROA for AS55902, maxLength 24.	673 of 673
Route object: RIR	103.247.91.0/24	Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.	673 of 673
ROA: none	103.247.88.0/22	No ROA covers it. Add a ROA for AS55902, maxLength 22.	670 of 673
Route object: RIR	103.247.88.0/22	Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

103.247.88.0/24

No ROA covers it. Add a ROA for AS55902, maxLength 24.

673 of 673

Route object: RIR

103.247.88.0/24

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

673 of 673

ROA: none

103.247.89.0/24

No ROA covers it. Add a ROA for AS55902, maxLength 24.

673 of 673

Route object: RIR

103.247.89.0/24

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

673 of 673

ROA: none

103.247.90.0/24

No ROA covers it. Add a ROA for AS55902, maxLength 24.

673 of 673

Route object: RIR

103.247.90.0/24

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

673 of 673

ROA: none

103.247.91.0/24

No ROA covers it. Add a ROA for AS55902, maxLength 24.

673 of 673

Route object: RIR

103.247.91.0/24

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

673 of 673

ROA: none

103.247.88.0/22

No ROA covers it. Add a ROA for AS55902, maxLength 22.

670 of 673

Route object: RIR

103.247.88.0/22

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

670 of 673

Route objects not announced

Every route object with origin AS55902 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.