Network · data from 2026-11-12
AS136796 CL-JP-AS - CORELINK JAPAN
Registry name: CL-JP-AS - CORELINK JAPAN, JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136796, 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.
| 195.180.150.0/23 | Invalid: origin | None | 1 0%low visibility |
| 195.180.151.0/24 | Invalid: origin | None | 1 0%low visibility |
AS-SET
AS136796 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 5 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 195.180.150.0/23 | ROAs covering it name AS834, not AS136796. If AS136796 should announce it, add a ROA for AS136796. |
| Route object: none | 195.180.150.0/23 | No route object for it. Add a route object with origin AS136796 in the RIR database for the space. |
| ROA: origin | 195.180.151.0/24 | ROAs covering it name AS834, not AS136796. If AS136796 should announce it, add a ROA for AS136796. |
| Route object: none | 195.180.151.0/24 | No route object for it. Add a route object with origin AS136796 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS136796 whose prefix no peer sees AS136796 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.192.56.0/24 | RIPE | Valid |
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.