Oskol Net
OskolNet
Cluster stats
Netblocks17
Cluster ID192395178
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (17)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.18.224.25/32 Oskolnet PEERINGDB ASSIGNED ● high
195.208.209.234/32 Oskolnet PEERINGDB ASSIGNED ● high
37.110.224.0/21 OSKOLNET RIPE ASSIGNED PA ● low
37.110.232.0/21 OSKOLNET RIPE ASSIGNED PA ● low
46.231.168.0/22 OskolNet RIPE ASSIGNED PA ● low
46.231.172.0/22 OskolNet RIPE ASSIGNED PA ● low
62.33.226.0/23 OskolNet RIPE ASSIGNED PA ● low
94.230.32.0/21 OskolNet RIPE ASSIGNED PA ● low
94.230.40.0/21 OskolNet RIPE ASSIGNED PA ● low
128.140.192.0/22 OskolNet RIPE ASSIGNED PA ● low
128.140.196.0/22 OskolNet RIPE ASSIGNED PA ● low
185.25.176.0/23 OskolNet RIPE ASSIGNED PA ● low
185.25.178.0/23 OskolNet RIPE ASSIGNED PA ● low
188.124.96.0/21 OskolNet RIPE ASSIGNED PA ● low
188.124.104.0/21 OskolNet RIPE ASSIGNED PA ● low
188.124.112.0/21 OskolNet RIPE ASSIGNED PA ● low
188.124.120.0/21 OskolNet RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: F how networks compare →
17.6% of checked blocks have valid RPKI ROA coverage (3 of 17)
Possible discrepancies (1)

These blocks are registered to OskolNet but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

62.33.226.0/23 /23 authorized for AS20485 — Joint Stock Company TransTeleCom

NIC Handles

AS48475 DUMY-RIPE DUMY-RIPE OSKOLNET-MNT TRANSTELECOM-MNT