CONDORNET-SK-20111006

BGP inherited
Cluster stats
Netblocks8 · 5,040 IPv4 addresses
All fragments 17 blocks across 2 clusters
Cluster ID204706111
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 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
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
92.245.0.0/20 CONDORNET-SK-20111006 RIPE SUB-ALLOCATED PA ● low
92.245.0.0/24 CONDORNET-SK-20111006 RIPE ASSIGNED PA ● low
92.245.2.128/25 CONDORNET-SK-20111006 RIPE ASSIGNED PA ● low
92.245.4.0/29 CONDORNET-SK-20111006 RIPE ASSIGNED PA ● low
92.245.4.16/28 CONDORNET-SK-20111006 RIPE ASSIGNED PA ● low
92.245.4.64/27 CONDORNET-SK-20111006 RIPE ASSIGNED PA ● low
92.245.5.0/24 CONDORNET-SK-20111006 RIPE ASSIGNED PA ● low
92.245.6.0/24 CONDORNET-SK-20111006 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “CONDORNET SK” — 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.
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.

NIC Handles

ARTOS-MNT DUMY-RIPE DUMY-RIPE MNT-CN ORG-Cs154-RIPE