MNT-PERESVET-SERVERS

BGP inherited
Cluster stats
Netblocks6
All fragments 17 blocks across 11 clusters
Cluster ID209565092
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
85.31.176.248/29 MNT-PERESVET-SERVERS RIPE ASSIGNED PA ● low
85.31.177.64/28 MNT-PERESVET-SERVERS RIPE ASSIGNED PA ● low
85.31.177.80/28 MNT-PERESVET-SERVERS RIPE ASSIGNED PA ● low
85.31.177.96/28 MNT-PERESVET-SERVERS RIPE ASSIGNED PA ● low
85.31.177.252/30 MNT-PERESVET-SERVERS RIPE ASSIGNED PA ● low
85.31.178.252/30 MNT-PERESVET-SERVERS RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MNT PERESVET” — 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.
Combined view of all 11 name-family clusters →
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 (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-PERESVET