YaDa-electronic

BGP inherited
Cluster stats
Netblocks6
Cluster ID210110897
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
112.95.171.114/32 YaDa-electronic APNIC ASSIGNED NON-PORTABLE ● low
112.95.171.115/32 YaDa-electronic APNIC ASSIGNED NON-PORTABLE ● low
112.95.171.116/32 YaDa-electronic APNIC ASSIGNED NON-PORTABLE ● low
112.95.171.117/32 YaDa-electronic APNIC ASSIGNED NON-PORTABLE ● low
112.95.171.118/32 YaDa-electronic APNIC ASSIGNED NON-PORTABLE ● low
112.95.171.119/32 YaDa-electronic 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.

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

AC1718-AP CG272-AP CG272-AP MAINT-CNCGROUP-GD