bgpreport

Network · data from 2026-11-12

AS37918 ECL-INET - NTT, Inc.

Registry name: ECL-INET - NTT, Inc., JP · not in PeeringDB

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

Announced routes

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

192.68.240.0/23 No ROA None 669 99% 69
192.68.246.0/23 No ROA None 669 99% 69
192.68.248.0/28 No ROA Nonecovered by 192.68.248.0/24 9 1%low visibility 11
129.60.0.0/17 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
129.60.128.0/17 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
129.60.0.0/16 No ROA Other IRR onlyJPIRR, RADB 672 100% 69
192.68.235.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.236.0/23 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.236.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 67
192.68.237.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 67
192.68.238.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.239.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.240.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 67
192.68.241.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 67
192.68.242.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.243.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.244.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.245.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.246.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 67
192.68.247.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 67
192.68.248.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
192.68.249.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 69
2001:df0:45::/48 No ROA Other IRR onlyJPIRR, RADB 636 100% 68

AS-SET

AS37918 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 48 are in fix.csv.

  • ROA: none23
  • Route object: none3
  • Route object: RIR20
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none192.68.240.0/23No ROA covers it. Add a ROA for AS37918, maxLength 23.669 of 673
Route object: none192.68.240.0/23No route object for it. Add a route object with origin AS37918 in the RIR database for the space.669 of 673
ROA: none192.68.246.0/23No ROA covers it. Add a ROA for AS37918, maxLength 23.669 of 673
Route object: none192.68.246.0/23No route object for it. Add a route object with origin AS37918 in the RIR database for the space.669 of 673
ROA: none192.68.248.0/28No ROA covers it. Add a ROA for AS37918, maxLength 28.9 of 673
Route object: none192.68.248.0/28No route object for it. A route object for 192.68.248.0/24 with origin AS37918 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS37918 in the RIR database for the space.9 of 673
ROA: none129.60.0.0/17No ROA covers it. Add a ROA for AS37918, maxLength 17.673 of 673
Route object: RIR129.60.0.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none129.60.128.0/17No ROA covers it. Add a ROA for AS37918, maxLength 17.673 of 673
Route object: RIR129.60.128.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none129.60.0.0/16No ROA covers it. Add a ROA for AS37918, maxLength 16.672 of 673
Route object: RIR129.60.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.68.235.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.235.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.236.0/23No ROA covers it. Add a ROA for AS37918, maxLength 23.670 of 673
Route object: RIR192.68.236.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.236.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.236.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.237.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.237.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.238.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.238.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.239.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.239.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.240.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.240.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.241.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.241.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.242.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.242.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.243.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.243.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.244.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.244.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.245.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.245.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.246.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.246.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.247.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.247.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.248.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.248.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.68.249.0/24No ROA covers it. Add a ROA for AS37918, maxLength 24.670 of 673
Route object: RIR192.68.249.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none2001:df0:45::/48No ROA covers it. Add a ROA for AS37918, maxLength 48.636 of 636
Route object: RIR2001:df0:45::/48Route object only in JPIRR, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

192.68.238.0/23JPIRR, RADBNo ROA
192.68.248.0/23JPIRR, RADBNo 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.