Gosarhiv

Registry
Cluster stats
Netblocks8
All fragments 9 blocks across 2 clusters
Cluster ID210015371
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
2.135.144.156/30 Gosarhiv RIPE ASSIGNED PA ● low
5.63.100.100/30 Gosarhiv RIPE ASSIGNED PA ● low
37.151.72.64/30 Gosarhiv RIPE ASSIGNED PA ● low
89.218.99.108/30 GosArhiv RIPE ASSIGNED PA ● low
89.218.224.172/30 Gosarhiv RIPE ASSIGNED PA ● low
92.47.96.188/30 Gosarhiv RIPE ASSIGNED PA ● low
92.47.97.24/30 Gosarhiv RIPE ASSIGNED PA ● low
92.47.97.120/30 Gosarhiv RIPE ASSIGNED PA ● low

Possibly related to this organisation

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