Network · data from 2026-11-12
AS55911 kazukichi
Registry name: kazukichi - kazukichi, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55911, 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.66.180.0/23 | Valid | Other IRR onlyJPIRR | 673 100% |
| 157.66.181.0/24 | Valid | Other IRR onlyJPIRR | 672 100% |
| 2401:98a0:100::/40 | Valid | Other IRR onlyJPIRR | 636 100% |
| 2401:98a0:110::/44 | Valid | Other IRR onlyJPIRR | 636 100% |
| 2401:98a0::/32 | Valid | Other IRR onlyJPIRR | 635 100% |
| 2401:98a0:210::/44 | Valid | Other IRR onlyJPIRR | 635 100% |
| 2401:98a0:220::/44 | Valid | Other IRR onlyJPIRR | 635 100% |
| 2401:98a0:200::/40 | Valid | Other IRR onlyJPIRR | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS55911: AS-KAZUKICHI. 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 (AS55911 isn't in the set, or no route object for AS55911 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 | AS55911 in it | Not covered |
|---|---|---|---|---|---|
| AS-KAZUKICHI | 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 23 are in fix.csv.
- Route object: RIR8
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 157.66.180.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 157.66.181.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2401:98a0:100::/40 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2401:98a0:110::/44 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2401:98a0::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2401:98a0:210::/44 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2401:98a0:220::/44 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2401:98a0:200::/40 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55911 whose prefix no peer sees AS55911 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 157.66.180.0/24 | JPIRR | Valid |
| 2401:98a0::/33 | JPIRR | Valid |
| 2401:98a0::/34 | JPIRR | Valid |
| 2401:98a0:1::/48 | JPIRR | Invalid: maxLength |
| 2401:98a0:2::/48 | JPIRR | Invalid: maxLength |
| 2401:98a0:3::/48 | JPIRR | Invalid: maxLength |
| 2401:98a0:4::/48 | JPIRR | Invalid: maxLength |
| 2401:98a0:300::/40 | JPIRR | Invalid: maxLength |
| 2401:98a0:310::/44 | JPIRR | Invalid: maxLength |
| 2401:98a0:320::/44 | JPIRR | Invalid: maxLength |
| 2401:98a0:330::/44 | JPIRR | Invalid: maxLength |
| 2401:98a0:4000::/34 | JPIRR | Valid |
| 2401:98a0:8000::/33 | JPIRR | Valid |
| 2401:98a0:8000::/34 | JPIRR | Valid |
| 2401:98a0:c000::/34 | JPIRR | 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.