Network · data from 2026-11-12
AS55611 KYUNGMIN-AS-KR-KR - kyungmin university
Registry name: KYUNGMIN-AS-KR-KR - kyungmin university, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55611, 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.232.162.0/24 | No ROA | None | 673 100% |
| 203.232.161.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.232.163.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.232.180.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.232.181.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.232.186.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.249.38.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.50.167.0/24 | No ROA | Other IRR onlyRADB | 33 5%low visibility |
AS-SET
AS55611 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 18 are in fix.csv.
- ROA: none8
- Route object: none1
- Route object: RIR7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.232.162.0/24 | No ROA covers it. Add a ROA for AS55611, maxLength 24. |
| Route object: none | 203.232.162.0/24 | No route object for it. Add a route object with origin AS55611 in the RIR database for the space. |
| ROA: none | 203.232.161.0/24 | No ROA covers it. Add a ROA for AS55611, maxLength 24. |
| Route object: RIR | 203.232.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.232.163.0/24 | No ROA covers it. Add a ROA for AS55611, maxLength 24. |
| Route object: RIR | 203.232.163.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.232.180.0/24 | No ROA covers it. Add a ROA for AS55611, maxLength 24. |
| Route object: RIR | 203.232.180.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.232.181.0/24 | No ROA covers it. Add a ROA for AS55611, maxLength 24. |
| Route object: RIR | 203.232.181.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.232.186.0/24 | No ROA covers it. Add a ROA for AS55611, maxLength 24. |
| Route object: RIR | 203.232.186.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.249.38.0/24 | No ROA covers it. Add a ROA for AS55611, maxLength 24. |
| Route object: RIR | 203.249.38.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.50.167.0/24 | No ROA covers it. Add a ROA for AS55611, maxLength 24. |
| Route object: RIR | 211.50.167.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55611 whose prefix no peer sees AS55611 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 220.65.193.128/25 | RADB | No ROA |
| 221.155.109.160/27 | 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.