PINGAN-CO

BGP inherited
Cluster stats
Netblocks7
All fragments 27 blocks across 12 clusters
Cluster ID210172935
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 17 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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
114.251.36.208/28 PINGAN-CO APNIC ASSIGNED NON-PORTABLE ● high
114.251.100.96/28 PINGAN-CO APNIC ASSIGNED NON-PORTABLE ● high
114.251.100.112/28 PINGAN-CO APNIC ASSIGNED NON-PORTABLE ● high
180.168.13.200/30 PINGAN APNIC ASSIGNED NON-PORTABLE ● high
180.169.40.32/29 PINGAN APNIC ASSIGNED NON-PORTABLE ● high
222.66.142.208/29 PINGAN-CO APNIC ASSIGNED NON-PORTABLE ● high
222.68.184.160/27 PINGAN-CO APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PINGAN” — 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.
Combined view of all 12 name-family clusters →
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.

Network trust

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

NIC Handles

AC1591-AP JH1345-AP JH1345-AP MAINT-CHINANET-SH MAINT-CNCGROUP-BJ MK643-AP MK643-AP MK644-AP MK644-AP MK645-AP MK645-AP ZHS2-AP +5 more