bgpreport

Network · data from 2026-11-12

AS23569 SEOJEONG-AS-KR-KR - SEOJEONG COLLEGE

Registry name: SEOJEONG-AS-KR-KR - SEOJEONG COLLEGE, KR · not in PeeringDB

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

Announced routes

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

114.70.202.0/24 No ROA Other origin only 673 100% 67
114.70.203.0/24 No ROA Other origin only 673 100% 67
114.70.204.0/24 No ROA Other origin only 673 100% 67
114.70.205.0/24 No ROA Other origin only 673 100% 67
117.17.118.0/24 No ROA None 673 100% 67
117.17.119.0/24 No ROA None 673 100% 67
222.120.222.0/24 No ROA None 673 100% 67
222.120.223.0/24 No ROA None 673 100% 67
61.84.112.128/25 No ROA None 16 2%low visibility 13
220.121.191.96/29 No ROA None 10 1%low visibility 10
114.70.201.0/24 No ROA Other IRR onlyRADB 673 100% 67
114.70.240.0/24 No ROA Other IRR onlyRADB 673 100% 67
114.70.241.0/24 No ROA Other IRR onlyRADB 673 100% 67
114.70.242.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS23569 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 28 are in fix.csv.

  • ROA: none14
  • Route object: none10
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none114.70.202.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: none114.70.202.0/24Route objects for it name AS4766. Add a route object with origin AS23569 in the RIR database for the space.673 of 673
ROA: none114.70.203.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: none114.70.203.0/24Route objects for it name AS4766. Add a route object with origin AS23569 in the RIR database for the space.673 of 673
ROA: none114.70.204.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: none114.70.204.0/24Route objects for it name AS4766. Add a route object with origin AS23569 in the RIR database for the space.673 of 673
ROA: none114.70.205.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: none114.70.205.0/24Route objects for it name AS4766. Add a route object with origin AS23569 in the RIR database for the space.673 of 673
ROA: none117.17.118.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: none117.17.118.0/24No route object for it. Add a route object with origin AS23569 in the RIR database for the space.673 of 673
ROA: none117.17.119.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: none117.17.119.0/24No route object for it. Add a route object with origin AS23569 in the RIR database for the space.673 of 673
ROA: none222.120.222.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: none222.120.222.0/24No route object for it. Add a route object with origin AS23569 in the RIR database for the space.673 of 673
ROA: none222.120.223.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: none222.120.223.0/24No route object for it. Add a route object with origin AS23569 in the RIR database for the space.673 of 673
ROA: none61.84.112.128/25No ROA covers it. Add a ROA for AS23569, maxLength 25.16 of 673
Route object: none61.84.112.128/25No route object for it. Add a route object with origin AS23569 in the RIR database for the space.16 of 673
ROA: none220.121.191.96/29No ROA covers it. Add a ROA for AS23569, maxLength 29.10 of 673
Route object: none220.121.191.96/29No route object for it. Add a route object with origin AS23569 in the RIR database for the space.10 of 673
ROA: none114.70.201.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: RIR114.70.201.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.70.240.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: RIR114.70.240.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.70.241.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: RIR114.70.241.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.70.242.0/24No ROA covers it. Add a ROA for AS23569, maxLength 24.673 of 673
Route object: RIR114.70.242.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 AS23569 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.