Network · data from 2026-11-12
AS131917 Toshiba I.S.
Registry name: TOSHIBA-IS - Toshiba I.S. corp, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131917, 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.
| 103.91.184.192/27 | No ROA | Nonecovered by 103.91.184.0/24 | 6 1%low visibility |
| 103.147.244.224/27 | No ROA | Nonecovered by 103.147.244.0/24 | 6 1%low visibility |
| 103.91.184.0/24 | No ROA | Other IRR onlyJPIRR, RADB | 673 100% |
| 103.147.244.0/24 | No ROA | Other IRR onlyJPIRR, RADB | 673 100% |
| 154.18.65.0/24 | No ROA | Other IRR onlyJPIRR, RADB | 673 100% |
| 154.18.67.0/24 | No ROA | Other IRR onlyJPIRR, RADB | 673 100% |
| 38.106.60.0/24 | No ROA | Other IRR onlyJPIRR, RADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS131917: AS-TOSHIBA-IS. 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 (AS131917 isn't in the set, or no route object for AS131917 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 | AS131917 in it | Not covered |
|---|---|---|---|---|---|
| AS-TOSHIBA-IS | JPIRR | 1 | 1 | Yes | 2 |
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 15 are in fix.csv.
- ROA: none7
- Route object: none2
- Route object: RIR5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.91.184.192/27 | No ROA covers it. Add a ROA for AS131917, maxLength 27. |
| Route object: none | 103.91.184.192/27 | No route object for it. A route object for 103.91.184.0/24 with origin AS131917 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131917 in the RIR database for the space. |
| ROA: none | 103.147.244.224/27 | No ROA covers it. Add a ROA for AS131917, maxLength 27. |
| Route object: none | 103.147.244.224/27 | No route object for it. A route object for 103.147.244.0/24 with origin AS131917 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131917 in the RIR database for the space. |
| ROA: none | 103.91.184.0/24 | No ROA covers it. Add a ROA for AS131917, maxLength 24. |
| Route object: RIR | 103.91.184.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.147.244.0/24 | No ROA covers it. Add a ROA for AS131917, maxLength 24. |
| Route object: RIR | 103.147.244.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 154.18.65.0/24 | No ROA covers it. Add a ROA for AS131917, maxLength 24. |
| Route object: RIR | 154.18.65.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 154.18.67.0/24 | No ROA covers it. Add a ROA for AS131917, maxLength 24. |
| Route object: RIR | 154.18.67.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 38.106.60.0/24 | No ROA covers it. Add a ROA for AS131917, maxLength 24. |
| Route object: RIR | 38.106.60.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131917 whose prefix no peer sees AS131917 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.59.149.0/24 | RADB | No ROA |
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.