APPARAT_AKIMA_ARKA

BGP inherited
Cluster stats
Netblocks4
All fragments 30 blocks across 17 clusters
Cluster ID204889516
RegistryRIPE
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

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
88.204.216.76/30 APPARAT_AKIMA_ARKA RIPE ASSIGNED PA ● low
88.204.216.136/30 APPARAT_AKIMA_ARKA RIPE ASSIGNED PA ● low
88.204.217.140/30 APPARAT_AKIMA_ARKA RIPE ASSIGNED PA ● low
88.204.217.160/30 APPARAT_AKIMA_ARKA RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “APPARAT AKIMA” — 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 17 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 (4 of 4)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT