Network · data from 2026-11-12

AS9855 KCCWF-AS-KR-KR - Korean Federation of Community Credit Cooperatives

Registry name: KCCWF-AS-KR-KR - Korean Federation of Community Credit Cooperatives, KR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 25.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No ROA 3 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS9855, seen from no peer

Announced routes

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


210.92.225.0/24	No ROA	None	673 100%	67
220.76.222.0/24	No ROA	None	673 100%	67
210.181.58.0/24	No ROA	None	671 100%	67
210.123.108.0/24	No ROA	Other IRR onlyNTTCOM	673 100%	67

AS-SET

AS9855 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 8 are in fix.csv.

ROA: none4
Route object: none3
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	210.92.225.0/24	No ROA covers it. Add a ROA for AS9855, maxLength 24.	673 of 673
Route object: none	210.92.225.0/24	No route object for it. Add a route object with origin AS9855 in the RIR database for the space.	673 of 673
ROA: none	220.76.222.0/24	No ROA covers it. Add a ROA for AS9855, maxLength 24.	673 of 673
Route object: none	220.76.222.0/24	No route object for it. Add a route object with origin AS9855 in the RIR database for the space.	673 of 673
ROA: none	210.181.58.0/24	No ROA covers it. Add a ROA for AS9855, maxLength 24.	671 of 673
Route object: none	210.181.58.0/24	No route object for it. Add a route object with origin AS9855 in the RIR database for the space.	671 of 673
ROA: none	210.123.108.0/24	No ROA covers it. Add a ROA for AS9855, maxLength 24.	673 of 673
Route object: RIR	210.123.108.0/24	Route object only in NTTCOM. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

210.92.225.0/24

No ROA covers it. Add a ROA for AS9855, maxLength 24.

673 of 673

Route object: none

210.92.225.0/24

No route object for it. Add a route object with origin AS9855 in the RIR database for the space.

673 of 673

ROA: none

220.76.222.0/24

No ROA covers it. Add a ROA for AS9855, maxLength 24.

673 of 673

Route object: none

220.76.222.0/24

No route object for it. Add a route object with origin AS9855 in the RIR database for the space.

673 of 673

ROA: none

210.181.58.0/24

No ROA covers it. Add a ROA for AS9855, maxLength 24.

671 of 673

Route object: none

210.181.58.0/24

No route object for it. Add a route object with origin AS9855 in the RIR database for the space.

671 of 673

ROA: none

210.123.108.0/24

No ROA covers it. Add a ROA for AS9855, maxLength 24.

673 of 673

Route object: RIR

210.123.108.0/24

Route object only in NTTCOM. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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