LANZHOU-AREA-NET-CLUB
Data as of 2026-10-04
BGP inherited
This organisation
| Netblocks | 16 · 9,085 IPv4 addresses |
| Record ID | 247197752 |
| Registry | APNIC |
| Customers | see who runs inside 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 · report an issue | |
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 61.178.13.0/24 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.16.0/24 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.18.0/23 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.20.0/23 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.23.2 – 61.178.23.126 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.25.0/24 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.26.0/23 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.28.0 – 61.178.30.255 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.30.0 – 61.178.35.255 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.59.0 – 61.178.63.255 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.74.0 – 61.178.79.255 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.109.0/24 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.110.0/24 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.111.0/24 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.111.2 – 61.178.115.126 | LANZHOU-AREA-NET-CLUB | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 61.178.115.0/24 | LANZHOU-AREA-NET-CLUB | APNIC | ASSIGNED NON-PORTABLE | ● low |
Footprint over time
15 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-10-04
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(16 of 16)
RPKI-inferred operator
No.31,Jin-rong Street
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
MAINT-CHINANET-GS
YZ37-AP
YZ37-AP