IEYS

BGP inherited
Cluster stats
Netblocks10
Cluster ID211876610
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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.134.118.0/29 IEYS APNIC ASSIGNED NON-PORTABLE ● low
61.134.118.8/30 IEYS APNIC ASSIGNED NON-PORTABLE ● low
124.67.64.12/30 IEYS APNIC ASSIGNED NON-PORTABLE ● low
124.67.64.20/30 IEYS APNIC ASSIGNED NON-PORTABLE ● low
124.67.64.44/30 IEYS APNIC ASSIGNED NON-PORTABLE ● low
124.67.64.64/30 IEYS APNIC ASSIGNED NON-PORTABLE ● low
124.67.64.84/30 IEYS APNIC ASSIGNED NON-PORTABLE ● low
124.67.64.104/30 IEYS APNIC ASSIGNED NON-PORTABLE ● low
124.67.64.152/30 IEYS APNIC ASSIGNED NON-PORTABLE ● low
124.67.64.248/30 IEYS 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 (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

HY690-AP HY690-AP MAINT-CNCGROUP-NM