bgpreport

Network · data from 2026-11-12

AS55625 CWUNET-AS-KR-KR - Chungwoon University

Registry name: CWUNET-AS-KR-KR - Chungwoon University, KR · not in PeeringDB

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

Announced routes

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

1.247.193.0/24 No ROA Other IRR onlyRADB 673 100% 66
1.247.194.0/23 No ROA Other IRR onlyRADB 673 100% 66
1.247.196.0/22 No ROA Other IRR onlyRADB 673 100% 66
1.247.200.0/23 No ROA Other IRR onlyRADB 673 100% 66
1.247.202.0/24 No ROA Other IRR onlyRADB 673 100% 66
175.204.143.0/24 No ROA Other IRR onlyRADB 673 100% 66
175.204.144.0/23 No ROA Other IRR onlyRADB 673 100% 66
210.95.164.0/22 No ROA Other IRR onlyRADB 673 100% 66
210.97.44.0/24 No ROA Other IRR onlyRADB 673 100% 66
210.97.45.0/24 No ROA Other IRR onlyRADB 673 100% 66
210.97.46.0/24 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS55625 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 22 are in fix.csv.

  • ROA: none11
  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
ROA: none1.247.193.0/24No ROA covers it. Add a ROA for AS55625, maxLength 24.673 of 673
Route object: RIR1.247.193.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none1.247.194.0/23No ROA covers it. Add a ROA for AS55625, maxLength 23.673 of 673
Route object: RIR1.247.194.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none1.247.196.0/22No ROA covers it. Add a ROA for AS55625, maxLength 22.673 of 673
Route object: RIR1.247.196.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none1.247.200.0/23No ROA covers it. Add a ROA for AS55625, maxLength 23.673 of 673
Route object: RIR1.247.200.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none1.247.202.0/24No ROA covers it. Add a ROA for AS55625, maxLength 24.673 of 673
Route object: RIR1.247.202.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none175.204.143.0/24No ROA covers it. Add a ROA for AS55625, maxLength 24.673 of 673
Route object: RIR175.204.143.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none175.204.144.0/23No ROA covers it. Add a ROA for AS55625, maxLength 23.673 of 673
Route object: RIR175.204.144.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.95.164.0/22No ROA covers it. Add a ROA for AS55625, maxLength 22.673 of 673
Route object: RIR210.95.164.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.97.44.0/24No ROA covers it. Add a ROA for AS55625, maxLength 24.673 of 673
Route object: RIR210.97.44.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.97.45.0/24No ROA covers it. Add a ROA for AS55625, maxLength 24.673 of 673
Route object: RIR210.97.45.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.97.46.0/24No ROA covers it. Add a ROA for AS55625, maxLength 24.673 of 673
Route object: RIR210.97.46.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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