Network · data from 2026-11-12
AS2526 HITNET - Hitachi, Ltd. IT strategy & Digital Integration Division, Employee Experience Office
Registry name: HITNET - Hitachi, Ltd. IT strategy & Digital Integration Division, Employee Experience Office, JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2526, 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.
| 133.145.32.0/19 | No ROA | Nonecovered by 133.145.0.0/16 | 673 100% |
| 133.145.64.0/19 | No ROA | Nonecovered by 133.145.0.0/16 | 673 100% |
| 133.145.96.0/20 | No ROA | Nonecovered by 133.145.0.0/16 | 673 100% |
| 133.145.112.0/21 | No ROA | Nonecovered by 133.145.0.0/16 | 673 100% |
| 133.145.128.0/18 | No ROA | Nonecovered by 133.145.0.0/16 | 673 100% |
| 133.145.184.0/24 | No ROA | Nonecovered by 133.145.0.0/16 | 673 100% |
| 133.145.185.0/24 | No ROA | Nonecovered by 133.145.0.0/16 | 673 100% |
| 133.145.224.0/19 | No ROA | Nonecovered by 133.145.0.0/16 | 673 100% |
| 133.145.0.0/16 | No ROA | Other IRR onlyNTTCOM | 673 100% |
AS-SET
AS2526 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 20 are in fix.csv.
- ROA: none9
- Route object: none8
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 133.145.32.0/19 | No ROA covers it. Add a ROA for AS2526, maxLength 19. |
| Route object: none | 133.145.32.0/19 | No route object for it. A route object for 133.145.0.0/16 with origin AS2526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2526 in the RIR database for the space. |
| ROA: none | 133.145.64.0/19 | No ROA covers it. Add a ROA for AS2526, maxLength 19. |
| Route object: none | 133.145.64.0/19 | No route object for it. A route object for 133.145.0.0/16 with origin AS2526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2526 in the RIR database for the space. |
| ROA: none | 133.145.96.0/20 | No ROA covers it. Add a ROA for AS2526, maxLength 20. |
| Route object: none | 133.145.96.0/20 | No route object for it. A route object for 133.145.0.0/16 with origin AS2526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2526 in the RIR database for the space. |
| ROA: none | 133.145.112.0/21 | No ROA covers it. Add a ROA for AS2526, maxLength 21. |
| Route object: none | 133.145.112.0/21 | No route object for it. A route object for 133.145.0.0/16 with origin AS2526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2526 in the RIR database for the space. |
| ROA: none | 133.145.128.0/18 | No ROA covers it. Add a ROA for AS2526, maxLength 18. |
| Route object: none | 133.145.128.0/18 | No route object for it. A route object for 133.145.0.0/16 with origin AS2526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2526 in the RIR database for the space. |
| ROA: none | 133.145.184.0/24 | No ROA covers it. Add a ROA for AS2526, maxLength 24. |
| Route object: none | 133.145.184.0/24 | No route object for it. A route object for 133.145.0.0/16 with origin AS2526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2526 in the RIR database for the space. |
| ROA: none | 133.145.185.0/24 | No ROA covers it. Add a ROA for AS2526, maxLength 24. |
| Route object: none | 133.145.185.0/24 | No route object for it. A route object for 133.145.0.0/16 with origin AS2526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2526 in the RIR database for the space. |
| ROA: none | 133.145.224.0/19 | No ROA covers it. Add a ROA for AS2526, maxLength 19. |
| Route object: none | 133.145.224.0/19 | No route object for it. A route object for 133.145.0.0/16 with origin AS2526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2526 in the RIR database for the space. |
| ROA: none | 133.145.0.0/16 | No ROA covers it. Add a ROA for AS2526, maxLength 16. |
| Route object: RIR | 133.145.0.0/16 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2526 whose prefix no peer sees AS2526 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.246.248.0/21 | NTTCOM | No ROA |
| 2001:df0:2b4::/48 | JPIRR, NTTCOM, 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.