Network · data from 2026-11-12
AS45064 ZSPNET - BEIJING ZHONGGUANCUN SOFTWARE PARK DEVELOPMENT CO.,Ltd.
Registry name: ZSPNET - BEIJING ZHONGGUANCUN SOFTWARE PARK DEVELOPMENT CO.,Ltd., CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45064, 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.
| 182.48.112.0/22 | Valid | None | 5 1%low visibility |
| 182.48.116.0/22 | Valid | None | 5 1%low visibility |
| 223.223.176.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 5 1%low visibility |
AS-SET
AS45064 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.
- Route object: none2
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 182.48.112.0/22 | No route object for it. Add a route object with origin AS45064 in the RIR database for the space. |
| Route object: none | 182.48.116.0/22 | No route object for it. Add a route object with origin AS45064 in the RIR database for the space. |
| Route object: RIR | 223.223.176.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45064 whose prefix no peer sees AS45064 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 223.223.180.0/22 | NTTCOM, RADB | Valid |
| 223.223.184.0/22 | NTTCOM, RADB | Valid |
| 223.223.188.0/22 | NTTCOM, 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.