Chukotka-NET

BGP inherited
Cluster stats
Netblocks10 · 6,646 IPv4 addresses
All fragments 11 blocks across 2 clusters
Cluster ID208988242
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.1.64.0/21 Chukotka-NET RIPE ASSIGNED PA ● low
37.1.72.0/23 Chukotka-NET RIPE ASSIGNED PA ● low
37.1.74.0/24 Chukotka-NET RIPE ASSIGNED PA ● low
37.1.75.0/24 Chukotka-NET RIPE ASSIGNED PA ● low
37.1.76.0/22 Chukotka-NET RIPE ASSIGNED PA ● low
81.176.196.0/23 CHUKOTKA RIPE ASSIGNED PA ● low
91.106.232.0/23 Chukotka-NET RIPE ASSIGNED PA ● low
91.106.234.0/24 Chukotka-NET RIPE ASSIGNED PA ● low
91.106.235.0/24 Chukotka-NET RIPE ASSIGNED PA ● low
91.106.236.0/22 Chukotka-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: C how networks compare →
60.0% of checked blocks have valid RPKI ROA coverage (6 of 10)
RPKI-inferred operator PJSC Rostelecom
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

AS8342-MNT DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT