ANPZ

BGP inherited
Cluster stats
Netblocks9
All fragments 12 blocks across 3 clusters
Cluster ID208859254
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
88.204.189.168/29 ANPZ RIPE ASSIGNED PA ● low
89.218.166.236/30 ANPZ RIPE ASSIGNED PA ● low
89.218.166.240/28 ANPZ RIPE ASSIGNED PA ● low
92.46.223.172/30 ANPZ RIPE ASSIGNED PA ● low
92.46.223.228/30 ANPZ RIPE ASSIGNED PA ● low
95.58.126.188/30 ANPZ RIPE ASSIGNED PA ● low
95.58.127.64/27 ANPZ RIPE ASSIGNED PA ● low
212.76.6.0/28 ANPZ-NET RIPE ASSIGNED PA ● low
212.154.184.36/30 ANPZ RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ANPZ” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
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.
  • TOOANPZ via JSC Kazakhtelecom sub-allocation
  • YAYANPZ sub-allocation
  • PTIANPZ via JSC Kazakhtelecom sub-allocation
  • Krishangiri via Bharti Airtel Limited sub-allocation

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.9% of checked blocks have valid RPKI ROA coverage (8 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT TNSPLUS-MNT