bgpreport

Network · data from 2026-11-12

AS55909 kochi-ct - National Institute of Technology, Kochi College

Registry name: kochi-ct - National Institute of Technology, Kochi College, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55909, 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.12.158.0/25 No ROA Nonecovered by 103.12.158.0/24 14 2%low visibility 14
103.12.158.128/25 No ROA Nonecovered by 103.12.158.0/24 14 2%low visibility 14
103.12.158.0/24 No ROA Other IRR onlyJPIRR 670 100% 69
2001:df0:2cc::/48 No ROA Other IRR onlyJPIRR 634 100% 69

AS-SET

AS55909 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 9 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none103.12.158.0/25No ROA covers it. Add a ROA for AS55909, maxLength 25.14 of 673
Route object: none103.12.158.0/25No route object for it. A route object for 103.12.158.0/24 with origin AS55909 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55909 in the RIR database for the space.14 of 673
ROA: none103.12.158.128/25No ROA covers it. Add a ROA for AS55909, maxLength 25.14 of 673
Route object: none103.12.158.128/25No route object for it. A route object for 103.12.158.0/24 with origin AS55909 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55909 in the RIR database for the space.14 of 673
ROA: none103.12.158.0/24No ROA covers it. Add a ROA for AS55909, maxLength 24.670 of 673
Route object: RIR103.12.158.0/24Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none2001:df0:2cc::/48No ROA covers it. Add a ROA for AS55909, maxLength 48.634 of 636
Route object: RIR2001:df0:2cc::/48Route object only in JPIRR. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

202.126.16.0/23JPIRRInvalid: origin

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.