Network · data from 2026-11-12
AS2515 JPNIC
Registry name: JPNIC - Japan Network Information Center, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2515, 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.
| 211.120.240.0/21 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 103.131.194.0/23 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 192.41.192.0/24 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 202.12.30.0/24 | Valid | Other IRR onlyJPIRR, RADB | 668 99% |
| 2001:dc2::/32 | Valid | Other IRR onlyJPIRR, RADB | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS2515: AS-JPNIC. 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 (AS2515 isn't in the set, or no route object for AS2515 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 | AS2515 in it | Not covered |
|---|---|---|---|---|---|
| AS-JPNIC | 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 7 are in fix.csv.
- Route object: RIR5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 211.120.240.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.131.194.0/23 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.41.192.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.12.30.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:dc2::/32 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2515 whose prefix no peer sees AS2515 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 211.120.248.0/24 | RADB | No ROA |
| 2001:fa0::/32 | 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.