bgpreport

Network · data from 2026-11-12

AS37914 Univnet - Advanced Software Technology and Management Research Institute of KYOTO

Registry name: Univnet - Advanced Software Technology and Management Research Institute of KYOTO, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37914, 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.
163.208.176.0/20 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
192.50.154.0/24 No ROA Other IRR onlyJPIRR, RADB 670 100% 67

AS-SET

AS37914 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 21 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none163.208.176.0/20No ROA covers it. Add a ROA for AS37914, maxLength 20.672 of 673
Route object: RIR163.208.176.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.50.154.0/24No ROA covers it. Add a ROA for AS37914, maxLength 24.670 of 673
Route object: RIR192.50.154.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

150.89.128.0/17NTTCOM, RADBNo ROA
192.50.8.0/23NTTCOMNo ROA
202.19.144.0/21NTTCOMNo ROA
202.25.113.0/24NTTCOM, RADBNo ROA
202.26.188.0/22NTTCOM, RADBNo ROA
202.48.228.0/22NTTCOM, RADBNo ROA
202.209.199.0/28JPIRRInvalid: origin
202.209.199.32/28JPIRRInvalid: origin
202.223.142.0/24NTTCOM, RADBNo ROA
202.223.162.0/24NTTCOM, RADBNo ROA
202.223.245.0/24NTTCOM, RADBNo ROA
202.236.120.0/24NTTCOM, RADBNo ROA
202.243.128.0/20NTTCOMNo ROA
202.245.124.0/24NTTCOMNo ROA
202.252.197.0/24NTTCOMNo ROA
202.252.247.0/24NTTCOMNo ROA
2400:e400::/32JPIRR, NTTCOMNo 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.