Network · data from 2026-11-12
AS9271 WKUNET-AS-KR - Wonkwang University
Registry name: WKUNET-AS-KR - Wonkwang University, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9271, 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.
| 203.246.100.0/24 | No ROA | Nonecovered by 203.246.100.0/22 | 672 100% |
| 203.246.101.0/24 | No ROA | Nonecovered by 203.246.100.0/22 | 672 100% |
| 203.246.102.0/24 | No ROA | Nonecovered by 203.246.100.0/22 | 672 100% |
| 203.246.103.0/24 | No ROA | Nonecovered by 203.246.100.0/22 | 672 100% |
| 210.97.136.0/24 | No ROA | Nonecovered by 210.97.136.0/22 | 672 100% |
| 210.97.137.0/24 | No ROA | Nonecovered by 210.97.136.0/22 | 672 100% |
| 210.97.138.0/24 | No ROA | Nonecovered by 210.97.136.0/22 | 672 100% |
| 210.97.139.0/24 | No ROA | Nonecovered by 210.97.136.0/22 | 672 100% |
| 210.110.108.0/24 | No ROA | Nonecovered by 210.110.108.0/22 | 672 100% |
| 210.110.109.0/24 | No ROA | Nonecovered by 210.110.108.0/22 | 672 100% |
| 210.110.110.0/24 | No ROA | Nonecovered by 210.110.108.0/22 | 672 100% |
| 210.110.111.0/24 | No ROA | Nonecovered by 210.110.108.0/22 | 672 100% |
| 61.245.224.0/19 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 123.108.16.0/20 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.249.48.0/20 | No ROA | Other IRR onlyRADB | 672 100% |
| 210.112.128.0/19 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS9271 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 56 are in fix.csv.
- ROA: none16
- Route object: none12
- Route object: RIR4
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.246.100.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 203.246.100.0/24 | No route object for it. A route object for 203.246.100.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 203.246.101.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 203.246.101.0/24 | No route object for it. A route object for 203.246.100.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 203.246.102.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 203.246.102.0/24 | No route object for it. A route object for 203.246.100.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 203.246.103.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 203.246.103.0/24 | No route object for it. A route object for 203.246.100.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 210.97.136.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 210.97.136.0/24 | No route object for it. A route object for 210.97.136.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 210.97.137.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 210.97.137.0/24 | No route object for it. A route object for 210.97.136.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 210.97.138.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 210.97.138.0/24 | No route object for it. A route object for 210.97.136.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 210.97.139.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 210.97.139.0/24 | No route object for it. A route object for 210.97.136.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 210.110.108.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 210.110.108.0/24 | No route object for it. A route object for 210.110.108.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 210.110.109.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 210.110.109.0/24 | No route object for it. A route object for 210.110.108.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 210.110.110.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 210.110.110.0/24 | No route object for it. A route object for 210.110.108.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 210.110.111.0/24 | No ROA covers it. Add a ROA for AS9271, maxLength 24. |
| Route object: none | 210.110.111.0/24 | No route object for it. A route object for 210.110.108.0/22 with origin AS9271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9271 in the RIR database for the space. |
| ROA: none | 61.245.224.0/19 | No ROA covers it. Add a ROA for AS9271, maxLength 19. |
| Route object: RIR | 61.245.224.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 123.108.16.0/20 | No ROA covers it. Add a ROA for AS9271, maxLength 20. |
| Route object: RIR | 123.108.16.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.249.48.0/20 | No ROA covers it. Add a ROA for AS9271, maxLength 20. |
| Route object: RIR | 203.249.48.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.112.128.0/19 | No ROA covers it. Add a ROA for AS9271, maxLength 19. |
| Route object: RIR | 210.112.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9271 whose prefix no peer sees AS9271 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.246.100.0/22 | RADB | No ROA |
| 203.249.48.0/24 | NTTCOM, RADB | No ROA |
| 203.249.49.0/24 | NTTCOM | No ROA |
| 203.249.50.0/24 | NTTCOM | No ROA |
| 203.249.51.0/24 | NTTCOM | No ROA |
| 203.249.52.0/22 | NTTCOM | No ROA |
| 203.249.56.0/21 | NTTCOM | No ROA |
| 210.97.136.0/22 | RADB | No ROA |
| 210.110.108.0/22 | RADB | No ROA |
| 210.112.128.0/20 | NTTCOM | No ROA |
| 210.112.144.0/22 | NTTCOM | No ROA |
| 210.112.148.0/24 | NTTCOM | No ROA |
| 210.112.149.0/24 | NTTCOM, RADB | No ROA |
| 210.112.150.0/24 | NTTCOM | No ROA |
| 210.112.151.0/24 | NTTCOM | No ROA |
| 210.112.152.0/24 | NTTCOM, RADB | No ROA |
| 210.112.153.0/24 | NTTCOM | No ROA |
| 210.112.154.0/24 | NTTCOM, RADB | No ROA |
| 210.112.155.0/24 | NTTCOM | No ROA |
| 210.112.156.0/24 | NTTCOM | No ROA |
| 210.112.157.0/24 | NTTCOM | No ROA |
| 210.112.158.0/24 | NTTCOM | No ROA |
| 210.112.159.0/24 | NTTCOM, RADB | No ROA |
| 218.151.58.0/24 | RADB | No 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.