bgpreport

Network · data from 2026-11-12

AS59108 KATCH-NET - KATCH NETWORK INC.

Registry name: KATCH-NET - KATCH NETWORK INC., JP · not in PeeringDB

45IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS59108, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59108, 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.
58.145.160.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
58.145.160.0/22 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
58.145.164.0/22 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
61.215.176.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
61.215.176.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
61.215.184.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
117.58.144.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
117.58.144.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
117.58.152.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
117.74.0.0/18 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
117.74.0.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
117.74.32.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
153.124.208.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
153.124.208.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
153.124.216.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
182.23.224.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
182.23.224.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
182.23.240.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
202.243.64.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
202.243.64.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
202.243.80.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
203.140.176.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
203.140.176.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
203.140.184.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
211.14.224.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
211.14.224.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
211.14.240.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
219.99.224.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
219.99.224.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
219.99.240.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
219.121.128.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
219.121.128.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
219.121.144.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
210.79.32.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
210.79.32.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
210.79.40.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
210.171.80.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
210.171.80.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
210.171.88.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
210.236.64.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
210.236.64.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
210.236.80.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
218.40.128.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
218.40.128.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
218.40.136.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
2405:7000:400::/40 Valid Other IRR onlyJPIRR, NTTCOM, RADB 634 100% 70
2405:7000:6000::/36 Valid Other IRR onlyJPIRR, RADB 633 100% 70

AS-SET

AS59108 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 47 are in fix.csv.

  • Route object: RIR47
ChangePrefix or setDetailFull-table peers
Route object: RIR58.145.160.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.145.160.0/22Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.145.164.0/22Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.215.176.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.215.176.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.215.184.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.58.144.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.58.144.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.58.152.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.74.0.0/18Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.74.0.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.74.32.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR153.124.208.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR153.124.208.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR153.124.216.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR182.23.224.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR182.23.224.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR182.23.240.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.243.64.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.243.64.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.243.80.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.140.176.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.140.176.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.140.184.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.14.224.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.14.224.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.14.240.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.99.224.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.99.224.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.99.240.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.121.128.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.121.128.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.121.144.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.79.32.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.79.32.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.79.40.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.171.80.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.171.80.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.171.88.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.236.64.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.236.64.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.236.80.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.40.128.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.40.128.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.40.136.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2405:7000:400::/40Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2405:7000:6000::/36Route object only in JPIRR, RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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