bgpreport

Network · data from 2026-11-12

AS38628 HIMEJI CABLE TELEVISION CORPORATION

Registry name: WINK-NET - HIMEJI CABLE TELEVISION CORPORATION, JP · PeeringDB

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

Announced routes

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

2401:e700::/32 No ROA Other IRR onlyJPIRR, RADB 635 100% 70
45.75.0.0/17 Valid Other IRR onlyJPIRR, NTTCOM 673 100% 67
61.245.32.0/19 Valid Other IRR onlyJPIRR 673 100% 67
115.84.184.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
115.124.48.0/20 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
115.126.136.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
116.193.96.0/19 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
120.50.160.0/21 Valid Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
126.209.240.0/20 Valid Other IRR onlyJPIRR 673 100% 67
163.131.64.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
163.131.80.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
163.131.96.0/21 Valid Other IRR onlyJPIRR, RADB 673 100% 67
103.16.236.0/22 Valid Other IRR onlyJPIRR, NTTCOM 671 100% 67
125.254.56.0/22 Valid Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
219.97.74.0/23 Valid Other IRR onlyJPIRR 671 100% 67
219.97.76.0/23 Valid Other IRR onlyJPIRR 671 100% 67
219.100.100.0/22 Valid Other IRR onlyJPIRR, NTTCOM 671 100% 67

AS-SET

AS38628's PeeringDB record names no 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 27 are in fix.csv.

  • ROA: none1
  • Route object: RIR17
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none2401:e700::/32No ROA covers it. Add a ROA for AS38628, maxLength 32.635 of 636
Route object: RIR2401:e700::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR45.75.0.0/17Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR61.245.32.0/19Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR115.84.184.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR115.124.48.0/20Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR115.126.136.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.193.96.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.50.160.0/21Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR126.209.240.0/20Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR163.131.64.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR163.131.80.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR163.131.96.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.16.236.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR125.254.56.0/22Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR219.97.74.0/23Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR219.97.76.0/23Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR219.100.100.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

115.84.184.0/22JPIRR, NTTCOMValid
115.84.188.0/22JPIRR, NTTCOMValid
115.126.136.0/22JPIRR, NTTCOMValid
115.126.140.0/22JPIRR, NTTCOMValid
116.193.96.0/25JPIRR, NTTCOMValid
116.193.96.128/26JPIRR, NTTCOMValid
120.50.160.0/22JPIRR, NTTCOMValid
120.50.164.0/22JPIRR, NTTCOMValid
202.183.48.0/20JPIRRNo 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.