WESERVIT-RAMNODE
Cluster stats
| Netblocks | 21 |
| All fragments | 48 blocks across 2 clusters |
| Cluster ID | 193941115 |
| 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 | |
IP Ranges (21)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 81.4.100.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.101.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.102.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.103.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.104.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.105.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.106.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.107.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.108.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.109.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.110.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.111.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.120.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.121.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.122.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.123.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.124.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.125.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.126.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 81.4.127.0/24 | WESERVIT-RAMNODE | RIPE | SUB-ALLOCATED PA | ● low |
| 2a00:d880:3::/48 | WESERVIT-RAMNODE | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(21 of 21)
RPKI-inferred operator
RouteLabel V.O.F.
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
ROUTELABEL