ISKER

BGP inherited
Cluster stats
Netblocks8
Cluster ID210445788
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.200.223.216/30 ISKER RIPE ASSIGNED PA ● low
89.218.7.192/29 ISKER RIPE ASSIGNED PA ● low
89.218.159.12/30 Isker RIPE ASSIGNED PA ● low
89.218.161.136/29 ISKER RIPE ASSIGNED PA ● low
92.46.213.120/30 ISKER RIPE ASSIGNED PA ● low
92.46.213.124/30 ISKER RIPE ASSIGNED PA ● low
92.47.95.68/30 ISKER RIPE ASSIGNED PA ● low
92.47.199.32/30 ISKER RIPE ASSIGNED PA ● 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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT