bgpreport

Network · data from 2026-11-12

AS9706 PETISNET-AS-KR - BUSAN EDUCATION RESEARCH & INFORMATION INSTITUTE

Registry name: PETISNET-AS-KR - BUSAN EDUCATION RESEARCH & INFORMATION INSTITUTE, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9706, 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.180.128.0/18 No ROA Other IRR onlyRADB 673 100% 67
210.180.192.0/19 No ROA Other IRR onlyRADB 673 100% 67
211.43.30.0/23 No ROA Other IRR onlyRADB 673 100% 67
211.43.32.0/19 No ROA Other IRR onlyRADB 673 100% 67
211.43.64.0/21 No ROA Other IRR onlyRADB 673 100% 67
211.43.72.0/22 No ROA Other IRR onlyRADB 673 100% 67
211.182.0.0/16 No ROA Other IRR onlyRADB 673 100% 67
211.43.29.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS9706 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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none210.180.128.0/18No ROA covers it. Add a ROA for AS9706, maxLength 18.673 of 673
Route object: RIR210.180.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.180.192.0/19No ROA covers it. Add a ROA for AS9706, maxLength 19.673 of 673
Route object: RIR210.180.192.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.43.30.0/23No ROA covers it. Add a ROA for AS9706, maxLength 23.673 of 673
Route object: RIR211.43.30.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.43.32.0/19No ROA covers it. Add a ROA for AS9706, maxLength 19.673 of 673
Route object: RIR211.43.32.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.43.64.0/21No ROA covers it. Add a ROA for AS9706, maxLength 21.673 of 673
Route object: RIR211.43.64.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.43.72.0/22No ROA covers it. Add a ROA for AS9706, maxLength 22.673 of 673
Route object: RIR211.43.72.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.182.0.0/16No ROA covers it. Add a ROA for AS9706, maxLength 16.673 of 673
Route object: RIR211.182.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.43.29.0/24No ROA covers it. Add a ROA for AS9706, maxLength 24.2 of 673
Route object: RIR211.43.29.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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