IMWS

BGP inherited
Cluster stats
Netblocks6
Cluster ID211877391
RegistryAPNIC
Customersfind 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
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
110.16.15.56/30 IMWS APNIC ASSIGNED NON-PORTABLE ● low
218.21.154.69/32 IMWS APNIC ASSIGNED NON-PORTABLE ● low
218.21.155.64/32 IMWS APNIC ASSIGNED NON-PORTABLE ● low
218.21.155.76/32 IMWS APNIC ASSIGNED NON-PORTABLE ● low
218.21.155.78/32 IMWS APNIC ASSIGNED NON-PORTABLE ● low
218.21.252.69/32 IMWS APNIC ASSIGNED NON-PORTABLE ● 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.
  • IMWSYJS via CNCGROUP IP network of ShangHai IDC sub-allocation
  • IMWSWB via CNCGROUP IP network of ShangHai IDC sub-allocation
  • IMWSF via China Unicom sub-allocation
  • IMWSR via China Unicom sub-allocation
  • IMWSY via China Unicom sub-allocation
  • IMWSM via China Unicom sub-allocation
  • IMWSJDJ via CNCGROUP IP network of ShangHai IDC sub-allocation
  • IMW Sz via China Unicom sub-allocation

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

HY690-AP HY690-AP MAINT-CNCGROUP-NM