Network · data from 2026-11-12
AS17931 Netforest
Registry name: NETFOREST - Netforest,Inc., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17931, 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.
| 202.165.160.0/20 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 203.153.72.0/21 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 203.191.136.0/21 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 211.19.48.0/20 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 218.45.16.0/20 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 103.238.236.0/22 | Valid | Other IRR onlyJPIRR, RADB | 669 99% |
| 203.153.64.0/22 | Valid | Other IRR onlyJPIRR, RADB | 669 99% |
| 203.153.68.0/22 | Valid | Other IRR onlyJPIRR, RADB | 669 99% |
| 219.100.160.0/22 | Valid | Other IRR onlyJPIRR, RADB | 669 99% |
| 2402:4700::/32 | Valid | Other IRR onlyJPIRR, RADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS17931: AS-NETFOREST. 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 (AS17931 isn't in the set, or no route object for AS17931 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 | AS17931 in it | Not covered |
|---|---|---|---|---|---|
| AS-NETFOREST | RADB | 1 | 1 | Yes | 0 |
| JPIRR (also) | 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 11 are in fix.csv.
- Route object: RIR10
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 202.165.160.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.72.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.191.136.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.19.48.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.45.16.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.238.236.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.64.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.68.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.160.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2402:4700::/32 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17931 whose prefix no peer sees AS17931 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.153.64.0/20 | JPIRR, RADB | 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.