Network · data from 2026-11-12
AS4678 Canon IT Solutions Inc.
Registry name: FINE - Canon IT Solutions Inc., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4678, 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.
| 157.77.0.0/16 | No ROA | Other IRR onlyJPIRR, RIPE-NONAUTH | 671 100% |
| 202.228.128.0/18 | No ROA | Other IRR onlyJPIRR, RADB | 671 100% |
| 210.134.160.0/19 | No ROA | Other IRR onlyJPIRR, RADB | 670 100% |
| 150.61.24.0/22 | No ROA | Other IRR onlyRADB | 668 99% |
| 2001:340::/32 | No ROA | Other IRR onlyJPIRR | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS4678: JPIRR::AS-FINE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS4678 isn't in the set, or no route object for AS4678 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS4678 in it | Not covered |
|---|---|---|---|---|---|
| JPIRR::AS-FINE | JPIRR | 1 | 1 | Yes | 0 |
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 15 are in fix.csv.
- ROA: none5
- Route object: RIR5
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 157.77.0.0/16 | No ROA covers it. Add a ROA for AS4678, maxLength 16. |
| Route object: RIR | 157.77.0.0/16 | Route object only in JPIRR, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 202.228.128.0/18 | No ROA covers it. Add a ROA for AS4678, maxLength 18. |
| Route object: RIR | 202.228.128.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.134.160.0/19 | No ROA covers it. Add a ROA for AS4678, maxLength 19. |
| Route object: RIR | 210.134.160.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 150.61.24.0/22 | No ROA covers it. Add a ROA for AS4678, maxLength 22. |
| Route object: RIR | 150.61.24.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:340::/32 | No ROA covers it. Add a ROA for AS4678, maxLength 32. |
| Route object: RIR | 2001:340::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4678 whose prefix no peer sees AS4678 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.193.144.0/20 | JPIRR, RADB | No ROA |
| 150.61.9.0/24 | RADB | No ROA |
| 150.61.22.0/24 | RADB | No ROA |
| 202.17.172.0/22 | RIPE-NONAUTH | No ROA |
| 202.23.200.0/21 | RIPE-NONAUTH | 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.