PP Merezha
PP "Merezha"
Cluster stats
Netblocks11
All fragments 458 blocks across 116 clusters
Cluster ID191600408
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-06

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.14.28.0/22 PP "Merezha" BGP ANNOUNCED ● high
91.200.8.0/22 PP "Merezha" BGP ANNOUNCED ● high
94.232.176.0/21 PP "Merezha" RIPE ASSIGNED PI ● high
94.232.176.0/21 PP "Merezha" BGP ANNOUNCED ● high
176.107.192.0/21 PP "Merezha" RIPE ASSIGNED PI ● high
176.107.192.0/21 PP "Merezha" BGP ANNOUNCED ● high
178.54.128.0/17 PP "Merezha" RIPE ASSIGNED PI ● high
178.54.128.0/17 PP "Merezha" BGP ANNOUNCED ● high
185.175.244.0/22 PP "Merezha" BGP ANNOUNCED ● high
195.22.140.0/23 PP "Merezha" BGP ANNOUNCED ● high
2001:678:d38::/48 PP "Merezha" RIPE ASSIGNED PI ● high

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (11 of 11)
Possible discrepancies (1)

These blocks are registered to PP "Merezha" 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.

2001:678:d38::/48 /48 authorized for AS42504 — SPD Bilopol Roman Leonidovich

NIC Handles

AS48437 AS57774 DUMY-RIPE DUMY-RIPE LDC-UA-MNT MEREZHA-UA-MNT MEREZHA-UA-MNT ORG-PA292-RIPE RIPE-NCC-END-MNT mnt-ua-alfa-1