Network · data from 2026-11-12
AS59106 Cyber and Internet Association
Registry name: INET6 - Cyber and Internet Association, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59106, 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.
| 2001:4460::/32 | No ROA | Other IRR onlyJPIRR | 635 100% |
| 210.171.160.0/21 | Valid | Nonecovered by 210.171.160.0/20 | 669 99% |
| 210.171.168.0/21 | Valid | Nonecovered by 210.171.160.0/20 | 669 99% |
| 203.178.12.0/24 | Valid | Other IRR onlyJPIRR | 605 90% |
AS-SET
PeeringDB's irr_as_set for AS59106: AS59106:AS-INET6JP. 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 (AS59106 isn't in the set, or no route object for AS59106 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 | AS59106 in it | Not covered |
|---|---|---|---|---|---|
| AS59106:AS-INET6JP | 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 14 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: RIR2
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:4460::/32 | No ROA covers it. Add a ROA for AS59106, maxLength 32. |
| Route object: RIR | 2001:4460::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: none | 210.171.160.0/21 | No route object for it. A route object for 210.171.160.0/20 with origin AS59106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59106 in the RIR database for the space. |
| Route object: none | 210.171.168.0/21 | No route object for it. A route object for 210.171.160.0/20 with origin AS59106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59106 in the RIR database for the space. |
| Route object: RIR | 203.178.12.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59106 whose prefix no peer sees AS59106 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 157.15.56.0/23 | JPIRR | Valid |
| 157.15.56.0/24 | JPIRR | Valid |
| 157.15.57.0/24 | JPIRR | Valid |
| 210.171.160.0/20 | JPIRR | Valid |
| 2401:7b60::/32 | JPIRR | Valid |
| 2401:7b60::/34 | JPIRR | Valid |
| 2401:7b60:4000::/34 | JPIRR | Valid |
| 2401:7b60:8000::/34 | JPIRR | Valid |
| 2401:7b60: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.