Network · data from 2026-11-12
AS10174 MBC-AS-KR-KR - Munhwa Broadcasting Corporation
Registry name: MBC-AS-KR-KR - Munhwa Broadcasting Corporation, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10174, 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.
| 103.3.36.0/24 | No ROA | None | 672 100% |
| 103.3.37.0/24 | No ROA | None | 671 100% |
| 103.3.38.0/24 | No ROA | None | 671 100% |
| 103.3.39.0/24 | No ROA | None | 671 100% |
| 103.164.78.0/24 | No ROA | Nonecovered by 103.164.78.0/23 | 671 100% |
| 103.164.79.0/24 | No ROA | Nonecovered by 103.164.78.0/23 | 671 100% |
| 203.238.224.0/19 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS10174 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 17 are in fix.csv.
- ROA: none7
- Route object: none6
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.3.36.0/24 | No ROA covers it. Add a ROA for AS10174, maxLength 24. |
| Route object: none | 103.3.36.0/24 | No route object for it. Add a route object with origin AS10174 in the RIR database for the space. |
| ROA: none | 103.3.37.0/24 | No ROA covers it. Add a ROA for AS10174, maxLength 24. |
| Route object: none | 103.3.37.0/24 | No route object for it. Add a route object with origin AS10174 in the RIR database for the space. |
| ROA: none | 103.3.38.0/24 | No ROA covers it. Add a ROA for AS10174, maxLength 24. |
| Route object: none | 103.3.38.0/24 | No route object for it. Add a route object with origin AS10174 in the RIR database for the space. |
| ROA: none | 103.3.39.0/24 | No ROA covers it. Add a ROA for AS10174, maxLength 24. |
| Route object: none | 103.3.39.0/24 | No route object for it. Add a route object with origin AS10174 in the RIR database for the space. |
| ROA: none | 103.164.78.0/24 | No ROA covers it. Add a ROA for AS10174, maxLength 24. |
| Route object: none | 103.164.78.0/24 | No route object for it. A route object for 103.164.78.0/23 with origin AS10174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10174 in the RIR database for the space. |
| ROA: none | 103.164.79.0/24 | No ROA covers it. Add a ROA for AS10174, maxLength 24. |
| Route object: none | 103.164.79.0/24 | No route object for it. A route object for 103.164.78.0/23 with origin AS10174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10174 in the RIR database for the space. |
| ROA: none | 203.238.224.0/19 | No ROA covers it. Add a ROA for AS10174, maxLength 19. |
| Route object: RIR | 203.238.224.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10174 whose prefix no peer sees AS10174 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.164.78.0/23 | RADB | No ROA |
| 203.238.227.0/24 | NTTCOM | No ROA |
| 211.180.235.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.