ZeroWolf Network
BGP inherited
Cluster stats
| Netblocks | 29 |
| All fragments | 34 blocks across 6 clusters |
| Cluster ID | 208805571 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 8 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
34
0 netblocks since 2026-07-05
2026-07-05
peak 34
2026-07-19
IP Ranges (29)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 6.99.4.26/32 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 23.154.164.142/32 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 33.0.0.26/32 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1:0:21:352:1/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2406:840:1f:1:0:21:352:1/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2406:840:1f:1000:0:21:352:1/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f429:31::7/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f613::2103:52:1/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::2b/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:3::11d/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:3::12c/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:9::10e/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:10::115/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:11::179/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:16::127/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:22::142/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:24::181/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:1cc7:fff0:1::26/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:7803:fc60:aaaa::2103:52/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a14:67c1:a080::2d40/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2a14:7581:30fa::2103:52:1/128 | ZeroWolf Network | PEERINGDB | ASSIGNED | ● high |
| 2406:840:9170::/44 | ZeroWolf-Network | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 2a0f:1cc5:f00::/48 | ZeroWolf-Network | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:f04::/48 | ZeroWolf-Network-HK3 | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:f05::/48 | ZeroWolf-Network-HK2 | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:f07::/48 | ZeroWolf-Network-JP2 | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:f09::/48 | ZeroWolf-Network-US2 | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:fff::/48 | ZeroWolf-Network-Anycast | RIPE | ASSIGNED | ● low |
| 2a14:67c1:a068::/48 | ZeroWolf-Network | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
55.2%
of checked blocks have valid RPKI ROA coverage
(16 of 29)
Possible discrepancies (8)
These blocks are registered to ZeroWolf Network but cryptographically authorized for a different, unrelated network (3 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2406:840:9170::/44 /44 | authorized for AS40115 — MoeDove |
| 2a14:67c1:a068::/48 /48 | authorized for AS210352 — Yijia Xu |
| 2a0f:1cc5:f00::/48 /48 | authorized for AS210352 — Yijia Xu |
| 2a0f:1cc5:f05::/48 /48 | authorized for AS210352 — Yijia Xu |
| 2a0f:1cc5:fff::/48 /48 | authorized for AS211575 — Rui Feng |
| 2a0f:1cc5:f04::/48 /48 | authorized for AS210352 — Yijia Xu |
| 2a0f:1cc5:f07::/48 /48 | authorized for AS210352 — Yijia Xu |
| 2a0f:1cc5:f09::/48 /48 | authorized for AS210352 — Yijia Xu |
NIC Handles
AS210352
DUMY-RIPE
DUMY-RIPE
LIUZHEN-MNT
MAINT-NBDHM-CN
ZEROWOLF-MNT
ZN328-AP
ZN328-AP