bgpreport

Network · data from 2026-11-12

AS17579 Korea Institute of Science and Technology Information

Registry name: KREONET2-AS-KR-KR - KISTI, KR · PeeringDB

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

Announced routes

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

2001:320:15::/48 No ROA None 636 100% 68
2001:320:15:123::/64 No ROA None 11 2%low visibility 9
2001:320:15:124::/64 No ROA None 11 2%low visibility 9
2001:320:15:125::/64 No ROA None 11 2%low visibility 9
2001:320:15:127::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:200::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:520::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:532::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:542::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:552::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:562::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:601::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:603::/64 No ROA None 10 2%low visibility 8
2001:320:1b00:604::/64 No ROA None 10 2%low visibility 8
2001:320:11:102::/64 No ROA None 2 0%low visibility 3
2001:320:1b00:1::128/125 No ROA None 2 0%low visibility 3
134.75.1.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.15.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.16.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.101.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.102.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.103.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.105.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.107.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.108.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.123.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.124.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.125.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.126.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.127.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.128.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.129.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.130.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.131.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.132.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.200.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.207.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.252.0/24 Valid RIR databaseAPNIC 673 100% 67
134.75.253.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
134.75.254.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.230.1.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
210.119.23.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
210.119.127.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68

AS-SET

PeeringDB's irr_as_set for AS17579: AS1237:AS-KREONET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS17579 isn't in the set, or no route object for AS17579 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS17579 in itNot covered
AS1237:AS-KREONET RADB1 member set in no database: AS1237:AS-KREOENT-TRANSITS 6623,334 Yes 16

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

  • ROA: none16
  • Route object: none16
  • AS-SET: missing member1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2001:320:15::/48No ROA covers it. Add a ROA for AS17579, maxLength 48.636 of 636
Route object: none2001:320:15::/48No route object for it. Add a route object with origin AS17579 in the RIR database for the space.636 of 636
ROA: none2001:320:15:123::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.11 of 636
Route object: none2001:320:15:123::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.11 of 636
ROA: none2001:320:15:124::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.11 of 636
Route object: none2001:320:15:124::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.11 of 636
ROA: none2001:320:15:125::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.11 of 636
Route object: none2001:320:15:125::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.11 of 636
ROA: none2001:320:15:127::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:15:127::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:200::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:200::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:520::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:520::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:532::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:532::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:542::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:542::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:552::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:552::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:562::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:562::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:601::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:601::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:603::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:603::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:1b00:604::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.10 of 636
Route object: none2001:320:1b00:604::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.10 of 636
ROA: none2001:320:11:102::/64No ROA covers it. Add a ROA for AS17579, maxLength 64.2 of 636
Route object: none2001:320:11:102::/64No route object for it. Add a route object with origin AS17579 in the RIR database for the space.2 of 636
ROA: none2001:320:1b00:1::128/125No ROA covers it. Add a ROA for AS17579, maxLength 125.2 of 636
Route object: none2001:320:1b00:1::128/125No route object for it. Add a route object with origin AS17579 in the RIR database for the space.2 of 636
AS-SET: missing memberAS1237:AS-KREONETAS1237:AS-KREONET (RADB) lists AS1237:AS-KREOENT-TRANSITS; no IRR database read has it.

Route objects not announced

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

134.75.203.0/24APNICValid

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.