yasen

BGP inherited
Cluster stats
Netblocks6
Registered in China (5) · Russia (1)
Cluster ID209479064
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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
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
80.73.160.16/30 Yasen-LTD-Net RIPE ASSIGNED PA ● low
221.11.6.120/30 yasen APNIC ASSIGNED NON-PORTABLE ● low
221.11.6.128/29 yasen APNIC ASSIGNED NON-PORTABLE ● low
221.11.12.64/26 yasen APNIC ASSIGNED NON-PORTABLE ● low
221.11.12.192/26 yasen APNIC ASSIGNED NON-PORTABLE ● low
221.11.35.64/30 yasen 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: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
No discrepancies found among checked blocks.

NIC Handles

ARTX-RIPE-MNT CH679-AP CH679-AP DUMY-RIPE DUMY-RIPE MAINT-CNCGROUP-SN