DE-KABELDEUTSCHLAND
Cluster stats
| Netblocks | 18 |
| All fragments | 16,500 blocks across 9,941 clusters |
| Cluster ID | 192099112 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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
2 weekly snapshots · JSON
18
0 netblocks since 2026-07-05
2026-07-05
peak 18
2026-07-06
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 83.169.144.0/20 | DE-KABELDEUTSCHLAND | RIPE | ASSIGNED PA | ● low |
| 2a02:8100::/30 | DE-KABELDEUTSCHLAND | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a02:8100::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8102::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8104::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8106::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8108::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:810a::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:810c::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:810e::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8110::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8112::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8114::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8116::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:8118::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:811a::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:811c::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a02:811e::/31 | DE-KABELDEUTSCHLAND | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
RPKI-inferred operator
Vodafone GmbH
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-KABELDEUTSCHLAND