Network · data from 2026-11-12
AS10191 SGMF-AS-KR-KR - SEEGENE MEDICAL FOUNDATION
Registry name: SGMF-AS-KR-KR - SEEGENE MEDICAL FOUNDATION, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10191, 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.
| 219.252.39.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 222.109.87.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS10191 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 63 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced59
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 219.252.39.0/24 | No ROA covers it. Add a ROA for AS10191, maxLength 24. |
| Route object: RIR | 219.252.39.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 222.109.87.0/24 | No ROA covers it. Add a ROA for AS10191, maxLength 24. |
| Route object: RIR | 222.109.87.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10191 whose prefix no peer sees AS10191 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 113.192.64.0/18 | RADB | No ROA |
| 113.192.72.0/21 | NTTCOM | No ROA |
| 113.192.88.0/21 | NTTCOM | No ROA |
| 113.192.104.0/21 | NTTCOM | No ROA |
| 113.192.120.0/21 | NTTCOM | No ROA |
| 116.212.0.0/19 | RADB | No ROA |
| 116.212.0.0/20 | RADB | No ROA |
| 116.212.0.0/21 | RADB | No ROA |
| 116.212.8.0/21 | RADB | No ROA |
| 116.212.16.0/20 | RADB | No ROA |
| 116.212.16.0/21 | RADB | No ROA |
| 116.212.24.0/21 | RADB | No ROA |
| 124.216.0.0/16 | RADB | No ROA |
| 124.216.0.0/19 | NTTCOM, RADB | No ROA |
| 124.216.0.0/21 | RADB | No ROA |
| 124.216.8.0/21 | RADB | No ROA |
| 124.216.16.0/21 | RADB | No ROA |
| 124.216.24.0/21 | RADB | No ROA |
| 124.216.32.0/19 | NTTCOM, RADB | No ROA |
| 124.216.32.0/21 | RADB | No ROA |
| 124.216.32.0/22 | RADB | No ROA |
| 124.216.36.0/22 | NTTCOM | No ROA |
| 124.216.40.0/22 | NTTCOM | No ROA |
| 124.216.44.0/22 | NTTCOM | No ROA |
| 124.216.48.0/21 | RADB | No ROA |
| 124.216.56.0/21 | RADB | No ROA |
| 124.216.64.0/19 | NTTCOM, RADB | No ROA |
| 124.216.64.0/21 | NTTCOM | No ROA |
| 124.216.72.0/21 | NTTCOM | No ROA |
| 124.216.80.0/21 | NTTCOM | No ROA |
| 124.216.96.0/19 | NTTCOM, RADB | No ROA |
| 124.216.96.0/21 | NTTCOM | No ROA |
| 124.216.104.0/21 | NTTCOM | No ROA |
| 124.216.112.0/21 | NTTCOM | No ROA |
| 124.216.120.0/21 | NTTCOM | No ROA |
| 124.216.128.0/19 | NTTCOM, RADB | No ROA |
| 124.216.128.0/21 | NTTCOM | No ROA |
| 124.216.136.0/21 | NTTCOM | No ROA |
| 124.216.144.0/21 | NTTCOM | No ROA |
| 124.216.152.0/21 | RADB | No ROA |
| 124.216.160.0/19 | NTTCOM, RADB | No ROA |
| 124.216.160.0/21 | NTTCOM | No ROA |
| 124.216.168.0/21 | NTTCOM | No ROA |
| 124.216.176.0/21 | NTTCOM | No ROA |
| 124.216.184.0/21 | NTTCOM | No ROA |
| 124.216.192.0/19 | NTTCOM, RADB | No ROA |
| 124.216.192.0/20 | RADB | No ROA |
| 124.216.192.0/21 | RADB | No ROA |
| 124.216.200.0/21 | RADB | No ROA |
| 124.216.208.0/20 | RADB | No ROA |
| 124.216.208.0/21 | RADB | No ROA |
| 124.216.216.0/21 | RADB | No ROA |
| 124.216.224.0/19 | NTTCOM, RADB | No ROA |
| 124.216.224.0/21 | NTTCOM | No ROA |
| 124.216.232.0/21 | NTTCOM | No ROA |
| 124.216.240.0/21 | NTTCOM | No ROA |
| 124.216.248.0/21 | RADB | No ROA |
| 180.211.0.0/18 | NTTCOM, RADB | No ROA |
| 219.252.32.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.