Network · data from 2026-11-12
AS131925 CYBERHOME-2
Registry name: CYBERHOME2 - FAMILY NET JAPAN INCORPORATED, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131925, 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.
| 150.91.192.0/20 | Valid | Other IRR onlyJPIRR | 671 100% |
| 160.237.96.0/19 | Valid | Other IRR onlyJPIRR | 671 100% |
| 160.237.160.0/20 | Valid | Other IRR onlyJPIRR | 671 100% |
| 160.237.176.0/21 | Valid | Other IRR onlyJPIRR | 671 100% |
| 160.237.126.0/23 | Valid | Other IRR onlyJPIRR | 669 99% |
| 160.237.184.0/22 | Valid | Other IRR onlyJPIRR | 669 99% |
| 160.237.188.0/23 | Valid | Other IRR onlyJPIRR | 669 99% |
| 160.237.190.0/24 | Valid | Other IRR onlyJPIRR | 669 99% |
| 219.100.76.0/22 | Valid | Other IRR onlyJPIRR | 669 99% |
| 2406:1940::/32 | Valid | Other IRR onlyJPIRR | 636 100% |
| 2406:1940::/33 | Valid | Other IRR onlyJPIRR | 636 100% |
| 2406:1940:8000::/33 | Valid | Other IRR onlyJPIRR | 636 100% |
| 2401:4d44::/30 | Valid | Other IRR onlyJPIRR | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS131925: AS-CYBERHOME-2. 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 (AS131925 isn't in the set, or no route object for AS131925 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 | AS131925 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-CYBERHOME-2 | In no IRR database read today. | |||||
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 17 are in fix.csv.
- Route object: RIR13
- AS-SET: not found1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 150.91.192.0/20 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 160.237.96.0/19 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 160.237.160.0/20 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 160.237.176.0/21 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 160.237.126.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 160.237.184.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 160.237.188.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 160.237.190.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.76.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2406:1940::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2406:1940::/33 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2406:1940:8000::/33 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2401:4d44::/30 | Route object only in JPIRR. Add it in the RIR database for the space. |
| AS-SET: not found | AS-CYBERHOME-2 | PeeringDB names AS-CYBERHOME-2; no IRR database read has it. |
Route objects not announced
Route objects with origin AS131925 whose prefix no peer sees AS131925 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 150.129.48.0/22 | RADB | No ROA |
| 160.237.188.0/24 | JPIRR | Valid |
| 160.237.189.0/24 | 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.