bgpreport

Network · data from 2026-11-12

AS18164 MOKPO-AS-KR-KR - Mokpo University

Registry name: MOKPO-AS-KR-KR - Mokpo University, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18164, 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.
61.84.218.0/24 No ROA Nonecovered by 61.84.218.0/23 673 100% 67
61.84.218.64/27 No ROA Nonecovered by 61.84.218.0/23 14 2%low visibility 13
61.84.218.96/27 No ROA Nonecovered by 61.84.218.0/23 3 0%low visibility 3
61.84.218.0/23 No ROA Other IRR onlyRADB 673 100% 66
61.84.220.0/23 No ROA Other IRR onlyRADB 673 100% 66
114.70.92.0/22 No ROA Other IRR onlyRADB 673 100% 66
117.17.80.0/21 No ROA Other IRR onlyRADB 673 100% 66
117.17.88.0/22 No ROA Other IRR onlyRADB 673 100% 66
202.20.99.0/24 No ROA Other IRR onlyRADB 673 100% 66
203.234.16.0/20 No ROA Other IRR onlyRADB 673 100% 66
210.216.80.0/22 No ROA Other IRR onlyRADB 673 100% 66
210.216.84.0/23 No ROA Other IRR onlyRADB 673 100% 66
220.67.86.0/23 No ROA Other IRR onlyRADB 673 100% 66
220.67.88.0/23 No ROA Other IRR onlyRADB 673 100% 66
220.149.52.0/22 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS18164 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 40 are in fix.csv.

  • ROA: none15
  • Route object: none3
  • Route object: RIR12
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none61.84.218.0/24No ROA covers it. Add a ROA for AS18164, maxLength 24.673 of 673
Route object: none61.84.218.0/24No route object for it. A route object for 61.84.218.0/23 with origin AS18164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18164 in the RIR database for the space.673 of 673
ROA: none61.84.218.64/27No ROA covers it. Add a ROA for AS18164, maxLength 27.14 of 673
Route object: none61.84.218.64/27No route object for it. A route object for 61.84.218.0/23 with origin AS18164 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS18164 in the RIR database for the space.14 of 673
ROA: none61.84.218.96/27No ROA covers it. Add a ROA for AS18164, maxLength 27.3 of 673
Route object: none61.84.218.96/27No route object for it. A route object for 61.84.218.0/23 with origin AS18164 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS18164 in the RIR database for the space.3 of 673
ROA: none61.84.218.0/23No ROA covers it. Add a ROA for AS18164, maxLength 23.673 of 673
Route object: RIR61.84.218.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none61.84.220.0/23No ROA covers it. Add a ROA for AS18164, maxLength 23.673 of 673
Route object: RIR61.84.220.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.70.92.0/22No ROA covers it. Add a ROA for AS18164, maxLength 22.673 of 673
Route object: RIR114.70.92.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.17.80.0/21No ROA covers it. Add a ROA for AS18164, maxLength 21.673 of 673
Route object: RIR117.17.80.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.17.88.0/22No ROA covers it. Add a ROA for AS18164, maxLength 22.673 of 673
Route object: RIR117.17.88.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.20.99.0/24No ROA covers it. Add a ROA for AS18164, maxLength 24.673 of 673
Route object: RIR202.20.99.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.234.16.0/20No ROA covers it. Add a ROA for AS18164, maxLength 20.673 of 673
Route object: RIR203.234.16.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.216.80.0/22No ROA covers it. Add a ROA for AS18164, maxLength 22.673 of 673
Route object: RIR210.216.80.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.216.84.0/23No ROA covers it. Add a ROA for AS18164, maxLength 23.673 of 673
Route object: RIR210.216.84.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.67.86.0/23No ROA covers it. Add a ROA for AS18164, maxLength 23.673 of 673
Route object: RIR220.67.86.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.67.88.0/23No ROA covers it. Add a ROA for AS18164, maxLength 23.673 of 673
Route object: RIR220.67.88.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.149.52.0/22No ROA covers it. Add a ROA for AS18164, maxLength 22.673 of 673
Route object: RIR220.149.52.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

59.3.220.0/23RADBNo ROA
59.3.220.0/24RADBNo ROA
59.3.221.0/24RADBNo ROA
114.70.80.0/23RADBNo ROA
203.234.16.0/21RADBNo ROA
203.234.24.0/22RADBNo ROA
203.234.28.0/24RADBNo ROA
203.234.29.0/24RADBNo ROA
203.234.30.0/23RADBNo ROA
220.67.89.0/24RADBNo 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.