bgpreport

Network · data from 2026-11-12

AS55888 Nintatsu - Nintatsu Global Telecommunications Corporation

Registry name: Nintatsu - Nintatsu Global Telecommunications Corporation, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55888, 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.
36.50.48.0/24 No ROA Nonecovered by 36.50.48.0/23 671 100% 67
202.48.254.0/24 No ROA Other IRR onlyRADB 672 100% 67
36.50.49.0/24 No ROA Other IRR onlyRADB 671 100% 67
202.24.197.0/24 No ROA Other IRR onlyRADB 671 100% 67
36.50.48.0/23 No ROA Other IRR onlyRADB 670 100% 68
61.200.81.128/25 Valid Other IRR onlyNTTCOM 31 5%low visibility 24

AS-SET

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

  • ROA: none5
  • Route object: none1
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none36.50.48.0/24No ROA covers it. Add a ROA for AS55888, maxLength 24.671 of 673
Route object: none36.50.48.0/24No route object for it. A route object for 36.50.48.0/23 with origin AS55888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55888 in the RIR database for the space.671 of 673
ROA: none202.48.254.0/24No ROA covers it. Add a ROA for AS55888, maxLength 24.672 of 673
Route object: RIR202.48.254.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none36.50.49.0/24No ROA covers it. Add a ROA for AS55888, maxLength 24.671 of 673
Route object: RIR36.50.49.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.24.197.0/24No ROA covers it. Add a ROA for AS55888, maxLength 24.671 of 673
Route object: RIR202.24.197.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none36.50.48.0/23No ROA covers it. Add a ROA for AS55888, maxLength 23.670 of 673
Route object: RIR36.50.48.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR61.200.81.128/25Route object only in NTTCOM. Add it in the RIR database for the space.31 of 673

Route objects not announced

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