LAN-WANG
BGP inherited
Cluster stats
| Netblocks | 14 |
| Cluster ID | 211734022 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
14
0 netblocks since 2026-07-05
2026-07-05
peak 14
2026-07-19
IP Ranges (14)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a01:4f8:10b:26c6::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:162:206e::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:162:2287::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:162:2290::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:162:3117::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:171:1a2e::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:171:2b12::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:202:401::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:231:aa::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:242:498e::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:252:1dd2::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:261:1282::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:272:53c5::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
| 2a01:4f8:2220:1446::/64 | LAN-WANG | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- HARBIN-HULAN-WANGYIXIUXIAN-NETBAR via Heilongjiang Province, P.R.China. sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(14 of 14)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
HOS-GUN