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

Footprint over time

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

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
87.76.132.0/24 Karmuz RIPE ASSIGNED PA ● high
185.1.147.250/32 Karmuz PEERINGDB ASSIGNED ● high
185.1.155.170/32 Karmuz PEERINGDB ASSIGNED ● high
185.1.222.238/32 Karmuz PEERINGDB ASSIGNED ● high
194.153.153.91/32 Karmuz PEERINGDB ASSIGNED ● high
2001:7f8:b7::a520:9990:1/128 Karmuz PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:20:9990:1/128 Karmuz PEERINGDB ASSIGNED ● high
2001:7f8:16c:1:0:20:9990:1/128 Karmuz PEERINGDB ASSIGNED ● high
2a0c:b641:701:0:a5:20:9990:1/128 Karmuz PEERINGDB ASSIGNED ● high
2a0e:46c4:102::209:990:1/128 Karmuz PEERINGDB ASSIGNED ● high
2a0b:4e07:c8::/48 KARMUZ-AS RIPE ASSIGNED ● low
2a0b:4e07:c9::/48 KARMUZ-AS RIPE ASSIGNED ● low
2a0b:4e07:ca::/48 KARMUZ-AS RIPE ASSIGNED ● low
2a0b:4e07:cb::/48 KARMUZ-AS RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
57.1% of checked blocks have valid RPKI ROA coverage (8 of 14)
No discrepancies found among checked blocks.

NIC Handles

AS209990 DUMY-RIPE DUMY-RIPE IPBNB-MNT KARMUZ-MNT ORG-KA1155-RIPE am34346