Network · data from 2026-11-12
AS23394 PSPINC-BDC - Pacific Software Publishing, Inc.
Registry name: PSPINC-BDC - Pacific Software Publishing, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23394, 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.
| 199.21.220.0/22 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 216.230.240.0/20 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 216.230.240.0/21 | No ROA | RIR databaseARIN, NTTCOM | 673 100% |
| 216.230.248.0/21 | No ROA | RIR databaseARIN, NTTCOM | 673 100% |
AS-SET
AS23394 isn't in PeeringDB, where networks name their AS-SET.
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 6 are in fix.csv.
- ROA: none4
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.21.220.0/22 | No ROA covers it. Add a ROA for AS23394, maxLength 22. |
| Route object: RIR | 199.21.220.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.230.240.0/20 | No ROA covers it. Add a ROA for AS23394, maxLength 20. |
| Route object: RIR | 216.230.240.0/20 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.230.240.0/21 | No ROA covers it. Add a ROA for AS23394, maxLength 21. |
| ROA: none | 216.230.248.0/21 | No ROA covers it. Add a ROA for AS23394, maxLength 21. |
Route objects not announced
Every route object with origin AS23394 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.