Network · data from 2026-11-12
AS10157 NHNBUGS-AS-KR-KR - NHN Bugs
Registry name: NHNBUGS-AS-KR-KR - NHN Bugs, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10157, 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.132.32.0/22 | No ROA | Other IRR onlyRADB | 31 5%low visibility |
AS-SET
AS10157 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 9 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.132.32.0/22 | No ROA covers it. Add a ROA for AS10157, maxLength 22. |
| Route object: RIR | 103.132.32.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10157 whose prefix no peer sees AS10157 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 123.0.0.0/20 | NTTCOM, RADB | No ROA |
| 202.47.143.0/24 | NTTCOM | No ROA |
| 202.89.248.0/22 | NTTCOM, RADB | No ROA |
| 202.93.6.0/23 | RADB | No ROA |
| 203.110.236.0/24 | RADB | No ROA |
| 203.212.160.0/19 | RADB | No ROA |
| 211.53.6.128/25 | 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.