Karmuz
Data as of 2026-07-26
Registry
Cluster stats
| Netblocks | 13 |
| IPv6 | 9 prefixes (largest 2a0b:4e07:c8::/48) |
| Registered in | Switzerland (2) · Germany (1) · Netherlands (1) |
| Cluster ID | 214592365 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| 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 · report an issue | |
Footprint over time
6 weekly snapshots · JSON
13
-1 netblocks since 2026-07-05
2026-07-05
peak 14
2026-07-26
IP Ranges (13)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 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 |
IPv6 ranges (9)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
53.8%
of checked blocks have valid RPKI ROA coverage
(7 of 13)
No discrepancies found among checked blocks.
NIC Handles
AS209990
DUMY-RIPE
DUMY-RIPE
KARMUZ-MNT