30IPv4 routes
100.0% RPKI valid · 100.0% with a route object
1IPv6 routes
0.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS9351, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS9351, 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.
| 2401:900::/32 | No ROA | Other IRR onlyJPIRR | 633 100% |
| 27.113.192.0/19 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 61.125.144.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.198.48.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.206.192.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 110.44.64.0/19 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 112.136.0.0/17 | Valid | Other IRR onlyJPIRR | 673 100% |
| 113.20.192.0/18 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 117.18.128.0/18 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 122.152.32.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 124.40.64.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 124.40.96.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 124.110.160.0/19 | Valid | Other IRR onlyJPIRR | 673 100% |
| 150.91.128.0/20 | Valid | Other IRR onlyJPIRR | 673 100% |
| 157.70.160.0/19 | Valid | Other IRR onlyJPIRR | 673 100% |
| 157.70.192.0/20 | Valid | Other IRR onlyJPIRR | 673 100% |
| 182.22.128.0/17 | Valid | Other IRR onlyJPIRR | 673 100% |
| 193.116.0.0/19 | Valid | Other IRR onlyJPIRR | 673 100% |
| 193.117.64.0/19 | Valid | Other IRR onlyJPIRR | 673 100% |
| 202.59.176.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 202.60.160.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.91.208.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 202.137.32.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 203.133.128.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 219.103.64.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 219.109.240.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 219.113.112.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 218.45.144.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 218.216.160.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 218.228.0.0/20 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 210.236.160.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS9351: AS-9351. 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 (AS9351 isn't in the set, or no route object for AS9351 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 | AS9351 in it | Not covered |
|---|---|---|---|---|---|
| AS-9351 | JPIRR | 6 | 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 32 are in fix.csv.
- ROA: none1
- Route object: RIR31
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2401:900::/32 | No ROA covers it. Add a ROA for AS9351, maxLength 32. |
| Route object: RIR | 2401:900::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 27.113.192.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.125.144.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.198.48.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.206.192.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 110.44.64.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 112.136.0.0/17 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 113.20.192.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 117.18.128.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.152.32.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.40.64.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.40.96.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.110.160.0/19 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 150.91.128.0/20 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 157.70.160.0/19 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 157.70.192.0/20 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 182.22.128.0/17 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 193.116.0.0/19 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 193.117.64.0/19 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.59.176.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.60.160.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.91.208.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.137.32.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.133.128.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.103.64.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.109.240.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.113.112.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.45.144.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.216.160.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.228.0.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.236.160.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS9351 is announced.
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.