Network · data from 2026-11-12
AS9769 SEJONG-AS-KR - Sejong University
Registry name: SEJONG-AS-KR - Sejong University, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9769, 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.250.148.0/24 | No ROA | Nonecovered by 203.250.148.0/23 | 672 100% |
| 203.250.149.0/24 | No ROA | Nonecovered by 203.250.148.0/23 | 672 100% |
| 210.107.224.0/23 | No ROA | Nonecovered by 210.107.224.0/20 | 672 100% |
| 210.107.226.0/23 | No ROA | Nonecovered by 210.107.224.0/20 | 672 100% |
| 210.107.228.0/22 | No ROA | Nonecovered by 210.107.224.0/20 | 672 100% |
| 210.107.232.0/21 | No ROA | Nonecovered by 210.107.224.0/20 | 672 100% |
| 223.195.0.0/18 | No ROA | None | 672 100% |
| 223.195.64.0/20 | No ROA | None | 672 100% |
| 210.107.238.0/24 | No ROA | Nonecovered by 210.107.224.0/20 | 671 100% |
| 223.195.32.0/24 | No ROA | None | 669 99% |
| 223.195.40.0/24 | No ROA | None | 669 99% |
| 223.195.50.0/24 | No ROA | None | 669 99% |
| 115.91.213.0/24 | No ROA | None | 33 5%low visibility |
| 115.91.214.0/24 | No ROA | None | 33 5%low visibility |
| 203.250.148.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 210.107.212.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 210.107.216.0/21 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS9769 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 45 are in fix.csv.
- ROA: none17
- Route object: none14
- Route object: RIR3
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.250.148.0/24 | No ROA covers it. Add a ROA for AS9769, maxLength 24. |
| Route object: none | 203.250.148.0/24 | No route object for it. A route object for 203.250.148.0/23 with origin AS9769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 203.250.149.0/24 | No ROA covers it. Add a ROA for AS9769, maxLength 24. |
| Route object: none | 203.250.149.0/24 | No route object for it. A route object for 203.250.148.0/23 with origin AS9769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 210.107.224.0/23 | No ROA covers it. Add a ROA for AS9769, maxLength 23. |
| Route object: none | 210.107.224.0/23 | No route object for it. A route object for 210.107.224.0/20 with origin AS9769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 210.107.226.0/23 | No ROA covers it. Add a ROA for AS9769, maxLength 23. |
| Route object: none | 210.107.226.0/23 | No route object for it. A route object for 210.107.224.0/20 with origin AS9769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 210.107.228.0/22 | No ROA covers it. Add a ROA for AS9769, maxLength 22. |
| Route object: none | 210.107.228.0/22 | No route object for it. A route object for 210.107.224.0/20 with origin AS9769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 210.107.232.0/21 | No ROA covers it. Add a ROA for AS9769, maxLength 21. |
| Route object: none | 210.107.232.0/21 | No route object for it. A route object for 210.107.224.0/20 with origin AS9769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 223.195.0.0/18 | No ROA covers it. Add a ROA for AS9769, maxLength 18. |
| Route object: none | 223.195.0.0/18 | No route object for it. Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 223.195.64.0/20 | No ROA covers it. Add a ROA for AS9769, maxLength 20. |
| Route object: none | 223.195.64.0/20 | No route object for it. Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 210.107.238.0/24 | No ROA covers it. Add a ROA for AS9769, maxLength 24. |
| Route object: none | 210.107.238.0/24 | No route object for it. A route object for 210.107.224.0/20 with origin AS9769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 223.195.32.0/24 | No ROA covers it. Add a ROA for AS9769, maxLength 24. |
| Route object: none | 223.195.32.0/24 | No route object for it. Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 223.195.40.0/24 | No ROA covers it. Add a ROA for AS9769, maxLength 24. |
| Route object: none | 223.195.40.0/24 | No route object for it. Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 223.195.50.0/24 | No ROA covers it. Add a ROA for AS9769, maxLength 24. |
| Route object: none | 223.195.50.0/24 | No route object for it. Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 115.91.213.0/24 | No ROA covers it. Add a ROA for AS9769, maxLength 24. |
| Route object: none | 115.91.213.0/24 | No route object for it. Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 115.91.214.0/24 | No ROA covers it. Add a ROA for AS9769, maxLength 24. |
| Route object: none | 115.91.214.0/24 | No route object for it. Add a route object with origin AS9769 in the RIR database for the space. |
| ROA: none | 203.250.148.0/23 | No ROA covers it. Add a ROA for AS9769, maxLength 23. |
| Route object: RIR | 203.250.148.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.107.212.0/22 | No ROA covers it. Add a ROA for AS9769, maxLength 22. |
| Route object: RIR | 210.107.212.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.107.216.0/21 | No ROA covers it. Add a ROA for AS9769, maxLength 21. |
| Route object: RIR | 210.107.216.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9769 whose prefix no peer sees AS9769 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.224.36.0/22 | NTTCOM, RADB | No ROA |
| 58.224.40.0/21 | NTTCOM, RADB | No ROA |
| 118.218.200.0/22 | NTTCOM, RADB | No ROA |
| 175.116.0.0/19 | NTTCOM | No ROA |
| 210.107.224.0/20 | NTTCOM, RADB | No ROA |
| 210.117.106.0/23 | NTTCOM, RADB | No ROA |
| 210.117.108.0/23 | NTTCOM, RADB | No ROA |
| 222.237.180.0/22 | NTTCOM, RADB | No ROA |
| 222.237.184.0/22 | NTTCOM | No ROA |
| 222.237.188.0/22 | NTTCOM | No ROA |
| 222.237.192.0/22 | NTTCOM, 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.