Network · data from 2026-11-12
AS18142 BIWALOBE - KISTEM Co., Ltd.
Registry name: BIWALOBE - KISTEM Co., Ltd., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18142, 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.
| 210.141.176.0/20 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 210.173.32.0/19 | No ROA | Other IRR onlyNTTCOM | 671 100% |
AS-SET
AS18142 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 16 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 210.141.176.0/20 | No ROA covers it. Add a ROA for AS18142, maxLength 20. |
| Route object: RIR | 210.141.176.0/20 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 210.173.32.0/19 | No ROA covers it. Add a ROA for AS18142, maxLength 19. |
| Route object: RIR | 210.173.32.0/19 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18142 whose prefix no peer sees AS18142 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 210.141.176.0/24 | NTTCOM | No ROA |
| 210.141.177.0/24 | NTTCOM | No ROA |
| 210.141.178.0/24 | NTTCOM | No ROA |
| 210.173.32.0/24 | NTTCOM | No ROA |
| 210.173.33.0/24 | NTTCOM | No ROA |
| 210.173.34.0/24 | NTTCOM | No ROA |
| 210.173.36.0/24 | NTTCOM | No ROA |
| 210.173.37.0/24 | NTTCOM | No ROA |
| 210.173.38.0/24 | NTTCOM | No ROA |
| 210.173.39.0/24 | NTTCOM | No ROA |
| 210.173.40.0/24 | NTTCOM | No ROA |
| 210.173.41.0/24 | NTTCOM | 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.